With bios-protected boot sectors? Some AMI bioses has Virus protect feature, that, if turned on, disallows all writes to boot sector. You cannot avoid that feature except turning it off in BIOS. What this software will do? (Really, I don't understand why and who use that TurboTAX, etc. Paid preparers are not so much expensive, but you have a other people opinion on the tax and an additional person to whom the IRS can speak).
I think even 5% of all patent lawyers has about 2 times more weight and lobbying options on Capitol Hill than all slashdot readers and EFF together. So THEIR word and THEIR money are much more important...
For enterprize? Why not Erlang? At least it's fault tolerant and runs well 24/7. Production times is much faster using it than using Java. It can be combined with Java, Python, it has native CORBA, native fault-tolerant built-in database.
BTW, moving from http to https is MUCH easier than moving from ftp to... what? ftp has no corresponding widely used secure protocol,sftp is special case and is not widely accepted.
Case law is trying to make system consistent: a judgement made by one judge should be the same as a judgement made by another. But as time passes, case file becomes huge and harder to search, thus making an unnessesary strain on legal system and its accessibility.
Case law should be repealed at all. if that happens, you'll need to get only the law texts itself, and that will be enough.
Ok. Assume we found some "Smoldering guns". To whom shall we show the evidence? And more important, would that "who" who grant the patents be hearing us?
Did anyone notice that he in the article mentioned Apache, postfix and PostgreSQL? But those packets are NOT GPL! And he showed them as most brilliant examples of open source!.
At least two Soyuz flights failed in the mid 70s. In both cases the rocked blowed up and safety system worked, ejecting cosmonauts, who experienced 20g forces on arrival. In one situation cosmonauts were pulled to a mountain slope. No casualties, fortunately and because of a good safety system.
" for example, as one part of a transport system, you could hypothesize that a seamless body built out of (say) 1000-times as strong self-sealing materials comprising millions of layers of ablative and structural thin film, with a passive self-righting shape, might not have any problem at all in dealing with reentry conditions."
The "service port" ideology itself is in some conflict with the layer model. If we obsolete "service ports" and assume that we have HTTP as the one and only transport protocol - security tasks will be much easier to maintain. Writing TCP and UDP application SECURELY is much harder than writing the corresponding HTTP based application, HTTP and SOAP/XMLRPC provide support for much more reliable and secure application than TCP/IP So lets leave only DNS and routing for networks, and only HTTP for transport. The only exception MAY BE the real-time applications, but it's also an arguable topic.
At least I can open only one port on machine (443) and be sure that I'll need to worry only on security of httpd server and not of the security of TWO servers - sshd and httpd. Firewall-only security does not work - Slapper worm showed it in great sight. Applications and hosts should be secure, not networks.
It seems to me that non-Microsoft companies that suffer from the worm can try to sue Microsoft for negligence and lost of profits. They didn't sign anything like EULA that limits their right to sue MS. (I am not a lawyer and this cannot be seen as legal advice).
>you probably think UNIX is a great model with >only 2 priv levels, nothing and >absofuckinglutelyeverything. No. I am not. It is my opinion that there were a lot of good systems before (you know who) starts to create unmanageable from the security point of view systems like RSX,VMS, Windows NT... Those systems are common in following:
- a huge and unmanageable Discretory Access Control structure (ACL and privileges).
- a lack of ability to create virtual machine. or good isolation between processes.
- No Mandatory Access control structures or just rudiments of that.
- No information labelling.
- An enormous amount of subjects and objects of access.
For good systems I can account, for example RSTS/E, TSX. Or even mainframes' OSes (OS 370, VM/SP). May be CRAY UNICOS.
Really... OpenVMS has a VERY BAD security. If you leave SYSTEM/SYSTEM on login, it allow you everything. And also it has a privilege "grant yourself any privilege:)" Its logging is OK, though. Does it have information labelling? That versions I saw, nope. May be some hardened versions? OpenVMS need a administrator genius to be secure, systems with a really good security should allow a relatively dumb user to administer them securely.
The astronauts are relatively safe now. They have a sojuz docked to the ISS. And they can use it any time. A sojuz can accomodate 3 people. No launches are needed.
With bios-protected boot sectors?
Some AMI bioses has Virus protect feature, that,
if turned on, disallows all writes to boot sector.
You cannot avoid that feature except turning it off in BIOS.
What this software will do?
(Really, I don't understand why and who use that TurboTAX, etc. Paid preparers are not so much expensive, but you have a other people opinion on the tax and an additional person to whom the IRS can speak).
I think even 5% of all patent lawyers has about 2 times more weight and lobbying options on Capitol Hill than all slashdot readers and EFF together.
So THEIR word and THEIR money are much more important...
For enterprize? Why not Erlang?
At least it's fault tolerant and runs well 24/7.
Production times is much faster using it than using Java.
It can be combined with Java, Python, it has native CORBA,
native fault-tolerant built-in database.
I mistakenly read your post as
"M$ condemns this".
RedHat certifies government!
BTW, moving from http to https is MUCH easier than
moving from ftp to... what? ftp has no corresponding
widely used secure protocol,sftp is special case and
is not widely accepted.
that US legal system is flawed.
Case law is trying to make system consistent:
a judgement made by one judge should be the same
as a judgement made by another.
But as time passes, case file becomes huge and
harder to search, thus making an unnessesary strain on legal system and its accessibility.
Case law should be repealed at all.
if that happens, you'll need to get only the
law texts itself, and that will be enough.
Because magician's black boxes, that usually
contained some enigmas, were usually black.
Ok. Assume we found some "Smoldering guns".
To whom shall we show the evidence?
And more important, would that "who" who grant
the patents be hearing us?
Did anyone notice
that he in the article mentioned Apache, postfix
and PostgreSQL?
But those packets are NOT GPL! And
he showed them as most brilliant examples of open
source!.
Fatalities were on earth surface,
service people were affected by the blast.
No passengers of Souz died.
At least two Soyuz flights failed in the mid
70s. In both cases the rocked blowed up and
safety system worked, ejecting cosmonauts,
who experienced 20g forces on arrival.
In one situation cosmonauts were pulled to
a mountain slope.
No casualties, fortunately and because of
a good safety system.
>The correct machine for the job runs your code, >be it your desktop, the server, the toaster down >the hall in building 2
In Linux you can have it by running
openMosix (openmosix.sf.net)
This
" for example, as one part of a transport system, you could hypothesize that a seamless body built out of (say) 1000-times as strong self-sealing materials comprising millions of layers of ablative and structural thin film, with a passive self-righting shape, might not have any problem at all in dealing with reentry conditions."
is SOYUZ MODULE!
The "service port" ideology itself is in some conflict with the layer model.
If we obsolete "service ports" and assume that we have HTTP
as the one and only transport protocol - security
tasks will be much easier to maintain.
Writing TCP and UDP application SECURELY is much harder than writing the corresponding HTTP based application,
HTTP and SOAP/XMLRPC provide support for much more reliable and secure application than TCP/IP
So lets leave only DNS and routing for networks,
and only HTTP for transport.
The only exception MAY BE the real-time applications, but it's also an arguable topic.
At least I can open only one port on machine (443) and
be sure that I'll need to worry only on security of httpd server and not of the security of TWO servers - sshd and httpd.
Firewall-only security does not work - Slapper worm showed it in great sight. Applications and hosts should be
secure, not networks.
Just curious: what is the eggdrop bot?
It seems to me that non-Microsoft companies that
suffer from the worm can try to sue Microsoft for
negligence and lost of profits.
They didn't sign anything like EULA that
limits their right to sue MS.
(I am not a lawyer and this cannot be seen as legal advice).
>you probably think UNIX is a great model with >only 2 priv levels, nothing and >absofuckinglutelyeverything.
No. I am not. It is my opinion that there were a lot of good systems before (you know who) starts
to create unmanageable from the security point of view systems like
RSX,VMS, Windows NT...
Those systems are common in following:
- a huge and unmanageable Discretory Access Control structure (ACL and privileges).
- a lack of ability to create virtual machine.
or good isolation between processes.
- No Mandatory Access control structures or
just rudiments of that.
- No information labelling.
- An enormous amount of subjects and objects of
access.
For good systems I can account, for example RSTS/E, TSX.
Or even mainframes' OSes (OS 370, VM/SP).
May be CRAY UNICOS.
Yep. Ok. B[123] or A1 security.
At least RSBAC security for Linux (www.rsbac.de)
Really... OpenVMS has a VERY BAD security. :)"
If you leave SYSTEM/SYSTEM on login,
it allow you everything.
And also it has a privilege "grant yourself any
privilege
Its logging is OK, though.
Does it have information labelling?
That versions I saw, nope. May be some hardened
versions?
OpenVMS need a administrator genius to be secure, systems with a really good security should allow a relatively dumb user to administer them securely.
Is that USA's fault that there is a famine and inter-tribal wars?
The astronauts are relatively safe now. They have a sojuz docked to the ISS. And they can use it any time. A sojuz can accomodate 3 people.
No launches are needed.
What to do if shuttle becomes unavailable to reenter? Probably fly to ISS and somehow manage to enter it?
Columbia is the first shuttle and it lacked a docking device which allowed it to connect to ISS.
Tough luck...