2,359 karma · joined May 26, 2013
In terms of the cost of putting materials into space, isn't that the exact problem SpaceX is trying to solve? Right now, it would be economic folly to build one of these things. In decades or centuries, when we have moon colonies and/or asteroid mining and can do all the large-scale fabrication in situ, SSP could very well be significantly cheaper than other forms of power generation.
In terms of OS security, an integrated anti-virus package and a claim that no "external protection software" is needed to make the OS secure don't exactly inspire confidence.
- Shennong, who invented agriculture.
- Cangjie, who invented Chinese characters.
- Yao, Shun, and Yu, who tamed the river floods and irrigated the fields.
Good information has always taken work to obtain. The Internet cannot compensate for intellectual laziness, it can only magnify the effectiveness of the efforts of those willing to exercise discernment and look at things with a critical eye.
I'm quite glad that the Chinese of the late 19th/early 20th century often took the Japanese approach of coining semantically meaningful neologisms, rather than trying to transliterate everything.
Was I wrong? (I hope I was wrong.) My manager was a great guy, and definitely not unreasonable. But at least from my perspective at the time, the stakes were so high. Was this just some stupid fear that doesn't actually reflect what happens in real life?
Maybe some mathematician will prove AES is broken tomorrow. In terms of the analogy, I don't care. The most qualified, fastidious engineer building the most correct implementation of AES is going to have an insecure system on their hands at the end of the day if that's true, and there is nothing we can do about that on the implementation side.
This is distinct from some programmer reading "Learn Crypto in 24 Hours", building a bad implementation of an otherwise secure cryptosystem due to inexperience or carelessness, and then screwing people over because that bad cryptosystem goes into production code.
Unfortunately, not even widely used, highly trusted implementations work right all the time. A out-of-bounds memory bug introduced by an insufficiently vetted commit opened up a serious flaw in OpenSSL. On a much, much smaller scale, I once had the misfortune of working with an old version of Microchip's PIC18 AES library, which had some serious issues that made it nonfunctional for anything more complex than the toy sample app it shipped with. But with enough exposure these problems are eventually exposed and fixed. Would a world where everyone rolled their own bespoke, ad-hoc SSL implementations be more secure? I doubt it.
In the end, I think there needs to be a cultural shift. People shouldn't be discouraged from building their own crypto for fun and learning, but they should be discouraged from deploying it for any application where real security is required - at least not before undergoing rigorous analysis. One of the first things Dan Boneh teaches in his Crypto I class is that you should think very long and hard before implementing your own cryptosystems (i.e. don't do it), because getting it right is hard, and getting it even the slightest bit wrong tends to make it useless. And when you consider that people's livelihoods (their personal information, their money) and even lives might be jeopardized, taking responsibility as an engineer becomes of paramount importance. Crypto just doesn't lend itself to a "build an MVP, get it working, move fast and break things" mindset.
- Do your project ideas never get finished?
- If not, is it because of technical issues that make it difficult to get your product working?
- If not, is it because you lose interest or the people you work with lose interest?
- If not, is it because there are non-technical factors outside your control that you cannot successfully deal with (e.g. licensing agreements)?
- Do your startups not get traction in the marketplace?
- If so, is it because you're trying to unsuccessfully compete with a larger player in the field?
- If so, is it because you're not waiting long enough, or your expectations are too high?
- If so, is it because you've tried the standard promotional channels and nobody is paying attention?
- If so, is it because the market has shifted in the period between inception and release in such a way your product is now redundant or obsolete?
- Are your projects torpedoed by issues related to the people you are working with, if any?
- Are your projects torpedoed by the fact that you run out of living expense money before they have a chance to catch on?
Although all startups face some similar base set of failure modes, the challenges facing (e.g.) a robotics startup can be very different from those facing a consumer web-services startup trying to build the next Instagram.
Before Snowden changed things, it was readily apparent that everyone was ready to believe the US and nobody was ready to believe China. So the accusations were a rational thing to do.
The US isn't the only country that does this, obviously, and people are divided over whether or not it is the 'right' way to conduct international relations.
Then there are the assholes who claim that if you don't torrent your films and games you're not enough of a 'hacker', or that there's no problem with piratical torrenting at all because all the people who torrent would never have purchased the album/film/game legitimately if the torrent hadn't been available (as if even a small fraction of those people would willingly admit otherwise).
I don't know what the solution is. If I ever became rich (not going to happen), I would seriously consider becoming a patron of the types of arts that I enjoy. But that's a pipe dream, and even if it did happen it wouldn't scale.
The Buffer Overflow #1 and #2 projects might also be worth checking out. You can download the project description, starter code, and VM image, and see if you can write code to get the root shell.