Fix extra bytes display for composed SSK

[TheSeeker]

Fix for composed private SSK displaying as AQICAAE instead of AQECAAE.

[Thynix]

I'm not familiar with this part of the code, and without reading and understanding the context it's not clear to me why there was a problem, or why the change fixes it. Could you please elaborate in the body of the commit message?

[Thynix]

Also, the build is failing?? Not that this introduced the breakage.

[TheSeeker]

Also, the build is failing?? Not that this introduced the breakage.

This was addressed in PR #17, while separately addressed by adding a wrapper function for the deprecated call.

[TheSeeker]

I'm not familiar with this part of the code, and without reading and understanding the context it's not clear to me why there was a problem, or why the change fixes it. Could you please elaborate in the body of the commit message?

I have no idea how to edit the commit message from the github web interface, sorry. The Extra bytes for an SSK are (currently) either AQACAAE (public) or AQECAAE (private) but when composing the bytes for conversion to base64 and display, the wrong value (2) was being placed in the byte describing the key type when private, resulting in AQICAAE when it should be AQECAAE. see: https://github.com/freenet/fred/blob/next/src/freenet/keys/ClientSSK.java#L148

[ArneBab]

Tests work here with the merged #17, changes look good to me.