[jira] Commented: (GERONIMO-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due
[
https://issues.apache.org/jira/browse/GERONIMO-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517855
]
Jason Dillon commented on GERONIMO-1761:
Um, why not just {{geronmo-crypto}}, it may contain some wrapper bits, but also
some handy utils and other much related to cryptographic mumbo jumbo.
Lets just rename the beast...
Change geronimo-util module to geronimo-crypto, give credit where credit is
due
---
Key: GERONIMO-1761
URL: https://issues.apache.org/jira/browse/GERONIMO-1761
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: core
Affects Versions: 1.0
Reporter: Aaron Mulder
Assignee: Jason Dillon
Fix For: 2.1
The util module holds a bunch of crypto-related stuff. Speculation is that
it's the non-encumbered code from bouncycastle. It should be in a more
accurately named module and package, since it's not just generic util code.
It would also be nice to put a note in every file header saying where it's
from, or at least in NOTICE.txt perhaps. There may be improvements we want
to track?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due
[ http://issues.apache.org/jira/browse/GERONIMO-1761?page=comments#action_12371537 ] Rick McGuire commented on GERONIMO-1761: There's already a NOTICE.txt and LICENSE.txt file in the root directory of the module giving the bouncycastle attribution. We had a similar discussion about the util name when this was first put in...nobody could come up with a more appropriate name then, either. Change geronimo-util module to geronimo-crypto, give credit where credit is due --- Key: GERONIMO-1761 URL: http://issues.apache.org/jira/browse/GERONIMO-1761 Project: Geronimo Type: Bug Components: core Versions: 1.0 Reporter: Aaron Mulder Fix For: 1.2 The util module holds a bunch of crypto-related stuff. Speculation is that it's the non-encumbered code from bouncycastle. It should be in a more accurately named module and package, since it's not just generic util code. It would also be nice to put a note in every file header saying where it's from, or at least in NOTICE.txt perhaps. There may be improvements we want to track? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due
[ http://issues.apache.org/jira/browse/GERONIMO-1761?page=comments#action_12371512 ] John Sisson commented on GERONIMO-1761: --- I agree we should be giving credit. AFAIK, the standard way is to use the NOTICE.txt file. The geronimo-util module doesn't contain any crypto implementations, it is just an abstraction layer for crypto implementations. I don't think crypto is a good name for it considering the other stuff it contains such as: * An encoders package (e.g. Base64) that are used by the remoteDeployUtil and the KeyStoreGBean. * An ASN.1 package that is used by the KeyStoreGBean and AFAIK, OpenEJB uses some classes in some corba support (X509 names). John Change geronimo-util module to geronimo-crypto, give credit where credit is due --- Key: GERONIMO-1761 URL: http://issues.apache.org/jira/browse/GERONIMO-1761 Project: Geronimo Type: Bug Components: core Versions: 1.0 Reporter: Aaron Mulder Fix For: 1.2 The util module holds a bunch of crypto-related stuff. Speculation is that it's the non-encumbered code from bouncycastle. It should be in a more accurately named module and package, since it's not just generic util code. It would also be nice to put a note in every file header saying where it's from, or at least in NOTICE.txt perhaps. There may be improvements we want to track? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (GERONIMO-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due
Can you recommend another name then? util doesn't do it for me. Thanks, Aaron On 3/22/06, John Sisson (JIRA) dev@geronimo.apache.org wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1761?page=comments#action_12371512 ] John Sisson commented on GERONIMO-1761: --- I agree we should be giving credit. AFAIK, the standard way is to use the NOTICE.txt file. The geronimo-util module doesn't contain any crypto implementations, it is just an abstraction layer for crypto implementations. I don't think crypto is a good name for it considering the other stuff it contains such as: * An encoders package (e.g. Base64) that are used by the remoteDeployUtil and the KeyStoreGBean. * An ASN.1 package that is used by the KeyStoreGBean and AFAIK, OpenEJB uses some classes in some corba support (X509 names). John Change geronimo-util module to geronimo-crypto, give credit where credit is due --- Key: GERONIMO-1761 URL: http://issues.apache.org/jira/browse/GERONIMO-1761 Project: Geronimo Type: Bug Components: core Versions: 1.0 Reporter: Aaron Mulder Fix For: 1.2 The util module holds a bunch of crypto-related stuff. Speculation is that it's the non-encumbered code from bouncycastle. It should be in a more accurately named module and package, since it's not just generic util code. It would also be nice to put a note in every file header saying where it's from, or at least in NOTICE.txt perhaps. There may be improvements we want to track? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
