Skip to content
rotor is a usable now, highly portable, NTRU based extendable output public key application. in addition, it's a collection of functions usable as a toolkit to incorporate in other applications without difficulty. designed primarily on FreeBSD and OS X. some assembly may be required.
C Assembly Perl Roff Makefile C++ Other
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bzlib
include
lib
libntru
passwdqc-1.3.1
progressbar
skein
src
zefcrypt
README.md

README.md

screen shot 2016-11-06 at 8 49 01 am


it's easier to hide something small in plain sight, isn't it?
and the body is a lot more of a digital brick without the header attached...
here's an example (click this issue, download the image):
testing
save it in "rotor/src/testing.jpg", the name doesn't matter, really
now get yourself a good old fashioned steganography tool, jphide and seek:
https://github.com/h3xx/jphs
go in to the "rotor/src" directory and run "jpseek testing.jpg test.enc.key"
the password is "test", since we're really just hiding that there's another file here, not the contents
that should elicit a file called "test.enc.key" which is the NTRU encrypted header that goes to "test.enc". now run "rotor --infile test.enc --dec --ext"
the password to the enclosed keypair is "t3strotor". look in the file you just decrypted, "test", it should start with "begin 644". from here, you figure out the rest. ;)
the advantage here is, without that header, you'd have a file, test.enc, that is a headerless blob of three combined ciphers - Salsa20, NTRU and then SHAKE 256. without that header, pretty hopeless even should you have the private key. and the header is small enough, i hid it in that jpg and left it on github for you in the issues. there's plenty of other ways to use that feature, this is just one.

You can’t perform that action at this time.