The engines on a rocket are designed to withstand huge amounts of heat. It may be the intent is to have the rocket re-enter engine first. I'd love to see more information on that part of the rocket myself. Certainly interesting :D
573 karma · joined April 8, 2012
The engines on a rocket are designed to withstand huge amounts of heat. It may be the intent is to have the rocket re-enter engine first. I'd love to see more information on that part of the rocket myself. Certainly interesting :D
The data from the last launch provided a lot of really crucial information that has informed design decisions made for this and following launches.
It's actually better if the next recovery fails too, at least if it happens in a way that provides really important data. This would then let them work out the engineering and science required to improve the design further.
The FTL kickstarter started off demonstrating how excited they were to build the game followed almost directly with information and footage of the core mechanics. The game looked fun before even getting past the first minute of the video.
On the other hand, the presentation of your kickstarter just didn't do much for me. I got through to about 3 minutes in the video before deciding stop watching.
The main problem for me was that nothing in the presentation me made me want to love either the game or the people behind it.
You call the game an action RPG... but the footage shown during the first 3 minutes that I watched involved mostly walking around and opening a chest. I'd have much preferred to have seen some whitty dialog with an NPC or some of the core game mechanics. This would have helped immensely as nothing that I saw looked "action" or "rpg".
I want to say that I would have done the same thing. At the same time though... doing so with a security application assumes that the team supporting the software you depend on is competent enough to properly audit and test their code.
I have a feeling that OpenSSL will be leaving a bad taste in peoples mouths for a while. :/
It's possible that he knows of a real exploitable problem.
It's possible that he is trying to boast about his prowess with things "security".
It's possible the "hole" is a design feature in FreeBSD that he just doesn't like. (And hence, considers to be a security problem.)
It's possible that he is bitter that FreeBSD has gotten more attention than OpenBSD.
It's possible that he said it to spur FreeBSD take more interest in security. (Justifiably or not...)
It's possible that he wanted to cause a commotion.
It's possible that more than one of the above is true. :) He is under no obligation to make a disclosure of an exploit that he finds. Does it make him a bad net-denizen? Perhaps. But it's his prerogative.
DSA I believe is still patent encumbered.
I have a feeling it has less to do with something sinister, and more to do with Theo's very vocal stance on the security situation in FreeBSD.
http://www.itwire.com/business-it-news/open-source/62641-cry...
Most likely the FreeBSD kernel or libraries are doing something in a certain way that Theo finds insecure/insufficient. (Justified or not)
Long Answer: It's complicated and I do not understand the whole picture myself.
I can however outline two things that likely exasperate the situation.
a) OpenSSH is used by nearly everyone. Nearly every unix-like installation includes a copy of OpenSSH. Most companies which do business on the internet use a unix-like operating system in some way.
The OpenBSD Foundation has had trouble obtaining funding to cover operating costs in the past. Included in these operating costs is support and auditing of OpenSSH.
b) There has been a long and colored history between FreeBSD and OpenBSD. A lot of code and features developed under OpenBSD has been ported over to FreeBSD such as the OpenBSD Packet Filter (PF).
Juniper uses FreeBSD and PF in their routers and have donated in various ways to FreeBSD. For example, Juniper donated three EX3200s with full contracts to FreeBSD for use in their datacenter.
The OpenBSD Foundation on the other hand has not really seen the same support.
OpenSSL is an encryption API maintained by an entirely different group of people.
EDIT: Modified my reply. OpenSSH at some point moved it's "restrictively licenced software" (RSA, DES, etc) out of it's codebase and now depends on OpenSSL according to it's license. http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/LICENC...
When you do use pointers, we finally have a real null pointer literal now. (I believe the latest C spec has also received this.)
C++ is certainly crufty. The language has been around for a long time and many features in the specification exist to support legacy code. This is a side effect of being a living language with a huge user base.
Modern C++ tends to be fairly clean and reasonably easy to work in. Herb Sutter has some great talks and blog articles around the topic. For example: http://channel9.msdn.com/Events/Build/2014/2-661
Segregation is a lot more than a political issue, but also a human rights issue. That $1000 actively helped pass a bill that prevented consenting adult couples who wished to spend their lives together from having the same legal rights as everyone else. His donation in this case was more than having a political view, but actually helped to promote segregation.
Why would I want someone who has tried to take away my rights as the CEO of a company that I care about? If it was just his "view", this would not be the issue that it has been.
The wiki system on GitHub is based out of it's own git repo (https://github.com/[user]/[repo].wiki.git). If you could be bothered to pull/push when changes are made, I'd imagine this content could then be made distributed.
While not distributed/decentralized... GitHub does lets you export your existing issues. The resulting archive can then be imported into services like bitbucket, pivotal, and etc with a little work.
There are solutions for distributed/decentralized issue tracking, but I haven't seen any great way for users to interact with them. (SD and Bugs Everywhere, other users have posted links in their replies.)
Haskell is an Ivory Tower. The features that generally draw one to the language also tend to be the things that eventually push one away. Haskell has grown a lot over the years however as the language evolves to allow general programming within a pure framework.
OCaml on the other hand tends to make a compromise, acknowledging that the programmer occasionally needs a different tool for the job. OCaml allows the programmer to opt into things like mutability and objected oriented code when the need arises. These compromises can also be seen as the languages downside however.
I find it interesting that the driver for the author into OCaml is JavsScript... but it's nice to see OCaml come up a bit more often. :)
Use Github, Bitbucket, and your own "server" all at once. None have to be read-only. Push and pull from multiple sources.
Decide that Github is no longer the place for you? No problem! People contributing to your projects should already know where to push to reach everywhere it needs to go and they only need to stop pushing to github.
No reason to rely on a "central" repo.
Funny because the case looks like a jet engine :D
Not that it mattered... only 66 nays in House (63d, 2r, 1i) and 1 in Senate (1d).
Ron and Rand Paul are just milking the NSA situation for all it's worth right now.
This means:
1) It has had review by members outside of the NSA before inclusion into the kernel.
2) The source is available for anyone to view.
3) You can audit the source right now! :)
Because of this, one can reason that there is very low probability for a "NSA backdoor". Having said that, you can audit the source to make sure.
The same can be said for certain implementations of AES such as that found in OpenSSL. I can't vouch for the specific algorithms involved being secure however, so I'll leave that to someone specialized in cryptology :)
SELinux is only as secure as the access policies in place on your system and only certain distributions (like Fedora) actually distribute SELinux policies.
"Gee, you know... I think I will choose to be something that a large portion of the world hates, thinks is somehow wrong, or think is disgusting. That sounds like fun!"
It's not like being gay is some fad that one decides would be cool one day while idling at the pool.
What happens when you have more then 9 substitutions specified in the string? :D
edit: decided the code was a bit long to have pasted into my post. Can find it at the bottom of http://cm.bell-labs.com/cm/cs/who/dmr/last1120c/c03.c
The int argv[]; is where the declaration for argv is happening and is being declared as an pointer for ints.
You can also see elsewhere in the code where they are passing pointer addresses (as int params) into functions and then using the address to build pointers referencing that data.
Convenience foods (microwave dinners, fast food) tend to sit somewhere in the middle. Cheaper then restaurant food but also both likely deficient nutritionally and not tasting good unless it's absolutely loaded with carbs, fats, salt, etc.
That cup of snot is most likely better for you then fast food and is a hell of a lot cheaper. Eating something like it could very well mean that you get to eat delicious restaurant food more often simply because you can afford to do so.
I was having a hard time swallowing (ha) that sentence too. Many digestive problems have nothing to do with the lack of eating biologically correct nutrients. A good amount of acid reflux problems are caused by having a hiatal hernia for example.
Can I come over for dinner? :D
> My main gripe with Soylent (ever since I first saw it here on HN a month ago) is that they are making cooking seem like a horrible chore that nobody wants to do.
Some people really do hate cooking. Either they don't enjoy the act of it, or do not have a lot of time for it. I know... one could say that you could make time for it. The fast food industry works not because the food is good (It generally isn't...) but because it's so easy. I think people are a lot better off eating Soylent then MCD :)
On PaX https://en.wikipedia.org/wiki/PaX#Executable_space_protectio...
"The major feature of PaX is the executable space protection it offers. These protections take advantage of the NX bit on certain processors to prevent the execution of arbitrary code. This staves off attacks involving code injection or shellcode. On IA-32 CPUs where there is no NX bit, PaX can emulate the functionality of one in various ways."
And then on NX bit support on Linux: https://en.wikipedia.org/wiki/NX_bit#Linux
"The Linux kernel currently supports the NX bit on x86-64 CPUs and on x86 processors that implement it, such as the current 64-bit CPUs of AMD, Intel, Transmeta and VIA.
The support for this feature in the 64-bit mode on x86-64 CPUs was added in 2004 by Andi Kleen, and later the same year, Ingo Molnar added support for it in 32-bit mode on 64-bit CPUs. These features have been in the stable Linux kernel since release 2.6.8 in August 2004."
PaX also provides a few other features but the big defining one has been the NX bit support. Not sure why you seem to think I am mistaken in what I said.
Now you are just nitpicking :) "the" meaning, you gave me an example.
> If you're executing in kernel mode,.....Grsec/PaX kernel, however.
SELinux has a lot of overlap with grsec providing many of the same benefits while being more widely available. The flow of an exploit: 1) entry into a system (app compromise, shell access), 2) inserting/uploading of executable data, 3) execution of said data granting further access (Ex, exploiting a kernel bug, adding a backdoor, manipulating the host system in some way).
The goals of Grsec/SELinux, and marking data memory as non execute (NX bit, PaX, Exec Shield) are aimed at preventing #2 and #3. The idea is the prevention of access escalation in the first place.
On PaX, the kernel supports utilizing the NX bit on x86-64 and has for quite a while now. Not using a system supporting the NX bit or at least PaX/Exec Shield is pretty stupid.
> But there's a reasonable level of security you can achieve that's far beyond what docker provides
I had already agreed with you on VMs... no reason to argue this point. :) Since you mention VMs again however, I will also note that VMs are not entirely isolated from the host system. A Xen (as your example) exploit as an example: http://lists.xen.org/archives/html/xen-announce/2012-06/msg0...