Do you have a reference to statute or a precedent that backs that statement up?
Okay... no, but I'm not ready to give up yet.
It isn't usually the case that data generated by a copyrighted program is automatically assumed to be held under the copyright of the owners of the program. For instance, Microsoft doesn't hold copyright to IP packets that are transmitted by windows machines, even though it is their code that assembles those packets.
An interesting point.
Wouldn't circumventing STK's copyright protection mechanism (definition used liberally: GetKey) be copyright infringement? Isn't this the same as using deCSS or any other copyright circumvention techniques?
The 3rd party vendor is using STK's code to generate error logs and to diagnose hardware/software problems. They're basing their business largely on the unlicensed use of STK's intellectual property (the maintenance code in this case). How is that legal?
I read someone mentioning SCO in another thread, but I don't see how this pertains to the SCO trials. This isn't some farfetched claim that STK contributed 2 lines in a sub-routine somewhere... this is proprietary software that is a major contributor to STK's revenue.. and by the looks of their earnings the past few quarters they need all the money they can get.
It sucks that they've got a monopoly on the maintenance of the hardware they developed, but whoop-de-freakin-doo. That comes with the territory of buying "enterprise class" hardware, does it not?
The Maintenance Code is copyrighted material and protected intellectual property of StorageTek. The use of the event messages generated by the maintenance code by the 3rd party maintenance vendor is thus copyright infringement.
This is an open-and-shut case and shouldn't set a bad precedent in my opinion. It's upholding copyright law.
I would imagine that the early adopters of Wi-Fi were tech savy and thus that the "average" user two years ago was more tech savy than the "average" user today. It's numbers.
There will always be labels. There will always be talented musicians. There will always be people better than the guy writing all his music in fruity-loops and making it sound just like That Trance Track from 1999. The point is: now technology has come to a point where musically talented individuals with some creativity can create music that's at least pleasing to themselves without spending several thousand dollars on hardware and building an in-house studio full of synthesizers, drum machines, mixers, and effects processors.
Open publishing is already here and it's call the internet.
recording conversations, television, random noises, or sounds that i find interesting. take an 1/8th" jack from the ear out on the mini to the mic in on my laptop.. then cut it up with soundforge and use the wavs as samples.
I suck at piano and the fact that all I need to make music now is a laptop, a handheld mini-cassette recorder, and a single audio cable makes me happy. Working within a strict budget and being an electronic musician has always been pretty easy. Freeware tools that let you make noise have been around for a while. It's simply much easier and more accessible now.
Since when are composition and melody rad concepts, anyway? I'd hardly consider those ideas radical. What about experimental sound creation? What about twiddling knobs until you create the exact sound that's in your head and then build an idea out of that single sound? What about cutting up samples and putting them together much like the literary styles of Brion Gysin or William S. Burroughs? All easily done on a laptop with a couple of pieces of software.
I've heard more melodies than I care to think about and I think that area's been explored pretty well. I can't imagine what the next progression is for the melody. I can imagine what some of the next steps in sound creation are.
Good production can't make up for bad music, but it can make good music much better.
I was an Excite@home customer. I'm glad someone closed the holes.
I was a NYTimes customer. I'm glad someone closed the holes.
I was a Yahoo member. I'm glad someone closed the holes.
The fact that these holes existed and the companies weren't doing anything about them (because their admins misconfigured proxies and who knows what else) says to me that they didn't know the holes existed. Look at his targets. Were these 50-employee small businesses that got their IIS web-server hacked? No. They weren't. They were all very large corporations with substantial customer bases that had gaping holes in their security.
The targets were carefully selected and the publicity was purposeful. I doubt he made it public on purpose and I'd hardly call it bragging. This isn't someone getting on EFnet and joining #warez and saying (while holding down the shift-key instead of using caps lock)
# Appears as ADRIAN ADRIAN: OMG I HAXORED NYTIMES AND PWN3D THEIR PROXZ!
This was someone being professional about what he was doing, or so it would appear, calling up the system administrators and offering to help fix the problem. Not to mention making it publicly known that large American corporations don't care about safe-guarding data like your SSID or credit card numbers. But everyone already knew that, right? I guess nobody cares.
Damage? They owe him their thanks. If you didn't bother reading some of the other articles about his past experience you would have learned that most of the companies were grateful (WorldCom and @Home just to name a couple). The fact that the people at NYTimes are whiny asshats was simply something that was bound to happen sooner or later. Read some more articles and you'll see that some of the SSIDs he got were of some pretty important figures in world politics. I'm sure plenty of powerful people were pissed and expected, if not demanded, that NYTimes go after Adrian.
Do what we did: turn them off. When you find an infected client disable their port on the switch. When they call the helpdesk asking "Why doesn't my internet work?", then you can tell them "Because you are a moron. Fix your shit plz."
Re:Scalability?
on
MIT Roofnet
·
· Score: 2, Insightful
It's cool, but I don't see what else can be done with it than make it a college toy.
How about smaller college campuses? Apartment buildings, maybe? Neighborhoods?
How about redundant rooftop connections between houses for data transfer? Take some of the existing bandwidth from the fiber running to the integrated SLIC in front of the neighborhood and then pump it out to the rooftops of subscribers
Not XP itself that I know of, but Intel LANdesk administrator will allow you to do centralized patch management. If I've read the documentation correctly (we haven't implemented this yet), then you should be able to keep track of what's installed (applications, patches, _anything_ that's been installed) on all the machines managed by LANdesk.
Re:Seriously? Arrest Microsoft, Inc.
on
Blaster Writer Caught
·
· Score: 2, Insightful
So who the hell keeps buying their crap?
Companies that don't want to spend a large amount of money on employees, but don't necessarily mind spending astronimcally on license fees for MegaCorpOS. It's easy to sell windows products to suits because they use windows at home. It's not easy to sell OSS solutions because they immediately associate it with Linux which isn't as expensive as commercial unix solutions and therefore bad.
I have noticed that it's much easier to sell people on OSS/Unix backend solutions that don't require any interaction. We're finally moving our MX off of exchange to sendmail. Sendmail on Solaris, but I wasn't here when they made their initial purchasing decisions.
Start charging the folks who deploy Microsoft for negligence.
I don't like using Microsoft anymore than the next devoted Linux fan, kernel changelog reader, and developer, but I did learn something from last week's virus explosion. After we were down all of Monday, I went to my manager and explained that all of this could have been prevented had we actually used some of the features of using Win2k (group policies, etc). He just shook his head and explained that we were told we couldn't push out updates because they may break installed applications. There are, after all, developers using these machines. *groans* We've since made our case to the appropriate people in charge and can now push out all the updates we want. Prior to sobig.f and msblast/welchia the netadmin department sent out copious e-mails, reminded everyone when they saw them, and even went so far as to put pieces of paper with instructions on the doors to break rooms, the office, etc. None of the end-users patched their machines. E-mails were ignored, pieces of paper all over the office warning about the DCOM exploit and instructions for patching were ignored. The problem is slightly larger than "Microsoft Sucks" IMHO.
How many "UNIX System Administrators" do you know that are running around with exploitable desktops/servers at home/work? Who patches everything they have the day that patches are released? Overall laziness is a much larger problem than Microsoft's inability to write a secure or stable product.
Actually, that's HollywoodOS and I hold the patent on it. I figure there's a market for idiots who want to bang on their keyboard haphazardly and have any number of complex processes happen as a result. I also think that more people than just myself want hexagonal windows to be the standard shape.
Actually the job market for people with experience is pretty good right now. You may take a pay cut, but jobs for seasoned admins are never hard to find.
I have to agree with you here. I recently left my employer of ~4 years because my manager was a moron and the company sucked. Within three weeks I had another job at a much smaller company with better benefits, a real manager, and an excellent work environment. I walk on water here, it's great!:)
You're right though. I would hate to be a college grad right now. I have several friends who graduated from college this year or last and have been looking for a job since or are currently waiting tables. I won the race to (re-)employment, but only because i had 5 years of netadmin experience on my resume with some pretty impressive projects. One of my friends has been out of work for more than a year.
Re:sobig.M kills blacklists?
on
P2P Spam?
·
· Score: 1
I hardly think so. Most administrators of larger mail servers have realized that blacklists are not the way to do spam blocking. Even blacklisting networks is becoming a chore leading to hassles for administrators or, in extreme cases, lawsuits (already/.'d today).
More complex spam abatement filters, such as Brightmail, use complex algorithms to scan incoming e-mail content and identify it as spam. In some cases it's as simple as checking the md5sum of the body of the e-mail. Fortunately, whitelisting, such as TMDA, is becoming more prevelant. If it weren't for spam filtering methods such as these, I'd be getting those hundreds of daily spams in my inbox instead of them going straight to/dev/null.
Re:This is why ISPs are changing their SMTP rules?
on
P2P Spam?
·
· Score: 1
Are your customers using Exchange services? Is there any reason they need to use your hosted e-mail servers. I've never understood this argument against outbound port 25 filtering.
Re:Truly P2P if SOBIG.G contains the spam message
on
P2P Spam?
·
· Score: 2, Interesting
Quite a few national ISP's already do port 25 filtering so that customers connected to their network can only use their relays. What's needed on top of that is outbound spam filtering and virus filtering.
It doesn't stop at the ISP level, though. If Joe Customer gets a copy of Sobig.f in his inbox, opens it, starts spamming everyone in his address book, but is blocked due to the diligent efforts of his ISP. It doesn't stop him from taking his laptop to work and passing it along to all his friends at his office and thus hosing their Microsoft Exchange server with no outbound filtering.
I have no idea what the authors' motives are and I won't try and guess them until they've made their first move. Unless, of course, the first move has already been made. Let's not forget the incredible insecurity of the internet at large due to the presence of so many unpatched systems. At the very least this virus is yet another example of the grossly underestimated flaws in one of the world's vital communication systems.
Have you ever looked at Mars through a telescope from unclouded rural skies? It's breathtaking. The fact that you can clearly see the surface of the planet as well as you can is amazing. It being this close is a pretty cool thing to any astronomer. Granted Voyager did take some great shots of the planet's surface, but I like looking at things with my own eyes.
Slashdot Mirror
Do you have a reference to statute or a precedent that backs that statement up? Okay... no, but I'm not ready to give up yet. It isn't usually the case that data generated by a copyrighted program is automatically assumed to be held under the copyright of the owners of the program. For instance, Microsoft doesn't hold copyright to IP packets that are transmitted by windows machines, even though it is their code that assembles those packets. An interesting point. Wouldn't circumventing STK's copyright protection mechanism (definition used liberally: GetKey) be copyright infringement? Isn't this the same as using deCSS or any other copyright circumvention techniques? The 3rd party vendor is using STK's code to generate error logs and to diagnose hardware/software problems. They're basing their business largely on the unlicensed use of STK's intellectual property (the maintenance code in this case). How is that legal? I read someone mentioning SCO in another thread, but I don't see how this pertains to the SCO trials. This isn't some farfetched claim that STK contributed 2 lines in a sub-routine somewhere... this is proprietary software that is a major contributor to STK's revenue.. and by the looks of their earnings the past few quarters they need all the money they can get. It sucks that they've got a monopoly on the maintenance of the hardware they developed, but whoop-de-freakin-doo. That comes with the territory of buying "enterprise class" hardware, does it not?
The Maintenance Code is copyrighted material and protected intellectual property of StorageTek. The use of the event messages generated by the maintenance code by the 3rd party maintenance vendor is thus copyright infringement. This is an open-and-shut case and shouldn't set a bad precedent in my opinion. It's upholding copyright law.
I would imagine that the early adopters of Wi-Fi were tech savy and thus that the "average" user two years ago was more tech savy than the "average" user today. It's numbers.
There will always be labels. There will always be talented musicians. There will always be people better than the guy writing all his music in fruity-loops and making it sound just like That Trance Track from 1999. The point is: now technology has come to a point where musically talented individuals with some creativity can create music that's at least pleasing to themselves without spending several thousand dollars on hardware and building an in-house studio full of synthesizers, drum machines, mixers, and effects processors. Open publishing is already here and it's call the internet.
recording conversations, television, random noises, or sounds that i find interesting. take an 1/8th" jack from the ear out on the mini to the mic in on my laptop.. then cut it up with soundforge and use the wavs as samples.
I suck at piano and the fact that all I need to make music now is a laptop, a handheld mini-cassette recorder, and a single audio cable makes me happy. Working within a strict budget and being an electronic musician has always been pretty easy. Freeware tools that let you make noise have been around for a while. It's simply much easier and more accessible now.
Since when are composition and melody rad concepts, anyway? I'd hardly consider those ideas radical. What about experimental sound creation? What about twiddling knobs until you create the exact sound that's in your head and then build an idea out of that single sound? What about cutting up samples and putting them together much like the literary styles of Brion Gysin or William S. Burroughs? All easily done on a laptop with a couple of pieces of software.
I've heard more melodies than I care to think about and I think that area's been explored pretty well. I can't imagine what the next progression is for the melody. I can imagine what some of the next steps in sound creation are.
Good production can't make up for bad music, but it can make good music much better.
It's glad to know that more than just idiots are reproducing these days.
Thank you.
I was an Excite@home customer. I'm glad someone closed the holes.
I was a NYTimes customer. I'm glad someone closed the holes.
I was a Yahoo member. I'm glad someone closed the holes.
The fact that these holes existed and the companies weren't doing anything about them (because their admins misconfigured proxies and who knows what else) says to me that they didn't know the holes existed. Look at his targets. Were these 50-employee small businesses that got their IIS web-server hacked? No. They weren't. They were all very large corporations with substantial customer bases that had gaping holes in their security.
The targets were carefully selected and the publicity was purposeful. I doubt he made it public on purpose and I'd hardly call it bragging. This isn't someone getting on EFnet and joining #warez and saying (while holding down the shift-key instead of using caps lock)
# Appears as ADRIAN
ADRIAN: OMG I HAXORED NYTIMES AND PWN3D THEIR PROXZ!
This was someone being professional about what he was doing, or so it would appear, calling up the system administrators and offering to help fix the problem. Not to mention making it publicly known that large American corporations don't care about safe-guarding data like your SSID or credit card numbers. But everyone already knew that, right? I guess nobody cares.
Damage? They owe him their thanks. If you didn't bother reading some of the other articles about his past experience you would have learned that most of the companies were grateful (WorldCom and @Home just to name a couple). The fact that the people at NYTimes are whiny asshats was simply something that was bound to happen sooner or later. Read some more articles and you'll see that some of the SSIDs he got were of some pretty important figures in world politics. I'm sure plenty of powerful people were pissed and expected, if not demanded, that NYTimes go after Adrian.
Do what we did: turn them off. When you find an infected client disable their port on the switch. When they call the helpdesk asking "Why doesn't my internet work?", then you can tell them "Because you are a moron. Fix your shit plz."
How about smaller college campuses? Apartment buildings, maybe? Neighborhoods?
How about redundant rooftop connections between houses for data transfer? Take some of the existing bandwidth from the fiber running to the integrated SLIC in front of the neighborhood and then pump it out to the rooftops of subscribers
Not XP itself that I know of, but Intel LANdesk administrator will allow you to do centralized patch management. If I've read the documentation correctly (we haven't implemented this yet), then you should be able to keep track of what's installed (applications, patches, _anything_ that's been installed) on all the machines managed by LANdesk.
Companies that don't want to spend a large amount of money on employees, but don't necessarily mind spending astronimcally on license fees for MegaCorpOS. It's easy to sell windows products to suits because they use windows at home. It's not easy to sell OSS solutions because they immediately associate it with Linux which isn't as expensive as commercial unix solutions and therefore bad.
I have noticed that it's much easier to sell people on OSS/Unix backend solutions that don't require any interaction. We're finally moving our MX off of exchange to sendmail. Sendmail on Solaris, but I wasn't here when they made their initial purchasing decisions.
Start charging the folks who deploy Microsoft for negligence.
I don't like using Microsoft anymore than the next devoted Linux fan, kernel changelog reader, and developer, but I did learn something from last week's virus explosion. After we were down all of Monday, I went to my manager and explained that all of this could have been prevented had we actually used some of the features of using Win2k (group policies, etc). He just shook his head and explained that we were told we couldn't push out updates because they may break installed applications. There are, after all, developers using these machines. *groans* We've since made our case to the appropriate people in charge and can now push out all the updates we want. Prior to sobig.f and msblast/welchia the netadmin department sent out copious e-mails, reminded everyone when they saw them, and even went so far as to put pieces of paper with instructions on the doors to break rooms, the office, etc. None of the end-users patched their machines. E-mails were ignored, pieces of paper all over the office warning about the DCOM exploit and instructions for patching were ignored. The problem is slightly larger than "Microsoft Sucks" IMHO.
How many "UNIX System Administrators" do you know that are running around with exploitable desktops/servers at home/work? Who patches everything they have the day that patches are released? Overall laziness is a much larger problem than Microsoft's inability to write a secure or stable product.
Actually, that's HollywoodOS and I hold the patent on it. I figure there's a market for idiots who want to bang on their keyboard haphazardly and have any number of complex processes happen as a result. I also think that more people than just myself want hexagonal windows to be the standard shape.
Anyone want to start a project?
If I cna raed adn wrtei wrods wiht letrtes mvoed aruodn tihs asleiy deos taht maen i ma dylsexic?
I have to agree with you here. I recently left my employer of ~4 years because my manager was a moron and the company sucked. Within three weeks I had another job at a much smaller company with better benefits, a real manager, and an excellent work environment. I walk on water here, it's great! :)
You're right though. I would hate to be a college grad right now. I have several friends who graduated from college this year or last and have been looking for a job since or are currently waiting tables. I won the race to (re-)employment, but only because i had 5 years of netadmin experience on my resume with some pretty impressive projects. One of my friends has been out of work for more than a year.
I hardly think so. Most administrators of larger mail servers have realized that blacklists are not the way to do spam blocking. Even blacklisting networks is becoming a chore leading to hassles for administrators or, in extreme cases, lawsuits (already /.'d today).
More complex spam abatement filters, such as Brightmail, use complex algorithms to scan incoming e-mail content and identify it as spam. In some cases it's as simple as checking the md5sum of the body of the e-mail. Fortunately, whitelisting, such as TMDA, is becoming more prevelant. If it weren't for spam filtering methods such as these, I'd be getting those hundreds of daily spams in my inbox instead of them going straight to /dev/null.
Are your customers using Exchange services? Is there any reason they need to use your hosted e-mail servers. I've never understood this argument against outbound port 25 filtering.
Quite a few national ISP's already do port 25 filtering so that customers connected to their network can only use their relays. What's needed on top of that is outbound spam filtering and virus filtering. It doesn't stop at the ISP level, though. If Joe Customer gets a copy of Sobig.f in his inbox, opens it, starts spamming everyone in his address book, but is blocked due to the diligent efforts of his ISP. It doesn't stop him from taking his laptop to work and passing it along to all his friends at his office and thus hosing their Microsoft Exchange server with no outbound filtering. I have no idea what the authors' motives are and I won't try and guess them until they've made their first move. Unless, of course, the first move has already been made. Let's not forget the incredible insecurity of the internet at large due to the presence of so many unpatched systems. At the very least this virus is yet another example of the grossly underestimated flaws in one of the world's vital communication systems.
Have you ever looked at Mars through a telescope from unclouded rural skies? It's breathtaking. The fact that you can clearly see the surface of the planet as well as you can is amazing. It being this close is a pretty cool thing to any astronomer. Granted Voyager did take some great shots of the planet's surface, but I like looking at things with my own eyes.