Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Guarantee (Score 1) 716

Well, obviously, you would have to write everything yourself, from the custom OS upwards. The testing would have to be extreme, and extensive, and the code meticulously written and reviewed. All code paths would have to be exercised fully. You would not be able to use any third-party libraries of any kind, and you might even have to build the compilers and linkers yourself too. This is certainly doable, but the cost and time needed would be insanely prohibitive, so that is why it is never done. The cost and time components have to be weighed against the possibility of bugs being present. Most of us would rather risk a few bugs than to have to wait decades between releases, and have the software cost millions, if not billions, of dollars.

Comment: Re:Expected responses... (Score 1) 161

by TheSkepticCanuck (#37385482) Attached to: Kevin Mitnick Answers
The only problem with this theory is that your basement setup cannot help you learn the valuable skill of social engineering, which was a major tool in Kevin Mitnick's toolbox. The value of social engineering should not be underestimated. Computers get more secure at a much faster rate than people do. As Kevin said, people are the weakest link in the security chain.

The less time planning, the more time programming.