Displaying 3 results from an estimated 3 matches for "statefilename".
Did you mean:
stat_filename
2013 Sep 20
0
[LLVMdev] Adding diversity for security (and testing)
...andards.html#static
+ PKCS5_PBKDF2_HMAC_SHA1(Password.data(), Password.size(), (unsigned
char*)&Salt, sizeof(Salt), PBKDF_ITERATIONS, KeyLen, RandomBytes);
80-column violation.
http://llvm.org/docs/CodingStandards.html#source-code-width
+void RandomNumberGenerator::ReadStateFile(StringRef StateFilename) {
There's nothing wrong with this function per se. It isn't buggy. I'm
just wondering how this API fits with the general "llvm as a library"
approach. LLVM doesn't generally bake in the assumption that it's
running on a system with a filesystem. For example, the b...
2013 Sep 19
2
[LLVMdev] Adding diversity for security (and testing)
Thanks for all the feedback! It seems there is some interest, so I thought I'd try to summarize discussions so far, and provide patches for closer inspection. I'm not sure if patches should end up here or on a different list in this instance, so if I should instead send this to a different list, I'm happy to do so.
- Is diversity needed, or are existing protections sufficient? As
2013 Sep 20
2
[LLVMdev] Adding diversity for security (and testing)
...) makes the client code particularly unreadable, since it currently uses a static Generator() getter to get the instance of the RNG. I'd like to resolve this first, then we can look at whether using the operator() interface makes sense.
> +void RandomNumberGenerator::ReadStateFile(StringRef StateFilename) {
>
> There's nothing wrong with this function per se. It isn't buggy. I'm just wondering how this API fits with the general "llvm as a library" approach. LLVM doesn't generally bake in the assumption that it's running on a system with a filesystem. For example...