Hi y'all I've been working to get Freenet working on my Sheevaplug - I figure a 5watt 1GHz appliance with hardware crypto for $100 is something I can keep running 24x7.
Now, I have it running, but it sucks all the CPU out of the little fella and it times-out like crazy, so I've been thinking on how to best use the hardware, and what I'd need to do, assuming that crypto is a large part of the CPU hole... And that is to knock out a JNI interface to the hardware crypto and more generally to the *nix crpto api when it's available (as it would be more efficient than the Freenet java impl). But I look at the Fred code and and I am a little overwhelmed. There are no unit tests, so I am going to break something and not know it, and the package structure is flatter than I'd like... I find interfaces above impls gives me room to change the impl as I need. I'd like to find some place to write unit tests, and I'm used to the Maven dir structure, so I'd need to push the code in Fred down a directory or two. I'd need to choose a standard unit test framework (I'm a fan of TestNG and PowerMock over JUnit). I'd need to document. I'd want to start tidying up the structure a little so I could grok the whole codebase better.. and drop some package-info.java's in there too. Package by package. I'd touch a lot of things and shift code in flight. It would piss any one off. But I'd like to start doing just that with Crypto and the coupling to it it. Ultimately what I'd like to do is post a 'plug *nix image with Freenet on it that would boot up and self configure, locking out the user (making plausible deniability all the more plausible) except for limited status info. I figure this would be a no-hassle way to create a backbone from which more ad-hoc users would benefit. I'd appreciate your thoughts on if/when/when to start this and how to manage folding updates back in. Thanks for all your hard work guys! Sebastian Weetabix Key ID: 657AE5D6 hkp://keys.gnupg.net
