Bug 15178 – Convert CryptoAPI forum thread into xml

• Product: [OLD] Docs-user
• Status: RESOLVED WONTFIX

[Description Olivier Reisch (RETIRED) 2003-02-05 14:44:00 UTC]

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.

[Comment 1 Lars Weiler (RETIRED) 2003-07-28 21:52:18 UTC]

Does the cryptoapi still work on ppc?  I heard rumors it is unsupported (like our ppc-sources-crypto).

[Comment 2 Olivier Reisch (RETIRED) 2003-07-29 02:05:42 UTC]

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... 

[Comment 3 Zack Gilburd (RETIRED) 2003-08-12 12:48:03 UTC]

Does mutex have a name or an email address?

[Comment 4 Zack Gilburd (RETIRED) 2003-08-12 15:01:27 UTC]

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. :)

[Comment 5 Sven Vermeulen (RETIRED) 2003-08-14 07:23:29 UTC]

I'll review, hang on :)

[Comment 6 Zack Gilburd (RETIRED) 2003-08-15 07:16:59 UTC]

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.

[Comment 7 Sven Vermeulen (RETIRED) 2003-08-15 07:22:17 UTC]

k, acknowledged

[Comment 8 Sven Vermeulen (RETIRED) 2003-08-25 02:22:13 UTC]

Any news on this?

[Comment 9 Zack Gilburd (RETIRED) 2003-08-25 08:03:49 UTC]

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. ;)

[Comment 10 Zack Gilburd (RETIRED) 2003-09-28 19:40:16 UTC]

Finished.  Soon to be committed.

[Comment 11 Zack Gilburd (RETIRED) 2003-09-28 19:40:47 UTC]

Oh dear.  I committed to the wrong bug.  Sigh!!!

[Comment 12 Sven Vermeulen (RETIRED) 2004-10-09 05:35:41 UTC]

I believe this is now handled by the disk-cryptography.xml that tigger is writing, no? 

[Comment 13 rob holland (RETIRED) 2004-10-23 12:36:04 UTC]

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).

[Comment 14 Sven Vermeulen (RETIRED) 2004-10-24 02:27:38 UTC]

With the above in mind I propose to close off this bug as WONTFIX. 

[Comment 15 Sven Vermeulen (RETIRED) 2005-05-25 13:40:59 UTC]

Zack, mind marking this one as WONTFIX? Really, it's timed out. Flatlined.

[Comment 16 Sven Vermeulen (RETIRED) 2005-05-27 11:30:32 UTC]

Sorry zack for taking this out; it's cleansing time :)