oakenshield
Joined 16 years ago
Joined 16 years ago
Any apps that do implement this feature likely do so by making the original file read-only and having the first app that opens the file work on a copy. However, I think Windows may have a mandatory file locking mechanism.
Not surprisingly, most people who value their time prefer making a 35-minute drive at their convenience, and paying about $12-$18 per day of parking.
http://cpp-netlib.org/0.9.4/index.html
https://code.google.com/p/rapidjson/
I have no recommendations for writing REST services, however.
> ... so disadvantageous in an evolutionary sense? Environmental factors (such as staring at a computer screen...)
Well if you're arguing that it's a nurture thing, there are plenty of us who had bad vision at childhood, right from before the dawn of the computer age. You could say that it was not computer screens but books that caused it, but how far back can you make this argument? Any sources for this claim?
[1] on modern hardware, that is.
Very likely -- Run this on your machine and see if it improves things http://stackoverflow.com/a/9781943. I got about 18.6s for your python code while this one with a 16 byte salt and 250k iterations runs in 0.6s.
OWASP recommends over 100k iterations too: https://www.owasp.org/index.php/Password_Storage_Cheat_Sheet...
1. Print it out on paper and put it in a safe. This is somewhat annoying and inconvenient for the vast majority of users, and if you lose or don't have access to the paper, you're screwed.
2. Encrypt the password using answers to some security questions and store it with an online provider you marginally trust. This has the problem of reducing the security to the strength of your answers (which may be known to any number of people close to you), and people might even forget the spelling of their answers which puts them in the same pickle.
I feel what would be ideal is some sort of a question/challenge that evokes a consistent, unique, high-entropy response from the user but the response is not based on a fact... sort of like a Rorschach test, perhaps, but one where each user would have a unique response. Is anyone aware of some system/research like this?
Nginx: http://www.aosabook.org/en/nginx.html LLVM: http://www.aosabook.org/en/llvm.html Sendmail: http://www.aosabook.org/en/sendmail.html
Although this means there's no consistent style across chapters, it's really something else to hear about the architectural and design decisions that the author made, and how they look back at those decisions now (esp. in the Sendmail article).