True, but LambdaMOO's server code is now hosted on SourceForge. I think they require some sort of open source license for all hosted projects.
Yes. And I believe that this is pretty much considered an open source license because it allows changes and redistribution. The only issue is that he wants you to send him your name and address (which can be a good idea, like for example if some massively horrible bug is found).
The LambdaMOO admins occasionally make dumps of the live Lambda database and give away the core bits.
I think that last time that has happened was 1999. There are other more recent third party cores, which are generally based of off LambdaCore.
Copyright (c) 1995, 1996 Xerox Corporation. All rights reserved. Portions of this code were written by Stephen White, aka ghond. Use and copying of this software and preparation of derivative works based upon this software are permitted. Any distribution of this software or derivative works must comply with all applicable United States export control laws. This software is made available AS IS, and Xerox Corporation makes no warranty about the software, its performance or its conformity to any specification. Any person obtaining a copy of this software is requested to send their name and post office or electronic mail address to: Pavel Curtis Xerox PARC 3333 Coyote Hill Rd. Palo Alto, CA 94304 Pavel@Xerox.Com
(It isn't quite formatted correctly, but it'll do....)
Anyhow, the Xerox thing is that Xerox owns the code (Pavel Curtis wrote most of it while under the employ of Xerox)
Yep. I can see car chase scenes in movies becoming really boring very soon. Like the guy who robs a bank, runs to his getaway car, blows real hard in the breathalizer shouting COME ON! COME ON! then, 30 seconds later, puts the pedal to the metal.
What about the rolling tests? Let's say there is some chase scene, and all of a sudden, one of the main characters slows down and starts blowing real hard into the breathalizer without watching where's he's going?
mod -1 for being a troll post, openBSD is alive and well... and its not the linux kernel, its the BSD kernel you dumbshit.
Maybe you don't understand, but there has to be an attacker. You have to have a specific modification in the linux kernel of the linux machine (attacking machine) to successfully attack the openbsd machine (victem). Probably you could set up a FreeBSD machine, or even another OpenBSD machine to do the attack. Just a linux machine was used to attack in the example.
What the hell is a "chief creative officer"? That sounds about as made up as a "chief happiness officer".
What's to stop a corporation to have someone to handle their er, 'creative' side of the business? It may be almost as important as the other facets of a business, and something they shouldn't neglect. Really, they can have as many types of chief whatever officers as they want.
This is boring! It's all BSD and Linux! It would be really interesting to see how some of the new and completely from scratch open source stuff does too.
What the hell? Are you talking about HURD?
I doubt it would do as well as most of the others... I think it'd probably suck..but I don't know how well it'd really do..?
Although HURD isn't terribly new...it's been a GNU project for a while...
This is only vaguely on-topic, but SCO seems to have changed their webserver to openbsd or netbsd. At least, Netcraft says so. Although, that could mean more than one thing (such as they stuck another box in front to take the blunt of the impending attack).
Or wait, does that mean they really plan on going after the *BSDs now?
To maintain the maximum amount of portability, don't say/bin/bash. Say/bin/sh instead.
Also, don't assume true is located at/bin/true. On some systems in may be located in/usr/bin/true, or in some cases, somewhere else entirely. You'll probably be better off using ':'
There is still no substitution for good (that is with the security in mind) programming practices. And of course readily available information about vulnerabilities.
If you have a 'monoculture', you have no choice but to choose whatever one thing is available...you're stuck with it, so if it has poor programming involved, too bad. With a diversity of programs available, you can choose the best.
....What do you mean no driver? It should just look like a normal (USB) drive to the system, except quite a bit bigger than usual. (I dunno about firewire support in linux, or anything else firewire for that matter)
System V from the BSD OSes is public domain. That has been decided by a court of law.
Noo....As far as I know headers might public domain (only one way to implement it, yada yada), but the rest is still copyrighted. The difference is the license the BSDs are distributed under is extremely unrestricting. Free of most all restrictions and public domain are different things.
I guess if you do get in you should be free sift through my dirty landry. But please be respectly as Adrian Lamo was and tell me what I need to fix. I'll even offer to pay you!
Would it too much to have people knock first (ie drop me an email)? And if we are gonna praise people for poking around to get us to enhance security, why do even HAVE security in the first place?
Back then people sent passwords in plain text, there were no firewalls, nfs was as vulnerable as eggs laid on a freeway. Practically nobody paid any attention to security issues.
Back then, noone needed to.
[...] So again I say - thank Gawd for the crakers and guys - keep up the good work. Keep pounding home the point that people must pay attention to proper security. Without consequences for lax security it is clear they won't do a damn thing.
And without crackers we still wouldn't have to worry about it. If certain people decide to cause trouble, then we defend against it. Nothing more.
Put it this way: Noone needed locks. Noone needed to worry about that. Then one night, a thief broke into everyone's house...and everyone all got locks because of it. Should we call the thief a hero?
This has got to be the least-cared-about story on Slashdot, ever. =)
Yes it looks like it. ekkoBSD might be more interesting is if we had a nice phrase to go with it (like how portability goes with netbsd and so forth... we even know dfbsd aims to be high performance). We still don't -know- what ekkoBSD is for. My best guess right now is quick setup.
Of course, having a nice phrase, motto, whatever isn't a guarentee to stardom.
Everyone knows you gotta have expensive video card for your games, which is why I got the ATI Radeon 9500 ASC. You know, the one specially designed to render games like nethack. It works great!!
Sure enough, their Terms of Service require me to prevent others from obtaining my login/password. It goes on to say that if someone steals it, there is basically no way to reverse their actions.
Well, -you- are trying to prevent others from obtaining it while they might not be. If something does happen, point fingers. You kept up your end, and mentioning their problem then might help. And my guess is you'll have an advantage legally?
As I write, freshports says that there are 10022 ports. However, 62 of those are marked as broken, and 4 are marked as forbidden, so perhaps the celebration is premature. Only 44 ports need to be fixed!
Actually, it isn't that bad. Some ports report they are broken based on versions (like version of fbsd, perl, etc). For example, take a look at the Makefile of gnump3d. It requires a certain version of perl before it'll be 'unbroken'. Then again, it may be worse, because some don't compile, but aren't labeled as BROKEN. bento is a great place to find out which ports compile and which don't.
It's running Windows XP, so we have a bunch of slow down right there. I had a 200ish mhz laptop with FreeBSD and a 400mhz WinNT machine running the same program, and the FreeBSD machine ran it about twice as fast. Moral of the Story: Operating systems can add a lot of overhead.
Of course, I don't know what the overhead of OSX is against XP, but I think it's something I had to point out.
It's premature to call the failure to hear the initial signal as a "major setback".
People forget it still has to recharge itself. Upon landing it should probably only have enough power to open up and expose its solar panels. Once it has enough power, then it can send us a signal.
Well, if you do not believe in global warming, then you are in agreement the vast *minority* of scientists the world over. So, censuring a high level goverment scientist that comes out and blatantly supports the "wrong side" of the issue should be expected.
Well, if you don't believe in global warming, you would have to believe the ice age never occurred. Of course, the real issue at hand is how much us humans cause in addition to natural random warming.
Slashdot Mirror
Mr. de Raadt says...
They include a web server with/in the OS? *shudder*
True, but LambdaMOO's server code is now hosted on SourceForge. I think they require some sort of open source license for all hosted projects.
Yes. And I believe that this is pretty much considered an open source license because it allows changes and redistribution. The only issue is that he wants you to send him your name and address (which can be a good idea, like for example if some massively horrible bug is found).
The LambdaMOO admins occasionally make dumps of the live Lambda database and give away the core bits.
I think that last time that has happened was 1999. There are other more recent third party cores, which are generally based of off LambdaCore.
Anyhow, the Xerox thing is that Xerox owns the code (Pavel Curtis wrote most of it while under the employ of Xerox)
Yep. I can see car chase scenes in movies becoming really boring very soon. Like the guy who robs a bank, runs to his getaway car, blows real hard in the breathalizer shouting COME ON! COME ON! then, 30 seconds later, puts the pedal to the metal.
What about the rolling tests? Let's say there is some chase scene, and all of a sudden, one of the main characters slows down and starts blowing real hard into the breathalizer without watching where's he's going?
mod -1 for being a troll post, openBSD is alive and well... and its not the linux kernel, its the BSD kernel you dumbshit.
Maybe you don't understand, but there has to be an attacker. You have to have a specific modification in the linux kernel of the linux machine (attacking machine) to successfully attack the openbsd machine (victem). Probably you could set up a FreeBSD machine, or even another OpenBSD machine to do the attack. Just a linux machine was used to attack in the example.
Did you even RTFA?
What the hell is a "chief creative officer"? That sounds about as made up as a "chief happiness officer".
What's to stop a corporation to have someone to handle their er, 'creative' side of the business? It may be almost as important as the other facets of a business, and something they shouldn't neglect. Really, they can have as many types of chief whatever officers as they want.
This is boring! It's all BSD and Linux! It would be really interesting to see how some of the new and completely from scratch open source stuff does too.
What the hell? Are you talking about HURD?
I doubt it would do as well as most of the others... I think it'd probably suck..but I don't know how well it'd really do..?
Although HURD isn't terribly new...it's been a GNU project for a while...
This is only vaguely on-topic, but SCO seems to have changed their webserver to openbsd or netbsd. At least, Netcraft says so. Although, that could mean more than one thing (such as they stuck another box in front to take the blunt of the impending attack).
Or wait, does that mean they really plan on going after the *BSDs now?
To maintain the maximum amount of portability, don't say /bin/bash. Say /bin/sh instead.
Also, don't assume true is located at /bin/true. On some systems in may be located in /usr/bin/true, or in some cases, somewhere else entirely. You'll probably be better off using ':'
Now we have:
#!/bin/shwhile
do
wget -r -l10 http://www.sco.com -O
done
exit 0; # really unnecessary
There is still no substitution for good (that is with the security in mind) programming practices. And of course readily available information about vulnerabilities.
If you have a 'monoculture', you have no choice but to choose whatever one thing is available...you're stuck with it, so if it has poor programming involved, too bad. With a diversity of programs available, you can choose the best.
It's a cartoon devil.
No. It isn't. It's a daemon.
No Linux driver ...
....What do you mean no driver? It should just look like a normal (USB) drive to the system, except quite a bit bigger than usual. (I dunno about firewire support in linux, or anything else firewire for that matter)
System V from the BSD OSes is public domain. That has been decided by a court of law.
Noo....As far as I know headers might public domain (only one way to implement it, yada yada), but the rest is still copyrighted. The difference is the license the BSDs are distributed under is extremely unrestricting. Free of most all restrictions and public domain are different things.
I guess if you do get in you should be free sift through my dirty landry. But please be respectly as Adrian Lamo was and tell me what I need to fix. I'll even offer to pay you!
Would it too much to have people knock first (ie drop me an email)? And if we are gonna praise people for poking around to get us to enhance security, why do even HAVE security in the first place?
Back then people sent passwords in plain text, there were no firewalls, nfs was as vulnerable as eggs laid on a freeway. Practically nobody paid any attention to security issues.
Back then, noone needed to.
[...] So again I say - thank Gawd for the crakers and guys - keep up the good work. Keep pounding home the point that people must pay attention to proper security. Without consequences for lax security it is clear they won't do a damn thing.
And without crackers we still wouldn't have to worry about it. If certain people decide to cause trouble, then we defend against it. Nothing more.
Put it this way: Noone needed locks. Noone needed to worry about that. Then one night, a thief broke into everyone's house...and everyone all got locks because of it. Should we call the thief a hero?
This has got to be the least-cared-about story on Slashdot, ever. =)
Yes it looks like it. ekkoBSD might be more interesting is if we had a nice phrase to go with it (like how portability goes with netbsd and so forth... we even know dfbsd aims to be high performance). We still don't -know- what ekkoBSD is for. My best guess right now is quick setup.
Of course, having a nice phrase, motto, whatever isn't a guarentee to stardom.
Everyone knows you gotta have expensive video card for your games, which is why I got the ATI Radeon 9500 ASC. You know, the one specially designed to render games like nethack. It works great!!
Sure enough, their Terms of Service require me to prevent others from obtaining my login/password. It goes on to say that if someone steals it, there is basically no way to reverse their actions.
Well, -you- are trying to prevent others from obtaining it while they might not be. If something does happen, point fingers. You kept up your end, and mentioning their problem then might help. And my guess is you'll have an advantage legally?As I write, freshports says that there are 10022 ports. However, 62 of those are marked as broken, and 4 are marked as forbidden, so perhaps the celebration is premature. Only 44 ports need to be fixed!
Actually, it isn't that bad. Some ports report they are broken based on versions (like version of fbsd, perl, etc). For example, take a look at the Makefile of gnump3d. It requires a certain version of perl before it'll be 'unbroken'. Then again, it may be worse, because some don't compile, but aren't labeled as BROKEN. bento is a great place to find out which ports compile and which don't.
It's running Windows XP, so we have a bunch of slow down right there. I had a 200ish mhz laptop with FreeBSD and a 400mhz WinNT machine running the same program, and the FreeBSD machine ran it about twice as fast. Moral of the Story: Operating systems can add a lot of overhead.
Of course, I don't know what the overhead of OSX is against XP, but I think it's something I had to point out.
Yes..msdn would be mistake #1.
It's premature to call the failure to hear the initial signal as a "major setback".
People forget it still has to recharge itself. Upon landing it should probably only have enough power to open up and expose its solar panels. Once it has enough power, then it can send us a signal.
Well, if you do not believe in global warming, then you are in agreement the vast *minority* of scientists the world over. So, censuring a high level goverment scientist that comes out and blatantly supports the "wrong side" of the issue should be expected.
Well, if you don't believe in global warming, you would have to believe the ice age never occurred. Of course, the real issue at hand is how much us humans cause in addition to natural random warming.
Only 2 more years until shes legal, boys ;)
Quick...let's start a countdown site!
(er..running perl of course?)
You don't want to touch that. I've heard she's hairy.
Perl...hairy? naw...bison is hairy. (I always did personally prefer yacc)