This probably won't happen in the near future, actually. As soon as universities take any initiative in persuing DMCA violations, they'll have to continue to be proactive and be sure they don't miss anything.
The policy here at the University of Washington is simply to comply if the RIAA or MPAA make specific requests, or if they report specific violators, but to take the passive stance otherwise. Actively searching for violations is prohibitively expensive.
Any time an institution requires software to be installed at all, it's a red flag that says that institution is doing something else wrong. While it's a good idea for students to keep their computers up to date with virus scanners and security patches and the like, it's not a good idea for the institution to take that responsibility away from the students themselves.
I worked in the NOC here at the University of Washington, and the policy was to kill ethernet ports of infected computers. It was determined whether the computer was infected by analyzing traffic flow to/from the computers and picking out patterns characteristic of common worms and viruses. This not only helped alleviate the problem by preventing the viruses from propagating, but forcing the user to take action to get the wallport reactivated increased awareness.
The UW also makes CDs with the latest virus software and patches available for free from the bookstore and various other places on campus. This way users don't have to connect to the internet to clean and patch their systems, and it makes the job easy through automated software. This kit doesn't, however, let the institution perform updates automatically or install arbitrary software. The university also maintains a repository on the LAN containing virus definition files, and the virus scanner on the CD is set up to download these automatically.
So aside from the security implications the poster mentions, there are privacy issues with allowing the institution to install arbitrary software. By forcing the user to take action in order to use the resources provided, it eliminates the privacy concerns, and raises awareness of the greater issue.
I know the head in a floppy drive doesn't work the same way as it does in a hard drive, but I wonder if there's enough similarity to get the same effect? My FDDs seem to die more often than my HDDs so I'd try it with one of them before I take apart my hds
Re:Maybe public key encryption and signed DNS?
on
Pirate DNS?
·
· Score: 1
While this is a good idea, it would be slow and inefficient. If you're starting cold with no public keys stored locally, you're probably going to need to get a new key for each website you go to (for example). And if this requires TWO different server lookups, bad things will happen and people will get frustrated if things don't work perfectly and quickly. My experience with that sort of thing is that they rarely do =(
While it was a good idea, I think we'd need to figure something else out to get the effect we want.
Slashdot Mirror
This probably won't happen in the near future, actually. As soon as universities take any initiative in persuing DMCA violations, they'll have to continue to be proactive and be sure they don't miss anything.
The policy here at the University of Washington is simply to comply if the RIAA or MPAA make specific requests, or if they report specific violators, but to take the passive stance otherwise. Actively searching for violations is prohibitively expensive.
Any time an institution requires software to be installed at all, it's a red flag that says that institution is doing something else wrong. While it's a good idea for students to keep their computers up to date with virus scanners and security patches and the like, it's not a good idea for the institution to take that responsibility away from the students themselves.
I worked in the NOC here at the University of Washington, and the policy was to kill ethernet ports of infected computers. It was determined whether the computer was infected by analyzing traffic flow to/from the computers and picking out patterns characteristic of common worms and viruses. This not only helped alleviate the problem by preventing the viruses from propagating, but forcing the user to take action to get the wallport reactivated increased awareness.
The UW also makes CDs with the latest virus software and patches available for free from the bookstore and various other places on campus. This way users don't have to connect to the internet to clean and patch their systems, and it makes the job easy through automated software. This kit doesn't, however, let the institution perform updates automatically or install arbitrary software. The university also maintains a repository on the LAN containing virus definition files, and the virus scanner on the CD is set up to download these automatically.
So aside from the security implications the poster mentions, there are privacy issues with allowing the institution to install arbitrary software. By forcing the user to take action in order to use the resources provided, it eliminates the privacy concerns, and raises awareness of the greater issue.
They should use that in the FotR ad campaign... 'Rendered using the most powerful processing site in the southern hemisphere'
mm hmm, that would definitely sell all... the.... people who were going to see it anyway (geeks) =)
I know a lot of non-geeks that actually say "WTF". =)
I know the head in a floppy drive doesn't work the same way as it does in a hard drive, but I wonder if there's enough similarity to get the same effect? My FDDs seem to die more often than my HDDs so I'd try it with one of them before I take apart my hds
Why can't we do this for Invader Zim?
fp
While this is a good idea, it would be slow and inefficient. If you're starting cold with no public keys stored locally, you're probably going to need to get a new key for each website you go to (for example). And if this requires TWO different server lookups, bad things will happen and people will get frustrated if things don't work perfectly and quickly. My experience with that sort of thing is that they rarely do =(
While it was a good idea, I think we'd need to figure something else out to get the effect we want.
-David