Note to whoever moderated that as "Funny": that wasn't meant to be funny.
What I meant is that you should hope that they are literally 'kiddies' (read: children) and not adults (read: criminals) who might decide to visit your house and do unpleasant things to you (read: rob you, assault you, kill you).
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Your browser doesn't realize it's a binary file. Try IE (if possible) and right-click on the link and choose "Save As"; if the server reports the file as ASCII, Netscape will convert it to MS-DOS style ASCII (and mess it up) whereas IE will not.
Incidentally, all I saw was "slashdot.pqa" (Netscape 4.74)...
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Though they put so much work into A3D, they seemed to have skimped out on other aspects. One of the many problems I had with my Vortex2 card was that if I had 2 or more programs using the soundcard, sound would clip horribly. Even if only one of them was producing sound! The other big problem I ran into was poor SB16 emulation, particularly in its OPL2/OPL3 synthesis which was off-pitch AND failed to produce effects such as vibrato and tremolo, resulting in the music in my old MS-DOS games (like DOOM) sounding rather bland.
Which is why I ended up buying an SB Live! to replace it, only to find that its SB16 emulation does not work AT ALL due to some aspect of my system (possibly the motherboard itself; the DOS drivers don't even work); now I can trade my old Aureal Vortex2 card for a genuine SB16 to use in the system along with the SB Live!:)
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
The policy at most stores is that once the package is opened, you can only return it for the same thing (to allow you to get rid of defective media).
Because for all they know, you could have just bought the CD so you could make 50 copies of it and give[/sell] them to your friends and then return the CD so you effectively got 50 copies of the music for the cost of 50 blank CD-R's (and about 5-6 hours to burn them [at 10-12x]), which has the same end result as distributing them over Napster/gnutella/etc.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Actually, it IS possible to IP spoof with TCP, though it's rather difficult to do anything. You basically send a TCP SYN to some site spoofed as coming from an IP that's not going to respond (and result in the connection being refused). You then assume the server is going to send a SYN/ACK, so you wait a bit and then send an ACK and poof, the connection is established. The only thing you can do from here is send information TO the system, since any information the system tries to send you will be sent into oblivion (a non-existant system), but this could easily be used to buffer overflow a system and either crash it OR prepare it for being hacked. Which is why these itrace packets might be useful for TCP as well as UDP/ICMP/any other IP-based protocols.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
And while we're at it, an 'excessive bold' detector might be nice (perhaps limit a post to 30% bold or less; you should never need to emphasise THAT much), which would help get rid of the farm animal fawker and the E-Commerce spammer.
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
The only result of that is that the spammers and trolls will just start registering hundreds of accounts.
That, or Slashdot could implement something rather interesting: the ability to distinguish unregistered anonymous comments from registered anonymous comments. The only difference would be that, intsead of labeling registered anonymous comments as "Anonymous Coward", they would be labeled as "Anonymous Hero". Though I don't know exactly how well this would work, it seems like a good idea.
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Just like the other 5 replies to your post. And the hundreds of others that have been appearing all over Slashdot. I fear that these goatse.cx kiddies are the ones who will bring Slashdot's demise...
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Re:Ha, only 3 minutes and already
on
Geek Flavor
·
· Score: 1
Stupid me... it's part of Linux sourcecode:)
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Re:Ha, only 3 minutes and already
on
Geek Flavor
·
· Score: 1
...in ASCII, yet. And it's still there. Not bad...
Now, $5 to the first person who figures out what program's sourcecode was used for the text:)
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Also, there exist the 169.254.x.x addresses which Windows seems to enjoy assigning to itself. Though not officially part of RFC1918, they seem to be generally accepted as internal addresses.
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Okay, so maybe that was a bad example. I've seen others, though, which went through several internal IPs and then resurfaced several hops before the last one. I just can't think of any off the top of my head.
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
If you're going to be picky about it, then I'll be slightly pickier: /sbin/ipchains -A input -d 127.0.0.0/24 -j REJECT /sbin/ipchains -A input -d 192.168.0.0/16 -j REJECT /sbin/ipchains -A input -d 10.0.0.0/8 -j REJECT and, I think... /sbin/ipchains -A input -d 172.16.0.0/20 -j REJECT for 172.16.*.* thru 172.31.*.* (also internal IP ranges).
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Interestingly enough, I have received legitimate packets across the internet from IPs in the range of 192.168.*.*, 172.16.*.* - 172.31.*.*, and 10.*.*.*. How? Traceroute! It seems that some networks (including @home) are too cheap to assign an external IP to all of their routers, so when traffic goes through their network, the routers routing it have internal IP addresses (which are not noticed unless you do a traceroute or just ping with a low TTL set). Example: try tracert'ing a few IPs in the 24.112.51.* (@home) range.
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Which is what my ISP does already; any traffic coming from inside with an IP not within 169.207.*.* gets dropped and returns an error packet to the sender. Likewise, anything coming into the ISP marked as coming from one of their IP ranges should be blocked (a packet coming from (for example, if I'm on a LAN with a firewall facing the outside and my IP is 192.168.0.1, I should not be getting packets from 192.168.0.2 through the firewall since that address is already behind it). Sadly, the only thing that prevents other ISPs (and universities, by far the worst) from doing this is sheer lazyness or ignorance.
-- Sig, 120 chars -- Your friendly neighborhood mIRC scripter. if (ismoderator(reader)) hidecomment(this);
Slashdot Mirror
Eesh...
:)
Though you definitely have a point on that last line
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
- urinate
- defecate
- flatulate
Any I missed?-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
--
Note to whoever moderated that as "Funny": that wasn't meant to be funny.
What I meant is that you should hope that they are literally 'kiddies' (read: children) and not adults (read: criminals) who might decide to visit your house and do unpleasant things to you (read: rob you, assault you, kill you).
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Your browser doesn't realize it's a binary file.
Try IE (if possible) and right-click on the link and choose "Save As"; if the server reports the file as ASCII, Netscape will convert it to MS-DOS style ASCII (and mess it up) whereas IE will not.
Incidentally, all I saw was "slashdot.pqa" (Netscape 4.74)...
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Though they put so much work into A3D, they seemed to have skimped out on other aspects.
:)
One of the many problems I had with my Vortex2 card was that if I had 2 or more programs using the soundcard, sound would clip horribly. Even if only one of them was producing sound!
The other big problem I ran into was poor SB16 emulation, particularly in its OPL2/OPL3 synthesis which was off-pitch AND failed to produce effects such as vibrato and tremolo, resulting in the music in my old MS-DOS games (like DOOM) sounding rather bland.
Which is why I ended up buying an SB Live! to replace it, only to find that its SB16 emulation does not work AT ALL due to some aspect of my system (possibly the motherboard itself; the DOS drivers don't even work); now I can trade my old Aureal Vortex2 card for a genuine SB16 to use in the system along with the SB Live!
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Then, of course, there's the "Red Hat Hackers"...
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Actually, it IS possible to IP spoof with TCP, though it's rather difficult to do anything. You basically send a TCP SYN to some site spoofed as coming from an IP that's not going to respond (and result in the connection being refused). You then assume the server is going to send a SYN/ACK, so you wait a bit and then send an ACK and poof, the connection is established. The only thing you can do from here is send information TO the system, since any information the system tries to send you will be sent into oblivion (a non-existant system), but this could easily be used to buffer overflow a system and either crash it OR prepare it for being hacked. Which is why these itrace packets might be useful for TCP as well as UDP/ICMP/any other IP-based protocols.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
And while we're at it, an 'excessive bold' detector might be nice (perhaps limit a post to 30% bold or less; you should never need to emphasise THAT much), which would help get rid of the farm animal fawker and the E-Commerce spammer.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
The only result of that is that the spammers and trolls will just start registering hundreds of accounts.
That, or Slashdot could implement something rather interesting: the ability to distinguish unregistered anonymous comments from registered anonymous comments. The only difference would be that, intsead of labeling registered anonymous comments as "Anonymous Coward", they would be labeled as "Anonymous Hero".
Though I don't know exactly how well this would work, it seems like a good idea.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Just like the other 5 replies to your post. And the hundreds of others that have been appearing all over Slashdot. I fear that these goatse.cx kiddies are the ones who will bring Slashdot's demise...
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Stupid me... it's part of Linux sourcecode :)
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
...in ASCII, yet. And it's still there. Not bad...
:)
Now, $5 to the first person who figures out what program's sourcecode was used for the text
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Finally figured it out... Windows assigns itself a 169.254.x.x IP when it's told to use DHCP but can't find a DHCP server. More info here.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Also, there exist the 169.254.x.x addresses which Windows seems to enjoy assigning to itself. Though not officially part of RFC1918, they seem to be generally accepted as internal addresses.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Okay, so maybe that was a bad example.
I've seen others, though, which went through several internal IPs and then resurfaced several hops before the last one.
I just can't think of any off the top of my head.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
doh :)
/sbin/ipchains -A input -d 172.16.0.0/20 -j REJECT
/sbin/ipchains -A input -d 172.16.0.0/12 -j REJECT :)
should be
I counted the wrong bits
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
If you're going to be picky about it, then I'll be slightly pickier:
/sbin/ipchains -A input -d 127.0.0.0/24 -j REJECT
/sbin/ipchains -A input -d 192.168.0.0/16 -j REJECT
/sbin/ipchains -A input -d 10.0.0.0/8 -j REJECT
/sbin/ipchains -A input -d 172.16.0.0/20 -j REJECT
and, I think...
for 172.16.*.* thru 172.31.*.* (also internal IP ranges).
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Interestingly enough, I have received legitimate packets across the internet from IPs in the range of 192.168.*.*, 172.16.*.* - 172.31.*.*, and 10.*.*.*. How? Traceroute!
It seems that some networks (including @home) are too cheap to assign an external IP to all of their routers, so when traffic goes through their network, the routers routing it have internal IP addresses (which are not noticed unless you do a traceroute or just ping with a low TTL set).
Example: try tracert'ing a few IPs in the 24.112.51.* (@home) range.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);
Which is what my ISP does already; any traffic coming from inside with an IP not within 169.207.*.* gets dropped and returns an error packet to the sender. Likewise, anything coming into the ISP marked as coming from one of their IP ranges should be blocked (a packet coming from (for example, if I'm on a LAN with a firewall facing the outside and my IP is 192.168.0.1, I should not be getting packets from 192.168.0.2 through the firewall since that address is already behind it).
Sadly, the only thing that prevents other ISPs (and universities, by far the worst) from doing this is sheer lazyness or ignorance.
-- Sig, 120 chars --
Your friendly neighborhood mIRC scripter.
if (ismoderator(reader)) hidecomment(this);