Please excuse me if this has already been addressed, I'm just now starting to dig into the freenet source.
The encryption aspect interests me, but after writing a test program and testing various key/block sizes for Rijndael, I found that only the 128 bit block size appears to work as it stands in the SVN repository, yet everywhere that it is used in the rest of the source it is requested with a 256 blocksize. Apparently only due to not passing the blocksize into the key/encrypt/ decrypt functions, it appears easy enough to fix (example patch included). My question is, why aren't these other classes which rely on Rijndael-256-block encryption broken? or are they, silently? If I'm missing something obvious, please do tell. -- Robert Hailey [ 4 intended attachments] -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: output_no_patch.txt URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070108/08162b1e/attachment.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: output_with_patch.txt URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070108/08162b1e/attachment-0001.txt> -------------- next part -------------- A non-text attachment was scrubbed... Name: Rijndael.patch Type: application/octet-stream Size: 1245 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070108/08162b1e/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: TestEncrypt.java Type: application/octet-stream Size: 2671 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070108/08162b1e/attachment-0001.obj> -------------- next part --------------
