Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <54657510.10709@cox.net>
Date: Thu, 13 Nov 2014 21:20:48 -0600
From: "Michael S. Proctor" <michael.wolfie.proctor@....net>
To: john-users@...ts.openwall.com
Subject: Re: New tool in JtR toolset (and common code)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks Jim.  Looks like you've been busy!
Have a great one,
Mike

On 11/13/2014 2:52 PM, jfoug@....net wrote:
> There is a new tool that will be build (in the latest git bleeding
> JtR). The tool is base64conv, and will be built in ./run.  This
> tool will convert between any formats:   raw, hex (upper/lower
> case), mime-base64, crypt-base64 and a byte swapped crypt-base64.
> 
> This new 'tool' is simply a command line wrapper around the
> internal convert function.  This function is now being used in a
> few places in JtR, and it will start to replace a lot fo one-off
> custom code in dozens (if not hundreds) of hash formats.  I wrote
> this common code, after doing conversions of one base-64 flavor
> into another to make things like handling cisco8 or cisco9 formats
> easy.    Cisco8 is almost identical to pbkdf2-hmac-sha256, except
> for the encoding (and primary format signature). But with this
> conversion function, I was able to use the original
> pbkdf2-hmac-sha256-fmt.c source code, and simply add a few lines to
> a prepare() function and magically cisco8 works.   For cisco9, it
> was almost identical to scrypt, again, other than the base64
> encoding (and the signature used to pass N, r and p variables).
> Well, with the base64 convert function this was trivial to add to
> the existing scrypt format, by simply adding a little into the
> prepare function.
> 
> Shortly after this, I found one of the git issues, and that was to
> support the perl  ScryptKDF.pm format.  Again, that was trivial to
> add into the existing scrypt format, by simply converting the
> base64 string (and the N, r, p variable layouts).
> 
> Here is a real quick 'circular' example of conversions:
> 
> $ ../run/base64conv -i raw -o crypt ThisIsATestMessage 
> ThisIsATestMessage  -->  J4VdQoZnEJFZQrFBNLBnMKRZ
> 
> $ ../run/base64conv -i crypt -o mime J4VdQoZnEJFZQrFBNLBnMKRZ 
> J4VdQoZnEJFZQrFBNLBnMKRZ  -->  VGhpc0lzQVRlc3RNZXNzYWdl
> 
> $ ../run/base64conv -i mime -o hex VGhpc0lzQVRlc3RNZXNzYWdl 
> VGhpc0lzQVRlc3RNZXNzYWdl  -->
> 54686973497341546573744d657373616765
> 
> $ ../run/base64conv -i hex -o raw
> 54686973497341546573744d657373616765 
> 54686973497341546573744d657373616765  -->  ThisIsATestMessage
> 
> Jim.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJUZXUQAAoJEPc05JtbU3P4umYQAI+dJkVIPygkzT7Ze0dX0D/3
tqjVVwCx/tsmWpNQSUUFKBv0blCbZf423SqjmVD9czb1QpmkWq+mePyMO2wPZWe0
+shPh0g7HAUtgAN96g/BirYy43AubgfgYwEnkFyWdspcGsjtbv65MeMcrOU8062K
WKhOUri162xz5s4/Nc4BTM4fy4Snr8V1uxhyIFwbC+4tgRaOhd1noQoM9ZJejBOC
iEuTVHd4Sn9QD9vtoOtI8RBDcfb0gfLoTDgxhnl0fi7bvs/Ofc76acJGqyrFjpzH
jyBivHD5ycgcJ+Lpv4Kq1Bf0OWyd4rql+iztxQZorIyme+bzrNDZj7hLCJzDKHqR
2LPcFUYjFR4d5Xl+/4SlHdG0zRpi6ozuDwghNxDJSkguRQCcRFGJWmUOwZI05yuv
DoO9f9UezFy4SJ0GZVuLUDVPpcVoDm3AluOB0Hame7AwL+vxrVQ4OJHe7F2pHFEy
y+MkgVWMP82d2LCYRqcugk/bnseYk5GxGPPUYyMOC8I85HYeqLecZ1UHzThL7W2E
yeMzc4Ndtndx7yykLNhFiGsXzfbDZUvTZU2D6CctjJCAsVm6ZAjP8Zz5mbhsPPoJ
KfEgCct958XZC9i5rijSGl2WIFsFEFey2dzo0+BtX0HZLGiAWs+ocTfN0jTtdiIE
MG48BFZFcl8YKdqJJ3bW
=UIo5
-----END PGP SIGNATURE-----

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.