Convert CryptoAPI forum thread into xml to publish it as proper HowTO for general use. Make sure instructions are fine for x86 ppl too. Specify emerge command needed on x86, maybe put comment in on what kernel options to enable (as i don't know what options they set in x86 crypto kernel by default. Consult x86 maintainer of crypto-sources. Also, mention mutex as co-author or source (if you have a good title for a derived works contributor) as i inspired myself of some of his docs for parts of the HowTo. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Does the cryptoapi still work on ppc? I heard rumors it is unsupported (like our ppc-sources-crypto).
It still works on ppc, I have a 2.4.21-ben2 running here with cryptoapi patches applied. But due to my bad net connection atm, I can't update the ebuild for the ppc crypto kernel... But it definitely is still working...
Does mutex have a name or an email address?
Created attachment 15994 [details] The full XML of the guide. However, if mutex needs to recieve credit, I need his email and name. Also, updated versions of the doc can be found either here or at <http://docs.tehunlose.com/docs/crypto-ppc.xml>. Please review this so I can have it committed. :)
I'll review, hang on :)
This needs to be put on hold ASAP. I tried to use this guide for implementation and several commands failed. I'll post a patch to the XML will the correct commands later today.
k, acknowledged
Any news on this?
I've been asked to make this doc arch generic. I may be able to finish it up today after my classes. It depends on how much work I'm assigned. ;)
Finished. Soon to be committed.
Oh dear. I committed to the wrong bug. Sigh!!!
I believe this is now handled by the disk-cryptography.xml that tigger is writing, no?
This looks like it describes the 2.4 port of the 2.6 crypto-api stuff I've used for disk cryptography. So, it overlaps with my docs (which assume 2.6). Not sure what you'd like to do here..? I have no experience with the 2.4 side of things (nor do I want to have tbh).
With the above in mind I propose to close off this bug as WONTFIX.
Zack, mind marking this one as WONTFIX? Really, it's timed out. Flatlined.
Sorry zack for taking this out; it's cleansing time :)