Mark M

Brainstorming: so this is actually an interesting challenge. currently the communications between client and server are extremely informal. server binds to a port and listens for connections. upon receiving a...

Actually, can I assume the victim conveniently has pycrypto installed? Should I? Probably not.

http://the.randomengineer.com/2014/01/29/using-ssl-wrap_socket-for-secure-sockets-in-python/ http://www.reddit.com/r/AskNetsec/comments/2fnu7e/feedback_on_a_postexploitation_tool_i_wrote/ckb4v73 http://bobthegnome.blogspot.com/2007/08/making-ssl-connection-in-python.html http://security.stackexchange.com/questions/61021/how-does-the-ssl-connection-protocol-work-with-self-signed-certificate

what's the crypto design with the best simplest/secure tradeoff. i could do a dumb xor cipher? key could be a config or generated by the client/server independently based on some...

seek or something

Nope, sorry :) Thanks for letting me know you’re interested in this feature though, I’ll prioritize it! > On Aug 19, 2015, at 5:31 PM, Alex Nelson [email protected] wrote: >...

but of course, if we want these beacons to not trigger rsts, that necessitates a different server-always-on design

Yup, the solc fork is here: https://github.com/trailofbits/solidity/tree/basic-block-edges and some example current output: ``` [I] mark forge ~/c/e/s/corpus ❯ mysolc qq.sol --bin-runtime 0x7c -> [0x7d] 0xb -> [0xc, 0x3f] 0x3e ->...

need to revisit this, since that pr was merged.

example of "create function here" bug. it should have disassembled all the code at the bottom, but it just got 1 basic block and 1 invalid.