Okay, I was a little off base. Here's the address from a year ago: http://images.ucomics.com/comics/ch/1991/ch910317. gif
So the script would be :
http://images.ucomics.com/comics/ch/YYYY/chYYMMDD. gif, and yes, they are all available.
I think that the comic started in November 87, so you should be able to pound out a perl script in about 5 minutes.
Actually, you can view them all for free. Their image directory is not protected, you can wget the whole damned thing if you know the naming convention, and it's not difficult to figure out(it's something like CH + YYYY + MM + DD.gif).
A perl script and some time you'd have the whole thing in an hour.
As long as it's done right, then there would be no problems implementing voice/data and video over it. Odds are they are going to supply a circuit, and you do whatever you want with it. There doesn't seem to be a cap for the local access, so a lan extension would not be unheard of. Of course, you'll probably have to pony up for some decent routers.
No, you just have to hook up your fuel hose, and feed it back into the electrics, which will split it into H2 and 02, which will give you more fuel, which will make more water, which will make you pee...
You'd be driving for free!
Right now we have a solution that works. It's been working for 8 years, and it's paid for. That's why I'm supporting it. I'm not going to put any money into it, and when crunch-time comes, we'll see how well progress runs on slack. Until then, I'm keeping the steaming dog turd in my server room.
I know a lot of linux users who have installed Solaris in organizations for one reason: One throat to choke. It is a fundamental part of business, that will never change. RedHat has made great strides in filling this void in the linux marketplace. They do take responsibility for their product, and that allows businesses to consider it viable.
Is having accountability necessary with linux? Yes and no. How many times has it been fixed for no other reason than it was broken? Countless times. If Linus, Alan Cox, Richard Stallman, Bill Gates, Larry Wall, and any other big shots you can name were to die in a firey plane crash on their way to a convention, would M$, Linux, Perl, etc... go on? Of course. There are people in the wings ready to take on the challenges that lie ahead. But tell this to a businessman. M$ is really the only tangible business, therefore it would go on. Everything else would cease to exist, had it even existed to him in the first place.
The world in general is not farmiliar with the concepts that we have started. Many people see our ideas as a technocratic society as 'alien' and 'radical'. How can nobody own linux? That's crazy talk! Are you some kind of pinko commie tree hugging hippie?
There has to be a compromise between our ideals and the sometimes irrational behaviors of the business world. People are willing to buy what we've been giving away, yet they're not willing to accept it as a gift. Until they are, there will be a market for Unices, and people who go through all the trouble of 'selling' linux.
The only problem with this is scalability. Sure SMTP has had its problems, but the nice thing about SMTP is you control the server. You control how fast mail comes in, from who it comes in, how fast people can give you e-mail, and how fast you give it out to subscribers/recipients. All of these schemes seem to remove that control from your machine.
Instead of adding a band-aid solution to spam, let's sit down and list what we need for an a-mail server. Scalability, reliability, fault tolerance, expandability and distributed servers top my list. I'm sure that there are other better ones out there too. If you're going to revamp the protocol, try to get everything in the first time, and let's try to get it right.
You really shoudn't trust netstat on the same machine. It's good practice to get one on a laptop or something that you don't leave plugged in. Also a snort machine with a 1 way ethernet cable will catch things that a trojaned netstat, ps, lsof won't.
A good trojan woll remove all your tools to see if it's there.
And BTW, a stateful firewall can also limit which outbound ports you need open.
Uhm, If that be the case, then houw many webpages can you serve at once? The answer is ONE.
Your firewall has to allow your machines to initiate outbound connections, otherwise things would cease to work. Web services start on port 80, they don't continue there. So Sure you have your machines firewalled, but if you're serious about how your firewall works, then check the rules. I dare you to firewall every port outbound other than what your servers are publishing. You'll learn quickly how TCP/IP works.
Re:You have to think like an admin
on
Windows Rootkits
·
· Score: 1
Exactly. This is not a new concept. Confidence men and crooks have been doing it for thousands of years. Pretend to be part of the crowd, get in to where you wouldn't normally, and get what you want.
The medium may be new, but the old tricks are still the best.
That does not defeat the rootkit, that only makes you feel better. How about one that can get through your firewall. Maybe cycle through all ports until it can make communication? Hide with the rest of the traffic?
The best way to defeat this kind of trojan is to prevent it from being installed.
You have to think like an admin
on
Windows Rootkits
·
· Score: 3, Interesting
From trusted ports to trusted ports work for most firewalls. Another way is to control by e-mail.
You could even make it look like DNS queries if you wanted. The trick is not getting caught on the way in. Once in, there's not a lot holding you back.
Slashdot Mirror
If you can't have military-level accuracy, you just need a bomb that would make up the difference.
I'm getting the exact same thing now.
/.
Honestly it worked this morning. Their tech support must read
I've pulled the whole thing numerous times. Looks like I'll have to put up a mirror.
Actually, only the luddites are restricted to how far they can go back. I posted the solution a bit further up.
y ymmdd. gif
Mass wget
http://images.ucomics.com/comics/ch/YYYY/ch
Okay, I was a little off base. Here's the address from a year ago: http://images.ucomics.com/comics/ch/1991/ch910317. gif
So the script would be :
http://images.ucomics.com/comics/ch/YYYY/chYYMMDD. gif, and yes, they are all available.
I think that the comic started in November 87, so you should be able to pound out a perl script in about 5 minutes.
Actually, you can view them all for free. Their image directory is not protected, you can wget the whole damned thing if you know the naming convention, and it's not difficult to figure out(it's something like CH + YYYY + MM + DD.gif). A perl script and some time you'd have the whole thing in an hour.
Kindergarten won't be so bad. Have you ever picked on a guy in a tank?
Although 5th grade might be rough. Reminds me of Bonzai Kitty.
I've had the same thing, slackware w/ KDE sources. ./configure && make , su, make install works for me.
That's the best decision you ever made.
When we come up with a linux version that does everything you ask for, you won't have to buy it. We'll give it to you.
As long as it's done right, then there would be no problems implementing voice/data and video over it. Odds are they are going to supply a circuit, and you do whatever you want with it. There doesn't seem to be a cap for the local access, so a lan extension would not be unheard of. Of course, you'll probably have to pony up for some decent routers.
No, you just have to hook up your fuel hose, and feed it back into the electrics, which will split it into H2 and 02, which will give you more fuel, which will make more water, which will make you pee... You'd be driving for free!
I am my own evidence.
As proven here, everyone has the right to free speech, but some of us should not be given the medium to exercise that voice.
The last thing that I want are a bunch of gaotse pics on my tv, and trolls on my radio. The news is bad enough.
He could still screw an intern. That's shown to help.
Naw, we'll just blame it on Al-Queida and Sadaam.
And Calderra/SCO will form the asshole.
Right now we have a solution that works. It's been working for 8 years, and it's paid for. That's why I'm supporting it. I'm not going to put any money into it, and when crunch-time comes, we'll see how well progress runs on slack. Until then, I'm keeping the steaming dog turd in my server room.
I know a lot of linux users who have installed Solaris in organizations for one reason: One throat to choke. It is a fundamental part of business, that will never change. RedHat has made great strides in filling this void in the linux marketplace. They do take responsibility for their product, and that allows businesses to consider it viable.
Is having accountability necessary with linux? Yes and no. How many times has it been fixed for no other reason than it was broken? Countless times. If Linus, Alan Cox, Richard Stallman, Bill Gates, Larry Wall, and any other big shots you can name were to die in a firey plane crash on their way to a convention, would M$, Linux, Perl, etc... go on? Of course. There are people in the wings ready to take on the challenges that lie ahead. But tell this to a businessman. M$ is really the only tangible business, therefore it would go on. Everything else would cease to exist, had it even existed to him in the first place.
The world in general is not farmiliar with the concepts that we have started. Many people see our ideas as a technocratic society as 'alien' and 'radical'. How can nobody own linux? That's crazy talk! Are you some kind of pinko commie tree hugging hippie?
There has to be a compromise between our ideals and the sometimes irrational behaviors of the business world. People are willing to buy what we've been giving away, yet they're not willing to accept it as a gift. Until they are, there will be a market for Unices, and people who go through all the trouble of 'selling' linux.
The only problem with this is scalability. Sure SMTP has had its problems, but the nice thing about SMTP is you control the server. You control how fast mail comes in, from who it comes in, how fast people can give you e-mail, and how fast you give it out to subscribers/recipients. All of these schemes seem to remove that control from your machine.
Instead of adding a band-aid solution to spam, let's sit down and list what we need for an a-mail server. Scalability, reliability, fault tolerance, expandability and distributed servers top my list. I'm sure that there are other better ones out there too. If you're going to revamp the protocol, try to get everything in the first time, and let's try to get it right.
Unfortunately, these dinosours give us something that we need: Choice. I really don't want to see the whole computer industry to be M$ or RedHat.
You really shoudn't trust netstat on the same machine. It's good practice to get one on a laptop or something that you don't leave plugged in. Also a snort machine with a 1 way ethernet cable will catch things that a trojaned netstat, ps, lsof won't.
A good trojan woll remove all your tools to see if it's there.
And BTW, a stateful firewall can also limit which outbound ports you need open.
Uhm, If that be the case, then houw many webpages can you serve at once? The answer is ONE. Your firewall has to allow your machines to initiate outbound connections, otherwise things would cease to work. Web services start on port 80, they don't continue there. So Sure you have your machines firewalled, but if you're serious about how your firewall works, then check the rules. I dare you to firewall every port outbound other than what your servers are publishing. You'll learn quickly how TCP/IP works.
Exactly. This is not a new concept. Confidence men and crooks have been doing it for thousands of years. Pretend to be part of the crowd, get in to where you wouldn't normally, and get what you want.
The medium may be new, but the old tricks are still the best.
That does not defeat the rootkit, that only makes you feel better. How about one that can get through your firewall. Maybe cycle through all ports until it can make communication? Hide with the rest of the traffic?
The best way to defeat this kind of trojan is to prevent it from being installed.
From trusted ports to trusted ports work for most firewalls. Another way is to control by e-mail. You could even make it look like DNS queries if you wanted. The trick is not getting caught on the way in. Once in, there's not a lot holding you back.