Re: So, in simple terms
It stupidity to assume the network itself is secure.
Passing any password in plaintext is a MASSIVE mistake.
741 publicly visible posts • joined 17 Nov 2012
NRL certainly can. Been there seen that. In our group as soon as we were notified (as in, management saw/read the report, or sometimes even rumors) the passwords can be forced.
the normal replacement was every 90 days, as measured from last password change. But it could be reset to any interval.
Not 'industry standards'.
It is Microsoft standards masquerading as "industry standards".
Microsoft software is the poorest designed for security. Passwords stored in plaintext, hashes used for authentication, falling back to known broken authentication... executable everything...
The only way to win (in security) is to not use Microsoft software.
Yes, paraphrased :-) but still true.
It actually isn't.
Not all of the code is used for a particular instance - For example, none of the ARM code, or 68000, or Power, or IBM 370, or the Z code is used when you are X86 based.
But they ARE available if you want. The kernel you get is actually smaller than Windows. The only things that get added are driver and filesystem modules for your specific use.
Thus, no bloat.
Now when it comes to distributions, you have a different source of bloat, and it isn't the kernel.
Even that won't work - Linux is GPLv2.
And will always be GPLv2.
The most they could do is fork Linux... And they don't even need to depose Linus.
It would be quite hard to "wrest Linux copyright authority from all the Linux and GNU copyright stakeholders" - some are dead.
You can't change the license without the permission - and you can't get it from them. Nor will you be able to get it from all the thousands of contributors.
Actually not.
There were so many forks of UNIX that it devolved. Now there are three varieties of BSD, and a few dozen varieties of UNIX (one for each vendor), and none of the kernels are all that cross compatible. Just try taking a driver from AIX and add it to a Mac OS/X.... Not a chance. Try taking a driver from Solaris and add it to AIX or OS/X (or even any of the BSD systems)... not a chance.
Contrast that with Linux. A hundred or so distributions - yet the linux kernel is cross compatible with all of them.
There was a BIG difference for the lawyers...
The IBM lawyers were not presuming to defend Linux. They were defending IBM against the baseless attack of SCO.
Kuhn was/is just trying to drum up lawsuits.
Eben Moglen has a different approach. Instead of lawsuits he works with both the developers and the "accused" to eliminate the lawsuit - which is damaging to both parties in a lawsuit.
wget
is broken and should DIE, dev tells Microsoft
The order is a bit off:
1. change it so the Windows version is not compliant with the non-microsoft version
2. make it available in Windows
3. claim the Windows version is compliant
4. refuse to make the Windows version compliant
5. push windows version of said item
6. call non-Microsoft version "broken"
Hey - works for AD, being broken with LDAP/Kerberos/Bind.
Microsoft doesn't even know how its own software works as MS had to get help from the Samba project for the EU mandated documentation.
That depends on your definition of "limited".
There was a lot of damage caused by above ground testing (designed to minimize damage and investigate the damage there was). And this would NOT be testing - but deliberately placed detonations; designed specifically to kill people. Also even one detonation would be several times larger than the tests.
"It doesn't have a proper modular device driver system."
Unlike Windows that doesn't support backward compatibility with device drivers, and changes "modular device drivers" at the drop of a hat, forcing OEMs to do the work of conversion all the time.
"It just grows including support for every nasty and not so nasty processor and chipset that comes out."
Unlike Windows that only runs on ONE processor and a little bit on ONE ARM processor architecture.