On 09/16/10 13:33, Danek Duvall wrote:
Enda O'Connor wrote:
on 147 pkgmanager for publisher opensolaris.org, down left hand
frame, under category "system" has two entries for security.
Fist has a lot of packages associated with it, second one has only
system/library/security/crypto/pkcs11_kms
Looks like pkcs11_kms has independently used a three-level classification:
System/Security/Crypto. It's the only package to do so, and I'm not sure
if the package manager is designed to handle it. The rest of the packages
are merely under System/Security.
It's not clear to me whether this is a bug in pkcs11_kms, or whether we
should allow for arbitrary classifications with arbitrary depth. If not
the latter, it sounds like decent RFE for pkglint. I've copied Wyllys for
some understanding on why this particular classification was chosen.
Danek
I don't recall exactly why the extra level was added, but I think that came
out of discussions with the rest of the security team prior to submitting the
ARC case (PSARC 2010/195). Probably because pkcs11_kms is a plugin provider
for the crypto framework and lives in /usr/lib/security as opposed to a more
general
security-related library that goes in /lib or /usr/lib.
I'm fine with removing "crypto" from the path, though. It doesn't matter
much to me either way.
-Wyllys
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
