Summary: | New Packets: APG and librand, ebuilds attached | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | red0x <red0x> |
Component: | New packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | hardened |
Priority: | High | Keywords: | EBUILD |
Version: | 1.4 | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://autosec.sourceforge.net | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
librand-0.2.ebuild
APG-0.3.ebuild librand-0.2.ebuild librand-0.2.ebuild APG-0.3.ebuild |
Description
red0x
2004-02-21 14:31:53 UTC
Created attachment 26067 [details]
librand-0.2.ebuild
Created attachment 26068 [details]
APG-0.3.ebuild
hardened team: y'all want this? Gentoo needs a crypto herd. need a volunteer to head it up? volunteers are always welcome. If you would like to talk about the creation of such a herd stop by #gentoo-hardened on freenode and perhaps share some ideas. For sure I would want to see openssl, mhash, librand and the likes grouped into such a beast. It would be nice to have a semi central authority of cryptographic and entropy related efforts at gentoo. Anything happenning on this ebuild? I'd like to see it in portage if possible. red0x, few comments. RESTRICT="nomirror" <-- why do we need to do this for both .ebuilds when they are both marked as having a licence of GPL-2 KEYWORDS="x86" New ebuilds never get introduced as x86 In src_install() both .ebuilds rm -rf stuff in ${D}/usr/share/${PN} (Why?) Both .ebuilds inherit gcc eutils (Why?) I used some other ebuilds as references when writing these ebuilds, feel free to change things that don't make sense. red0x, Seeing as your the one that want's this support in portage I'd suggest that you clean vs dumping that on the devs. After you clean it up your still going to find a dev that actually has a use for this stuff. I don't have a use/need/desire so I'm personaly pretty unsure about me adding them to the tree. Maybe somebody else does? (like a crypto herd [hint,hint]) Yeah, I'll change it, no problem. I just figured that you know more about what this stuff means, and that they are all easy one liners. If you are that busy, I'll fix them up sometime tonight and post new ones. :) Created attachment 32899 [details]
librand-0.2.ebuild
Comment on attachment 32899 [details]
librand-0.2.ebuild
Forgot the ~x86, but that is only change needed. ;)
Created attachment 32900 [details]
librand-0.2.ebuild
Look, this one works, I promise. Sorry about the last one, it was bunk.
Created attachment 32901 [details]
APG-0.3.ebuild
Fixed up APG ebuild.
red0x, I'm going to bounce this back to bug-wranglers@ so your .ebuilds don't hit the hardened graveyard, maybe somebody else will want to maintain these. there is already a app-admin/apg in the tree, and I (personally) believe it's a lot more useful than your APG, as I use it at least once a week at work. solar: i'd be game to be a member of the crypto herd, as I handle libmcrypt,libmhash and a number of the entropy packages in the tree. crypto herd exists! Ah, there is already an apg in the tree. Someone beat me to it, and did a better job. ;) I guess I will close this bug then. |