so, after reading fermat's last theorem and how modular arithmetic and elliptical curves were related, i began to wonder if crypto, which relies heavily on modular arithmatic, could also be done using elliptical curves. in fact, not being a mathematician by any means, i was way behind and stumbled across what was obvious to people long before me.
the proof of this conjecture is pretty cool, and i am looking forward to what it means for cryptanalysis and cryptography in general.
so, after reading fermat's last theorem and how modular arithmetic and elliptical curves were related, i began to wonder if crypto, which relies heavily on modular arithmatic, could also be done using elliptical curves. in fact, not being a mathematician by any means, i was way behind and stumbled across what was obvious to people long before me.
the proof of this conjecture is pretty cool, and i am looking forward to what it means for cryptanalysis and cryptography in general.
so, i have read this latest piece, i have seen a lot of the hype for both chips. it seems to me that they're headed for different markets. intel wants the home user and the internet experience, while amd wants the high end technical market that would have bought an Alpha before. it's a shame that mere mortals like myself cannot afford this technology, but its trickle down effect is certainly welcome.
i mean, seriously. who frickin' cares what Linus says? you have the code. don't like it? who frickin' cares, incorporate your own changes. i do, and i love it. Linus' needs are what drive kernel development, not overall needs and issues. the PCMCIA shit should teach you that, as should the lousy IP stack implementation. it's about time someone stand up to this BS development model and actually do something based on performance or whatnot in a big way. the current model of "Well, it's Linus' OS" is a surefire way to stagnate development.
great, don't forget that Intel's Nightshade mboard, with the integrated NIC that does Wake on LAN, can also be put to sleep with an IP packet. these will most likely suffer the same problem. now all of your trusted IPsec Intel NICs are asleep. where did your network logging and IDS's go? oh yeah... nowhere.:) have a nice day, folks.
sorry if this got in blank.. tapped enter by mistake...
i run a thinkpad and Linux and love it. so i can't use my mwave modem, so what. *shrug* it's slower than i like, anyhow, and so i'll be grabbing a PC card modem when i need one. thinkpads are solid machines, more reliable than most other laptops out there (save for the powerbooks). guess what? over half of the hackers at defcon with laptops used... thinkpads.
i've been slashdotted. and starwars'd (i mirrored both trailers for TPM). i survived very well. how? a well tuned server. simple: control the instances of your web server to re something reasonable. apache is smart, the factory defaults wont let a slashdot effect take it down.
for fun, turn any SYN flood program (ie portfuck) on port 80 and bang away. make a bazillion servers TRY and start up and see how your box responds. simple as that.
oh yeah, my stats: PII/266, 64 MB ram, OC-3 connection in. my max instances of httpd? around 50.:)
wierdo's? well, maybe... anyhow, OpenBSD is chugging along very well. as is NetBSD, and obviously FreeBSD is, too. all of the OS's around here (Linux and the *BSD's) have their strengths, and i use all of NetBSD, OpenBSD and Linux (and IRIX, Solaris, SunOS4.x, NT, Win95, MacOS, BeOS and others) to do my job. each has benefits which aren't met by the others.
i'd like to try this. i haven't had a chance to play with it and if it works, hey, cool. if not, no big deal... i have some users who could use the proised features.
i am having difficulty in getting the OMAIL package from the server. the machine keeps telling me forbidden. i can get the other pieces, even in the server directory, i just can't get the OMAIL piece. anyone have any luck?
it deals with Intel, not MIPS. MIPS will still be IRIX. they are also porting IRIX to IA64 (no new info there) and wil help make Linux 64 bit on IA 64.
why is this news again? seriously, this is nothing new, except the misleading idea that IRIX/MIPS is dying.
d00d, Linux is not getting smaller. the kernel is getting bigger.
for someone like me who doesn't need all these new features the kernel adds, that tends to suck. i really noticed this when i was recently building some ramdisk floppies. i was starting with the darkstar resque disk (a 2.0.22 kernel) and wanted to use 2.0.29 for some networking drivers. it just wasn't going to happen with all the tools i needed as it was laid out.
and that's not to mention that distributions are getting all too large to fit onto small disks (ie look at the base size of a RedHat install). which is one reason i'm playing with single floppy distros on some of my systems.
that's not to say that Linux sucks (anyone who knows me know i have it deployed in a very important areas, like some of my beowulf supercomputing!), but seriously, let's face it, Linux is also suffering some code bloat.
yeah, i have. i really like it. both the telnet and ftp daemons work well in encrypted mode, and more importantly they handle unencrypted sessions perfectly, too. clients exist for most platforms, keysize can be huge (i use 1024 bit keys, myself), and it's transparent to the user (unlike ssh), so you don't have to "retask" them.
we have it mirrored at ftp://x.cwru.edu/pub/menace_408.mov for your viewing pleasure. i'd host it on one of my servers but our ethernet trunk is saturate.
slashdot away... brandon's got a goal of a terabyte for downloads by semesters' end.
we did it off the shelf. we're a redhat and kernel mirror, so we built our own 2.2.x kernels on top of a 5.2 install. we tweaked, of course, but hey, if you are building a supercomputer or a cluster, you better get set to tweak.
100bT and a switched hub, DEC Tulips bought on sale, donated hardware, etc... we paid approx $400 for our 8 node cluster.
i mean, who the heck wants to drop in a 2.2.x kernel rpm? c'mon! sources have been out for a while....
inetd is a mess in that it never checks the process table. i was hit last week with a DoS attack that failed. why? becuase xinetd was set to deny the IP anyhow nd never forked. just flooded my logs with failures, but hey, my machine survived.
linux inetd is, of course, subject to this issue. so just move to xinetd, already. other inetd replacements can also be used to control the number of daemon processes spawned... and you should use them. unfortunately, not everyone has the luxury of implementing firewalls.
Slashdot Mirror
so, after reading fermat's last theorem and how modular arithmetic and elliptical curves were related, i began to wonder if crypto, which relies heavily on modular arithmatic, could also be done using elliptical curves. in fact, not being a mathematician by any means, i was way behind and stumbled across what was obvious to people long before me.
the proof of this conjecture is pretty cool, and i am looking forward to what it means for cryptanalysis and cryptography in general.
so, after reading fermat's last theorem and how modular arithmetic and elliptical curves were related, i began to wonder if crypto, which relies heavily on modular arithmatic, could also be done using elliptical curves. in fact, not being a mathematician by any means, i was way behind and stumbled across what was obvious to people long before me.
the proof of this conjecture is pretty cool, and i am looking forward to what it means for cryptanalysis and cryptography in general.
so, i have read this latest piece, i have seen a lot of the hype for both chips. it seems to me that they're headed for different markets. intel wants the home user and the internet experience, while amd wants the high end technical market that would have bought an Alpha before. it's a shame that mere mortals like myself cannot afford this technology, but its trickle down effect is certainly welcome.
i mean, seriously. who frickin' cares what Linus says? you have the code. don't like it? who frickin' cares, incorporate your own changes. i do, and i love it. Linus' needs are what drive kernel development, not overall needs and issues. the PCMCIA shit should teach you that, as should the lousy IP stack implementation. it's about time someone stand up to this BS development model and actually do something based on performance or whatnot in a big way. the current model of "Well, it's Linus' OS" is a surefire way to stagnate development.
great, don't forget that Intel's Nightshade mboard, with the integrated NIC that does Wake on LAN, can also be put to sleep with an IP packet. these will most likely suffer the same problem. now all of your trusted IPsec Intel NICs are asleep. where did your network logging and IDS's go? oh yeah... nowhere. :) have a nice day, folks.
sorry if this got in blank.. tapped enter by mistake...
i run a thinkpad and Linux and love it. so i can't use my mwave modem, so what. *shrug* it's slower than i like, anyhow, and so i'll be grabbing a PC card modem when i need one. thinkpads are solid machines, more reliable than most other laptops out there (save for the powerbooks). guess what? over half of the hackers at defcon with laptops used... thinkpads.
i've been slashdotted. and starwars'd (i mirrored both trailers for TPM). i survived very well. how? a well tuned server. simple: control the instances of your web server to re something reasonable. apache is smart, the factory defaults wont let a slashdot effect take it down.
:)
for fun, turn any SYN flood program (ie portfuck) on port 80 and bang away. make a bazillion servers TRY and start up and see how your box responds. simple as that.
oh yeah, my stats: PII/266, 64 MB ram, OC-3 connection in. my max instances of httpd? around 50.
jose nazario
wierdo's? well, maybe... anyhow, OpenBSD is chugging along very well. as is NetBSD, and obviously FreeBSD is, too. all of the OS's around here (Linux and the *BSD's) have their strengths, and i use all of NetBSD, OpenBSD and Linux (and IRIX, Solaris, SunOS4.x, NT, Win95, MacOS, BeOS and others) to do my job. each has benefits which aren't met by the others.
try them all, they are, after all, free.
/j
so i did the rpcinfo scan for you folks:
/usr/sbin/rpcinfo -p crack.linuxppc.org
:)
$
program vers proto port
100000 2 tcp 111 rpcbind
100000 2 udp 111 rpcbind
not much there other than bind... but that can be useful. i leave it as an exercise on what to do with that info.
hi,
i'd like to try this. i haven't had a chance to play with it and if it works, hey, cool. if not, no big deal... i have some users who could use the proised features.
i am having difficulty in getting the OMAIL package from the server. the machine keeps telling me forbidden. i can get the other pieces, even in the server directory, i just can't get the OMAIL piece. anyone have any luck?
jose
it deals with Intel, not MIPS. MIPS will still be IRIX. they are also porting IRIX to IA64 (no new info there) and wil help make Linux 64 bit on IA 64.
why is this news again? seriously, this is nothing new, except the misleading idea that IRIX/MIPS is dying.
jose nazario
d00d, Linux is not getting smaller. the kernel is getting bigger.
for someone like me who doesn't need all these new features the kernel adds, that tends to suck. i really noticed this when i was recently building some ramdisk floppies. i was starting with the darkstar resque disk (a 2.0.22 kernel) and wanted to use 2.0.29 for some networking drivers. it just wasn't going to happen with all the tools i needed as it was laid out.
and that's not to mention that distributions are getting all too large to fit onto small disks (ie look at the base size of a RedHat install). which is one reason i'm playing with single floppy distros on some of my systems.
that's not to say that Linux sucks (anyone who knows me know i have it deployed in a very important areas, like some of my beowulf supercomputing!), but seriously, let's face it, Linux is also suffering some code bloat.
jose
yeah, i have. i really like it. both the telnet and ftp daemons work well in encrypted mode, and more importantly they handle unencrypted sessions perfectly, too. clients exist for most platforms, keysize can be huge (i use 1024 bit keys, myself), and it's transparent to the user (unlike ssh), so you don't have to "retask" them.
http://srp.stanford.edu/
enjoy, it works well!
hi all,
we have it mirrored at ftp://x.cwru.edu/pub/menace_408.mov for your viewing pleasure. i'd host it on one of my servers but our ethernet trunk is saturate.
slashdot away... brandon's got a goal of a terabyte for downloads by semesters' end.
jnazario
we did it off the shelf. we're a redhat and kernel mirror, so we built our own 2.2.x kernels on top of a 5.2 install. we tweaked, of course, but hey, if you are building a supercomputer or a cluster, you better get set to tweak.
100bT and a switched hub, DEC Tulips bought on sale, donated hardware, etc... we paid approx $400 for our 8 node cluster.
i mean, who the heck wants to drop in a 2.2.x kernel rpm? c'mon! sources have been out for a while....
inetd is a mess in that it never checks the process table. i was hit last week with a DoS attack that failed. why? becuase xinetd was set to deny the IP anyhow nd never forked. just flooded my logs with failures, but hey, my machine survived.
linux inetd is, of course, subject to this issue. so just move to xinetd, already. other inetd replacements can also be used to control the number of daemon processes spawned... and you should use them. unfortunately, not everyone has the luxury of implementing firewalls.
i grabbed xinetd from tp://coast.cs.purdue.edu/pub/tool/u nix/xinetd/ and it works like a champ.