Summary: | app-crypt/pvk - Converts PVK files to PEM files and back again | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bertrand Jacquin <bertrand> |
Component: | Current packages | Assignee: | Bertrand Jacquin <bertrand> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | CC: | proxy-maint |
Priority: | Low | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.drh-consultancy.demon.co.uk/pvk.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
app-crypt/pvk-0.12.ebuild
pvk-0.12.ebuild app-crypt/pvk/pvk-0.12.ebuild app-crypt/pvk/files/pvk-0.12-Makefile-rework.diff |
Description
Bertrand Jacquin
2011-08-06 15:03:06 UTC
Created attachment 282327 [details]
app-crypt/pvk-0.12.ebuild
Created attachment 350508 [details]
pvk-0.12.ebuild
Move to EAPI 5, respect LDFLAGS, avoid link with /usr/local, fix quotes
Same problem as with the other bug, how do you know the version and how will you know they do a version bump? Because the version is not in the URL a new version coming out can be problematic. Maybe we need to snapshot or just rehost them? If license permits... (In reply to Tom Wijsman (TomWij) from comment #3) > Same problem as with the other bug, how do you know the version and how will > you know they do a version bump? Because the version is not in the URL a new > version coming out can be problematic. Maybe we need to snapshot or just > rehost them? If license permits... Dr Stephen N Henson have been contact to solve this. Created attachment 356548 [details]
app-crypt/pvk/pvk-0.12.ebuild
Rewrite Makefile, rename SRC_URI to name src_unpack can handle in a generic way, use SLOTed DEPEND
Created attachment 356550 [details, diff]
app-crypt/pvk/files/pvk-0.12-Makefile-rework.diff
Here is a patch for the Makefile, it's more a rewrite that a patch. The main idea is to rely on pkg-config to get cflags and libs to link with.
Also mkerr.pk seems to not be exist in openssl installation so I drop the errors rule.
(In reply to Bertrand Jacquin from comment #4) > (In reply to Tom Wijsman (TomWij) from comment #3) > > Same problem as with the other bug, how do you know the version and how will > > you know they do a version bump? Because the version is not in the URL a new > > version coming out can be problematic. Maybe we need to snapshot or just > > rehost them? If license permits... > > Dr Stephen N Henson have been contact to solve this. Did you receive a response already? Otherwise we might just snapshot for now... Looked into the tarball, the license indeed permits redistributing. Here is Dr Stephen N Henson response :
> The webpages there are a bit out of date. There isn't really much need to use
> the old pvk utility any more. Newer versions of OpenSSL have better PVK support
> as standard. For example:
>
> openssl rsa -inform PVK -in key.pvk
|