I show that line on my comcast connect as well, however the tcp connect is blocked. TCP is not generally needed on a home connection as it allows for requesting larger UDP and that gets most people through. Of course 'most people' isn't everyone:(
Digs with tcpdump show me talking to opendns's servers so does not appear to be a redirect.
This is on a basic Comcast home connection however Comcast has the apperance of placing different rules in various parts of the country.
Permalink on scan
Any halfway decent sysadmin has about a dozen ways to punch holes in that particular scheme, and particularly at a bank you're almost certainly not going to get that to work. ARPtables, captive portals, fwknop, ssh, the list is endless of ways to stop that from working.
Sadly if you look less at the 'bank' world and more at the smaller 'Credit Unions' you'll quickly find little to no fully qualified sysadmins, instead you'll generally find over-titled help desk people with a bunch of vendors. Some have security vendors who MIGHT do continuous observations but generally do 'scans' at predetermined intervals. So yes there ARE endless ways to 'stop that from working' but sadly not all the people in position to use said ways are capable or have the time to do them.
So, a "Flag official, who declined to be named" reports that a major portion of the Gulf region's communications are being rerouted through the US and UK.
It's probably not as fishy as it sounds. I seem to recall a major portion of all Internet traffic at least passes through the US. However, it does make you wonder.
Of course this adds an interesting twist to the NSA wanting to access the 'tubes' that are running through the USA and the big worry that the anti-terrorism battle will be horribly lost if we don't let them sniff every packet that crosses the continent.
The problem is that I don't think there is a business model that really leaves the record companies in any form that we, and more importantly the shareholders would recognize. If anyone can distribute an MP3, then where does that leave the distribution channels? Since creating recorded music has become so much cheaper, the record companies don't even have that bottleneck. Well for all the crap they do, the Record Companies still do a lot of work in promotion. Sure having a grass roots effort promote your stuff works well for some but many people will give the Companies money to have them do all the work and let them (the artists) become famous from it.
It is not hard to write a quick PERL script that sends a packet to a server you control at boot up and/or at regular intervals. The server would just need to record the IP and time you checked in. This takes it off of some 'tracking' company's server and keeps the data in your control and you still have the history of where the machine was used. Not perfect but if someone were motivated they could make it a bit more complex (ssl etc) with a little bit more time.
Yah I was thinking something along those lines as well. Basically the prosecution would have to show what version of the Kazaa software they believed the defendant to be using and then show that option was not available in that version. I have no idea if it was avail or not at the time, however as it is an option today you would have to find that out. Of course that brings an interesting point, it's been a few days but I'm not sure the MediaSentry logs report the version of the client in use. If they don't then they have another problem as Kazaa was not found on the defendant's computer to get a version, even if it had been the version found on the drive at the time of mirroring would not necessarily be the same as at the alleged time of infringement.
Slashdot Mirror
I show that line on my comcast connect as well, however the tcp connect is blocked. TCP is not generally needed on a home connection as it allows for requesting larger UDP and that gets most people through. Of course 'most people' isn't everyone :(
Digs with tcpdump show me talking to opendns's servers so does not appear to be a redirect.
This is on a basic Comcast home connection however Comcast has the apperance of placing different rules in various parts of the country.
Permalink on scan
It is not hard to write a quick PERL script that sends a packet to a server you control at boot up and /or at regular intervals. The server would just need to record the IP and time you checked in. This takes it off of some 'tracking' company's server and keeps the data in your control and you still have the history of where the machine was used. Not perfect but if someone were motivated they could make it a bit more complex (ssl etc) with a little bit more time.
Lol did you actually click on his link? He is the Lawyer for a couple of the contested cases out there.
Yah I was thinking something along those lines as well. Basically the prosecution would have to show what version of the Kazaa software they believed the defendant to be using and then show that option was not available in that version. I have no idea if it was avail or not at the time, however as it is an option today you would have to find that out. Of course that brings an interesting point, it's been a few days but I'm not sure the MediaSentry logs report the version of the client in use. If they don't then they have another problem as Kazaa was not found on the defendant's computer to get a version, even if it had been the version found on the drive at the time of mirroring would not necessarily be the same as at the alleged time of infringement.