Displaying 3 results from an estimated 3 matches for "insertednop".
2013 Sep 20
2
[LLVMdev] Adding diversity for security (and testing)
...orks now, the state file really shouldn't be needed. Nuked.
> Overall this looks like a great start. However, I would like some other people to review things:
> - I don't actually approve lib/CodeGen and lib/Target changes. Somebody else is going to have to think about whether "InsertedNOP" belongs as an MIFlag.
The reasoning behind making this an MIFlag was to be able to skip over NOPs in the terminators of a block. For uniform security we want to be able to place NOPs in the terminators, but still need to skip over them when finding the first terminator.
> - I'm conc...
2013 Sep 20
0
[LLVMdev] Adding diversity for security (and testing)
...u should remove LLVM_ENABLE_RNG and make it driven solely on
LLVM_ENABLE_RNG? If you think we can put a good enough RNG into LLVM, we
should go with turning on LLVM_ENABLE_RNG permanently, but if not then
we should make the whole thing conditional on whether LLVM_WITH_OPENSSL
is set.
+ //// isInsertedNOP - Return true if the instruction is an
+ //// artificially inserted NOP
Three slashes for a doxygen comment, not four.
+ /**
+ * Shuffles an iplist of type T
+ */
In LLVM, the style is:
// Shuffles an iplist of type T
+ void shuffle(iplist<T>& list){
Missing space before...
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