Acceptable Use; Safety-Critical Systems. Your use of the Lumberyard Materials must comply with the AWS Acceptable Use Policy. The Lumberyard Materials are not intended for use with life-critical or safety-critical systems, such as use in operation of medical equipment, automated transportation systems, autonomous vehicles, aircraft or air traffic control, nuclear facilities, manned spacecraft, or military use in connection with live combat. However, this restriction will not apply in the event of the occurrence (certified by the United States Centers for Disease Control or successor body) of a widespread viral infection transmitted via bites or contact with bodily fluids that causes human corpses to reanimate and seek to consume living human flesh, blood, brain or nerve tissue and is likely to result in the fall of organized civilization.
Except that pretty much noone spends that time or resources to do that. It's more fun to continue adding features into the doomed architecture. Or start over... again.
If you design a software with a certain feature set insecurely, it's often difficult to keep those features when re-goaling for security.
A depressingly large majority of all software hasn't been coded with best-knowledge tools and APIs in mind. Not even those of the time of writing, but particularly not the one of the current time!
Spending resources on 'finding the next Heartbleed' bug... I fail to see the advantage of finding it by a coordinated search as opposed to someone just stumble on it (as long as the bugs are reported responsibly of course).
Software can't be made secure afterwards, it must be the the primary goal.
Except that is betting on that peak oil (or whatever) will happen gradually, over a decade or more. If, perhaps due to economical, political or technical reasons, there is a sudden sharp increase in oil price neither market nor society will not have time to adapt.
The countries then still sitting on a huge investment in obsolete gas hungry fleet of vehicles will lose so hard. Many european countries has realised this, thus the high tax on gas to create an artificial incitament.
It's the applet part of Java which has a bad security record. Running code under Java has exactly the same consequences to security as running native code, arguably even less.
I would argue that a large factor to why I would install and use Cygwin is to get rid of the "standard DOS shell". Replacing that crap with something like rxvt or xterm makes for a huge improvement.
His name was one of the first I learned to recognize as a young beginner sci-fi-aficionado (ohh, maybe 10 years old?). I really liked the Steel Rat books, both others as well.
Here is a comment by John Scalzi (who is actually surprisingly similiar in style - I recommend).
No, this isn't 'Interresting', rather mod as 'Blathering'.
Well, there is no point denying that Theo isn't the most malleable person. But, as has been said here on/. before: while he comes through as whining most of the time, he's also correct most of the time. Many people tries to interpret his statements from the common commercial viewpoint (like in, how to develop a successful software product and make PROFIT, or at least achieve world domination), but rather his goal is quite simple: develop a free, fast and secure Unix OS. That's all. No grand plans of IPOs or commercial success. Theo is quite happy getting by on selling those CDs, living in his little house, and occasionally traveling around the world climbing mountains and hacking Unix. You gotta read goal.html and observe him and the project for a few years to really understand that.
Theo, ranting, is why he got kicked off the NetBSD project.
While this is true, the history also proved him correct on many things (Charles Hannum was on the core team that did the kicking).
Theo, ranting, is why OpenBSD's drivers for Broadcom chipsets stink. (Look up how the original author tried to resolve the licensing problems of sticking his GPL drivers in an OpenBSD kernel and was ignored, then screamed at by Theo for making the issue public.)
That whole mess sucked. The OpenBSD developer that made the port (which was supposed to be a re-implemenation) f*cked up big time and imported GPL-files into the tree. The only thing positive in the whole affair is perhaps Theo's unconditional backing of his developer.
Theo, ranting, is why OpenBSD doesn't properly handle booting from software RAID.
It does (I believe the kernel must be on a non-RAID slice/disk, but that's no different to most other implementations).
Theo, ranting, is why the OpenBSD installer works like the UNIX crap I learned to loath back in 1985 and can't store the state of what you've already selected or go back, you just have to start over from scratch.
Actually, the very minimalistic installer is often hailed as one of the best and fastest in the industry. I don't think that there are that many installers where you can do the install by repeatedly pressing enter (and writing the hostname once) in that short time. And well, it's doesn't remember the state, but then again, you can restart it (a shell script) and start over without rebooting - that can't be said about many others.
Theo, ranting, is why OpenSSH has no built-in support for chroot cages.
This seems to disprove that. Unless you have different definition of 'chroot cage'.
Theo, ranting, is why OpenBSD has no virtualization server capability.
In many aspects virtualization contradicts the goal of security. Also, most VM solutions are proprietary, thus does not run on OpenBSD.
Theo, ranting, is why OpenSSH still stores both host keys and by default, user private keys in clear text with no expiration, and has no plans to fix this.
Yes, in clear text. Do you propose they should be encrypted? And where should the crypto key be placed? Perhaps... on disk? Hashed? If you are paranoid - use whole disk encryption. Because physical security is the key issue here as I see it. The keyfile is supposed to be user-readable only...
What is a reasonable default expiration time? No, there is no plan because the feature doesn't improve anything.
Theo, ranting, is why the "compatiblity chart" is a list of chipsets that don't match the actual chipsets published by the manufacturer, and usually are from chipsets at least 4 years old.
IIRC I've read (several years ago) about a fish that uses a leaf as cover to avoid being seen/caught by for example hungry birds (was it in south america? Amazonas?). But then again, I don't know if this either can be categorized as tool use. I mean, swimming under something isn't that difficult...
While the comments on the size of Pirate Party are correct, it can also be formulated slightly different: PP is, in the moment of writing, the fourth largest party in sweden (with respect to the number of party members). (source
)
By the rate of new members, PP should pass 'Centern' in the coming week or something like that, and thus become the third largest party.
PP's youth organisation is (perhaps unsurprisingly) the largest by far (actually has more members than the second and third combined).
It should however be noted that party membership in Sweden is not widespread, thus the actual voting result in an election will not necessarily reflect the membership records.
If you would like to contribute to the cause (for nothing else than just to spite the big media companies), you can make a donation here.
While I'm not sure they deliver merchandise abroad, they have a small shop where you can buy the obligatory t-shirt. Yes, the revolution accepts Visa.
Slashdot Mirror
https://play.google.com/store/...
This is the comment that should be pegged at the top.
While that is true to some extent, decisions taken by the LibreSSL team has
prevented a lot of vulnerabilities.
Notably, none of the vulnerabilities found in OpenSSL and rated "High" were applicable to LibreSSL.
57.10
Acceptable Use; Safety-Critical Systems. Your use of the Lumberyard Materials must comply with the AWS Acceptable Use Policy. The Lumberyard Materials are not intended for use with life-critical or safety-critical systems, such as use in operation of medical equipment, automated transportation systems, autonomous vehicles, aircraft or air traffic control, nuclear facilities, manned spacecraft, or military use in connection with live combat. However, this restriction will not apply in the event of the occurrence (certified by the United States Centers for Disease Control or successor body) of a widespread viral infection transmitted via bites or contact with bodily fluids that causes human corpses to reanimate and seek to consume living human flesh, blood, brain or nerve tissue and is likely to result in the fall of organized civilization.
From: http://aws.amazon.com/service-...
https://marc.info/?l=openbsd-t...
So one bug was in code deemed dodgy in external peer-review and the other was in code not really needed. Right.
LibreSSL is a great project, but they ripped out portability along the way.
[Citation needed]
Except that pretty much noone spends that time or resources to do that. It's more fun to continue adding features into the doomed architecture. Or start over... again.
If you design a software with a certain feature set insecurely, it's often difficult to keep those features when re-goaling for security.
A depressingly large majority of all software hasn't been coded with best-knowledge tools and APIs in mind. Not even those of the time of writing, but particularly not the one of the current time!
Spending resources on 'finding the next Heartbleed' bug... I fail to see the advantage of finding it by a coordinated search as opposed to someone just stumble on it (as long as the bugs are reported responsibly of course).
Software can't be made secure afterwards, it must be the the primary goal.
...how to titillate an ocelot.
(You oscillate its tit a lot.)
The countries then still sitting on a huge investment in obsolete gas hungry fleet of vehicles will lose so hard. Many european countries has realised this, thus the high tax on gas to create an artificial incitament.
http://forums.thedailywtf.com/...
http://thedailywtf.com/Article...
Shave the whales.
I realise that you're joking, but if we have gotten the stuff into orbit, just push it gently in the direction of the sun...
It's the applet part of Java which has a bad security record. Running code under Java has exactly the same consequences to security as running native code, arguably even less.
I would argue that a large factor to why I would install and use Cygwin is to get rid of the "standard DOS shell". Replacing that crap with something like rxvt or xterm makes for a huge improvement.
(or whatever a cup of coffee costs these days)
While on the subject it's worth mentioning the article from Ask Slashdot which nicely and detailed answers most of the questions you may have.
Actually, this is one of the best content articles I can remember on Slashdot... The graph in the middle is simultaneously funny and sad. :-/
But at least there is an offer of exclusive free content! Yay!
His name was one of the first I learned to recognize as a young beginner sci-fi-aficionado (ohh, maybe 10 years old?). I really liked the Steel Rat books, both others as well.
Here is a comment by John Scalzi (who is actually surprisingly similiar in style - I recommend).
No, this isn't 'Interresting', rather mod as 'Blathering'.
Well, there is no point denying that Theo isn't the most malleable person. But, as has been said here on /. before: while he comes through as whining most of the time, he's also correct most of the time. Many people tries to interpret his statements from the common commercial viewpoint (like in, how to develop a successful software product and make PROFIT, or at least achieve world domination), but rather his goal is quite simple: develop a free, fast and secure Unix OS. That's all. No grand plans of IPOs or commercial success. Theo is quite happy getting by on selling those CDs, living in his little house, and occasionally traveling around the world climbing mountains and hacking Unix. You gotta read goal.html and observe him and the project for a few years to really understand that.
Theo, ranting, is why he got kicked off the NetBSD project.
While this is true, the history also proved him correct on many things (Charles Hannum was on the core team that did the kicking).
Theo, ranting, is why OpenBSD's drivers for Broadcom chipsets stink. (Look up how the original author tried to resolve the licensing problems of sticking his GPL drivers in an OpenBSD kernel and was ignored, then screamed at by Theo for making the issue public.)
That whole mess sucked. The OpenBSD developer that made the port (which was supposed to be a re-implemenation) f*cked up big time and imported GPL-files into the tree. The only thing positive in the whole affair is perhaps Theo's unconditional backing of his developer.
Theo, ranting, is why OpenBSD doesn't properly handle booting from software RAID.
It does (I believe the kernel must be on a non-RAID slice/disk, but that's no different to most other implementations).
Theo, ranting, is why the OpenBSD installer works like the UNIX crap I learned to loath back in 1985 and can't store the state of what you've already selected or go back, you just have to start over from scratch.
Actually, the very minimalistic installer is often hailed as one of the best and fastest in the industry. I don't think that there are that many installers where you can do the install by repeatedly pressing enter (and writing the hostname once) in that short time. And well, it's doesn't remember the state, but then again, you can restart it (a shell script) and start over without rebooting - that can't be said about many others.
Theo, ranting, is why OpenSSH has no built-in support for chroot cages.
This seems to disprove that. Unless you have different definition of 'chroot cage'.
Theo, ranting, is why OpenBSD has no virtualization server capability.
In many aspects virtualization contradicts the goal of security. Also, most VM solutions are proprietary, thus does not run on OpenBSD.
Theo, ranting, is why OpenSSH still stores both host keys and by default, user private keys in clear text with no expiration, and has no plans to fix this.
Yes, in clear text. Do you propose they should be encrypted? And where should the crypto key be placed? Perhaps... on disk? Hashed? If you are paranoid - use whole disk encryption. Because physical security is the key issue here as I see it. The keyfile is supposed to be user-readable only...
What is a reasonable default expiration time? No, there is no plan because the feature doesn't improve anything.
Theo, ranting, is why the "compatiblity chart" is a list of chipsets that don't match the actual chipsets published by the manufacturer, and usually are from chipsets at least 4 years old.
Uhmm, wha
Sorry, I either don't remember or the article didn't say. And a quick googling didn't give any references...
IIRC I've read (several years ago) about a fish that uses a leaf as cover to avoid being seen/caught by for example hungry birds (was it in south america? Amazonas?). But then again, I don't know if this either can be categorized as tool use. I mean, swimming under something isn't that difficult...
...I would immediately make a large donation to PostgreSQL - the arch enemy for all Oracle database solutions. Just to spite them.
While the comments on the size of Pirate Party are correct, it can also be formulated slightly different: PP is, in the moment of writing, the fourth largest party in sweden (with respect to the number of party members). (source )
By the rate of new members, PP should pass 'Centern' in the coming week or something like that, and thus become the third largest party.
PP's youth organisation is (perhaps unsurprisingly) the largest by far (actually has more members than the second and third combined).
It should however be noted that party membership in Sweden is not widespread, thus the actual voting result in an election will not necessarily reflect the membership records.
If you would like to contribute to the cause (for nothing else than just to spite the big media companies), you can make a donation here.
While I'm not sure they deliver merchandise abroad, they have a small shop where you can buy the obligatory t-shirt. Yes, the revolution accepts Visa.
Really cool software: Tempest for Eliza. Make use of the old CRT in the corner...