[jira] [Resolved] (GERONIMO-6654) Ensure prometheus keys can be renamed
[ https://issues.apache.org/jira/browse/GERONIMO-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved GERONIMO-6654. -- Resolution: Fixed > Ensure prometheus keys can be renamed > - > > Key: GERONIMO-6654 > URL: https://issues.apache.org/jira/browse/GERONIMO-6654 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: Metrics_1.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GERONIMO-6654) Ensure prometheus keys can be renamed
Romain Manni-Bucau created GERONIMO-6654: Summary: Ensure prometheus keys can be renamed Key: GERONIMO-6654 URL: https://issues.apache.org/jira/browse/GERONIMO-6654 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: Metrics_1.0.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: KEYS file, where's the official location?
IIRC, there used to be more KEYS files... ;-) dist/geronimo/KEYS is the official location for release signing keys (should be the case for all . For tracking purposes (maybe?) we've also had a copy in svn -- geronimo/KEYS. The two files should be kept in sync. I don't really recall the exact reason why we have two... And getting out of sync, is not good... --kevan On Sat, Aug 23, 2014 at 11:28 AM, Alan D. Cabrera l...@toolazydogs.com wrote: We seem to have two locations for our KEYS file, http://svn.apache.org/repos/asf/geronimo/KEYS and http://www.apache.org/dist/geronimo/KEYS. Which one is the official one? Regards, Alan
Re: KEYS file, where's the official location?
Is there a sync process (from svn to dist seems the way to keep track of changes) or a way to get one? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-24 20:50 GMT+02:00 Kevan Miller kevan.mil...@gmail.com: IIRC, there used to be more KEYS files... ;-) dist/geronimo/KEYS is the official location for release signing keys (should be the case for all . For tracking purposes (maybe?) we've also had a copy in svn -- geronimo/KEYS. The two files should be kept in sync. I don't really recall the exact reason why we have two... And getting out of sync, is not good... --kevan On Sat, Aug 23, 2014 at 11:28 AM, Alan D. Cabrera l...@toolazydogs.com wrote: We seem to have two locations for our KEYS file, http://svn.apache.org/repos/asf/geronimo/KEYS and http://www.apache.org/dist/geronimo/KEYS. Which one is the official one? Regards, Alan
KEYS file, where's the official location?
We seem to have two locations for our KEYS file, http://svn.apache.org/repos/asf/geronimo/KEYS and http://www.apache.org/dist/geronimo/KEYS. Which one is the official one? Regards, Alan
[jira] [Closed] (GERONIMODEVTOOLS-751) No keys of Keyboard can jump out of the input box
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li closed GERONIMODEVTOOLS-751. verified on build 20110531125652 No keys of Keyboard can jump out of the input box - Key: GERONIMODEVTOOLS-751 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: windows xp x86-32 ,eclipse 3.6 SR1,IBM jdk6 Reporter: Tina Li Assignee: Yi Xiao Priority: Trivial Fix For: 3.0 Attachments: 1.1Keyboard access problem.JPG 1.Install gep 3.0-snapshot via deployable way 2.Create a new server using gep3.0 and the May 19 's build of geronimo server-3.0 snapshot 3.Using Jaws to read the Overviewinfo of this server, then found the accessibility problem:no keys of Keyboard can jump out of the input box 4.1.1Keyboard access problem.JPG is attached for detail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-751) No keys of Keyboard can jump out of the input box
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13039037#comment-13039037 ] Yi Xiao commented on GERONIMODEVTOOLS-751: -- Hi, Tina. You can use Ctrl + Tab to jump out of the input box. No keys of Keyboard can jump out of the input box - Key: GERONIMODEVTOOLS-751 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: windows xp x86-32 ,eclipse 3.6 SR1,IBM jdk6 Reporter: Tina Li Assignee: Yi Xiao Priority: Trivial Fix For: 3.0 Attachments: 1.1Keyboard access problem.JPG 1.Install gep 3.0-snapshot via deployable way 2.Create a new server using gep3.0 and the May 19 's build of geronimo server-3.0 snapshot 3.Using Jaws to read the Overviewinfo of this server, then found the accessibility problem:no keys of Keyboard can jump out of the input box 4.1.1Keyboard access problem.JPG is attached for detail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-751) No keys of Keyboard can jump out of the input box
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-751. -- Resolution: Fixed Fix Version/s: 3.0 No keys of Keyboard can jump out of the input box - Key: GERONIMODEVTOOLS-751 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: windows xp x86-32 ,eclipse 3.6 SR1,IBM jdk6 Reporter: Tina Li Assignee: Yi Xiao Priority: Trivial Fix For: 3.0 Attachments: 1.1Keyboard access problem.JPG 1.Install gep 3.0-snapshot via deployable way 2.Create a new server using gep3.0 and the May 19 's build of geronimo server-3.0 snapshot 3.Using Jaws to read the Overviewinfo of this server, then found the accessibility problem:no keys of Keyboard can jump out of the input box 4.1.1Keyboard access problem.JPG is attached for detail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-751) No keys of Keyboard can jump out of the input box
No keys of Keyboard can jump out of the input box - Key: GERONIMODEVTOOLS-751 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: windows xp x86-32 ,eclipse 3.6 SR1,IBM jdk6 Reporter: Tina Li Assignee: Yi Xiao Priority: Trivial 1.Install gep 3.0-snapshot via deployable way 2.Create a new server using gep3.0 and the May 19 's build of geronimo server-3.0 snapshot 3.Using Jaws to read the Overviewinfo of this server, then found the accessibility problem:no keys of Keyboard can jump out of the input box 4.1.1Keyboard access problem.JPG is attached for detail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-751) No keys of Keyboard can jump out of the input box
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li updated GERONIMODEVTOOLS-751: - Attachment: 1.1Keyboard access problem.JPG No keys of Keyboard can jump out of the input box - Key: GERONIMODEVTOOLS-751 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: windows xp x86-32 ,eclipse 3.6 SR1,IBM jdk6 Reporter: Tina Li Assignee: Yi Xiao Priority: Trivial Attachments: 1.1Keyboard access problem.JPG 1.Install gep 3.0-snapshot via deployable way 2.Create a new server using gep3.0 and the May 19 's build of geronimo server-3.0 snapshot 3.Using Jaws to read the Overviewinfo of this server, then found the accessibility problem:no keys of Keyboard can jump out of the input box 4.1.1Keyboard access problem.JPG is attached for detail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-4176) Documentation - Security - pluggable encryption system/custom keys
[ https://issues.apache.org/jira/browse/GERONIMO-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-4176: Assignee: Chi Runhua (was: Hernan Cunico) Documentation - Security - pluggable encryption system/custom keys -- Key: GERONIMO-4176 URL: https://issues.apache.org/jira/browse/GERONIMO-4176 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.x Reporter: Hernan Cunico Assignee: Chi Runhua Provide documentation for the pluggable encryption system for passwords. This feature has been available since [GERONIMO-2925] but never documented. snip If you want to have a fixed key generated by geronimo you can add this gbean to the rmi-naming module in config.xml: gbean name=org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car?name=ConfiguredEncryption,j2eeType=GBean gbeanInfo=org.apache.geronimo.system.util.ConfiguredEncryption attribute name=pathvar/security/ConfiguredSecretKey.ser/attribute reference name=ServerInfopatternnameServerInfo/name/pattern/reference /gbean This will create a key the first time its started, after that it will keep using the saved key at the location specified. If you put a serialized SecretKeySpec there it will use it instead. Of course using something like this leaves your system open to the key file changing or disappearing and losing all the saved password info. /snip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4176) Documentation - Security - pluggable encryption system/custom keys
[ https://issues.apache.org/jira/browse/GERONIMO-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-4176. -- Fix Version/s: 3.0 2.2 2.1.5 Resolution: Fixed Doc updated accordingly for G2.1/2.2/3.0 space. https://cwiki.apache.org/GMOxDOC21/basic-hints-on-security-configuration.html https://cwiki.apache.org/GMOxDOC22/basic-hints-on-security-configuration.html https://cwiki.apache.org/GMOxDOC30/basic-hints-on-security-configuration.html Documentation - Security - pluggable encryption system/custom keys -- Key: GERONIMO-4176 URL: https://issues.apache.org/jira/browse/GERONIMO-4176 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.x Reporter: Hernan Cunico Assignee: Chi Runhua Fix For: 3.0, 2.2, 2.1.5 Provide documentation for the pluggable encryption system for passwords. This feature has been available since [GERONIMO-2925] but never documented. snip If you want to have a fixed key generated by geronimo you can add this gbean to the rmi-naming module in config.xml: gbean name=org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car?name=ConfiguredEncryption,j2eeType=GBean gbeanInfo=org.apache.geronimo.system.util.ConfiguredEncryption attribute name=pathvar/security/ConfiguredSecretKey.ser/attribute reference name=ServerInfopatternnameServerInfo/name/pattern/reference /gbean This will create a key the first time its started, after that it will keep using the saved key at the location specified. If you put a serialized SecretKeySpec there it will use it instead. Of course using something like this leaves your system open to the key file changing or disappearing and losing all the saved password info. /snip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r901700 - /geronimo/KEYS
Delos, you need to create a new PGP key that's 4096 bits, instead of the default 1024. Here is some info from a previous posting - Everyone who uploads artifacts (snapshot or release), don't forget that you need to: 1) update your existing PGP keys to avoid using SHA-1 http://www.apache.org/dev/openpgp.html#sha1 2) create a new 4096 bit key for future code signing http://www.apache.org/dev/key-transition.html 3) update/add your key into the KEYS file in svn - geronimo/KEYS 4) upload the updated KEYS file to our distro directory - /www/www.apache.org/dist/geronimo/ -Donald On 1/21/10 8:38 AM, de...@apache.org wrote: Author: delos Date: Thu Jan 21 13:38:06 2010 New Revision: 901700 URL: http://svn.apache.org/viewvc?rev=901700view=rev Log: append public key of delos Modified: geronimo/KEYS Modified: geronimo/KEYS URL: http://svn.apache.org/viewvc/geronimo/KEYS?rev=901700r1=901699r2=901700view=diff == --- geronimo/KEYS (original) +++ geronimo/KEYS Thu Jan 21 13:38:06 2010 @@ -1008,3 +1008,40 @@ WiPNXzqCfvuELA6IUAcu =N6IO -END PGP PUBLIC KEY BLOCK- + +pub 1024D/3D50A4B2 2010-01-21 +uid delos de...@apache.org +sig 33D50A4B2 2010-01-21 delos de...@apache.org +sub 2048g/10EAF5DA 2010-01-21 +sig 3D50A4B2 2010-01-21 delos de...@apache.org + +-BEGIN PGP PUBLIC KEY BLOCK- +Version: GnuPG v1.4.9 (GNU/Linux) + +mQGiBEtYHlQRBACsODzmCQRbMlLclxstXLcVfdW9ikMfR5fsAX0gNsEjmcXKX/kz +vljH76DuykeLK2DzeTYj3syL+R0yLEFrXuTF+aVbPH11eXTP1rWWL14NguxZmIfn +Tzzr+v/ndqzLLBkyNWnT/z8t83pHlBDUo/kvfVppKgDHyQ1EKIpdoglWkwCg8Hx8 +wk7PuBcW5QDnQCpIms0DR2UEAIafAVdS0uLj+G9DOqbUAV6Tnf3cvur873+cjb4M +aPUB4CXnF9rwbRWc/jNAZw7yu6KwLMR7lXuy0yB3bJYLzGfh0vFUVS2XlPDMbDYw +2WRxIQHLtQTD/w1YaL5vxu+FKwzaAp7/Ixt2K2HyjDJdtNxsEOWUqkdRXjGNOSxe +IiuUA/9M0Qz1p7/OQJ48AjPI3+KnQyFAewGhjQk2sOtEAB1TuvIAgY2N08f7sLh4 +SvSw/yZUWKMQA6HGHjmY1+mpOplY+AZVLmsp8gOZss9CJ/jwPsx9D7Kmt7hoGXaq +zsyk+pSi/bb31DZX2s2LoYKbh1bXjiFxPas5FQNZmrElkXzh3bQYZGVsb3MgPGRl +bG9zQGFwYWNoZS5vcmc+iGAEExECACAFAktYHlQCGwMGCwkIBwMCBBUCCAMEFgID +AQIeAQIXgAAKCRBaZfiFPVCksqklAJ9F7lcqF5mvpPndTYghVs+bYDs3gACeKoeQ +v2CVmxrivz8O5lsZkSfnO4y5Ag0ES1geWBAIAMLJxGyagLqsSpPARKl8gL6V6wDX +3O0VhwaUPd7hoihuAxQlGr4byUXeQObcq6P4K3rPWhQJgEjBFUjdds/zBvV8lr9q +etxqitXHXVs80tTSzhdVs809ofaR89CuEhubBUpqR1ExOglPuP7FGJRaIrQhxMPm +whHs7v33EbjOViHBBnVNI04k48SAwXSuVzevcAZWNo0U9smnUjFpS57JY0N8AAWN +G5yiABRhwgvovfuShIolI07KOLm59WiXvreAhRj85v3k8GL5z1SJyDromZuiiKao +hCeiWvzdX0fH1snlsQtFtfF7oK8X0oM0KvTNkgjsCGS4JEseMfElFTCO0OsAAwUH +/RhTsYbf5IvmRcfEDRfDATqADgYqheSS7KDhf2gmEBLZkaPtedxYUNaocOyjAQxM +5Ar//4VAeTE1IfPeNe70CYRY9kyHLnNcxyZm1Biuh56xNEJfbYL/Y1mumQHMpW2v +Cyq5GfwdUhMUJFNrQVZ0HsGtOPTObYghOxy1kKNGsyendra+AARWf8YzrP+yEgc1 +Wm878oalf4J2Gt0Jv+QEKDNBHUWh1dTbG+UyAnJxcoL+9QQ7+lKJt2oRpBgCRPC0 +zxeVc1A6+avz7/XnF8GQtfCzu4zXhi7kp+WnJOLu3BCOAXjALOLEt7v9WGRBvOtp +EBLfkZCg1JTzRPMKAJM5CiqISQQYEQIACQUCS1geWAIbDAAKCRBaZfiFPVCkslgG +AKDCE2bxV2FScEFsq+Bq+jCz1pzggACggovY/jhbCvj+NIlOXXMAANsqbdo= +=WjOT +-END PGP PUBLIC KEY BLOCK- +
Re: svn commit: r901700 - /geronimo/KEYS
OK, thanks Donald. I will re-create the new key. 2010/1/21 Donald Woods dwo...@apache.org Delos, you need to create a new PGP key that's 4096 bits, instead of the default 1024. Here is some info from a previous posting - Everyone who uploads artifacts (snapshot or release), don't forget that you need to: 1) update your existing PGP keys to avoid using SHA-1 http://www.apache.org/dev/openpgp.html#sha1 2) create a new 4096 bit key for future code signing http://www.apache.org/dev/key-transition.html 3) update/add your key into the KEYS file in svn - geronimo/KEYS 4) upload the updated KEYS file to our distro directory - /www/www.apache.org/dist/geronimo/ -Donald On 1/21/10 8:38 AM, de...@apache.org wrote: Author: delos Date: Thu Jan 21 13:38:06 2010 New Revision: 901700 URL: http://svn.apache.org/viewvc?rev=901700view=rev Log: append public key of delos Modified: geronimo/KEYS Modified: geronimo/KEYS URL: http://svn.apache.org/viewvc/geronimo/KEYS?rev=901700r1=901699r2=901700view=diff == --- geronimo/KEYS (original) +++ geronimo/KEYS Thu Jan 21 13:38:06 2010 @@ -1008,3 +1008,40 @@ WiPNXzqCfvuELA6IUAcu =N6IO -END PGP PUBLIC KEY BLOCK- + +pub 1024D/3D50A4B2 2010-01-21 +uid delos de...@apache.org +sig 33D50A4B2 2010-01-21 delos de...@apache.org +sub 2048g/10EAF5DA 2010-01-21 +sig 3D50A4B2 2010-01-21 delos de...@apache.org + +-BEGIN PGP PUBLIC KEY BLOCK- +Version: GnuPG v1.4.9 (GNU/Linux) + +mQGiBEtYHlQRBACsODzmCQRbMlLclxstXLcVfdW9ikMfR5fsAX0gNsEjmcXKX/kz +vljH76DuykeLK2DzeTYj3syL+R0yLEFrXuTF+aVbPH11eXTP1rWWL14NguxZmIfn +Tzzr+v/ndqzLLBkyNWnT/z8t83pHlBDUo/kvfVppKgDHyQ1EKIpdoglWkwCg8Hx8 +wk7PuBcW5QDnQCpIms0DR2UEAIafAVdS0uLj+G9DOqbUAV6Tnf3cvur873+cjb4M +aPUB4CXnF9rwbRWc/jNAZw7yu6KwLMR7lXuy0yB3bJYLzGfh0vFUVS2XlPDMbDYw +2WRxIQHLtQTD/w1YaL5vxu+FKwzaAp7/Ixt2K2HyjDJdtNxsEOWUqkdRXjGNOSxe +IiuUA/9M0Qz1p7/OQJ48AjPI3+KnQyFAewGhjQk2sOtEAB1TuvIAgY2N08f7sLh4 +SvSw/yZUWKMQA6HGHjmY1+mpOplY+AZVLmsp8gOZss9CJ/jwPsx9D7Kmt7hoGXaq +zsyk+pSi/bb31DZX2s2LoYKbh1bXjiFxPas5FQNZmrElkXzh3bQYZGVsb3MgPGRl +bG9zQGFwYWNoZS5vcmc+iGAEExECACAFAktYHlQCGwMGCwkIBwMCBBUCCAMEFgID +AQIeAQIXgAAKCRBaZfiFPVCksqklAJ9F7lcqF5mvpPndTYghVs+bYDs3gACeKoeQ +v2CVmxrivz8O5lsZkSfnO4y5Ag0ES1geWBAIAMLJxGyagLqsSpPARKl8gL6V6wDX +3O0VhwaUPd7hoihuAxQlGr4byUXeQObcq6P4K3rPWhQJgEjBFUjdds/zBvV8lr9q +etxqitXHXVs80tTSzhdVs809ofaR89CuEhubBUpqR1ExOglPuP7FGJRaIrQhxMPm +whHs7v33EbjOViHBBnVNI04k48SAwXSuVzevcAZWNo0U9smnUjFpS57JY0N8AAWN +G5yiABRhwgvovfuShIolI07KOLm59WiXvreAhRj85v3k8GL5z1SJyDromZuiiKao +hCeiWvzdX0fH1snlsQtFtfF7oK8X0oM0KvTNkgjsCGS4JEseMfElFTCO0OsAAwUH +/RhTsYbf5IvmRcfEDRfDATqADgYqheSS7KDhf2gmEBLZkaPtedxYUNaocOyjAQxM +5Ar//4VAeTE1IfPeNe70CYRY9kyHLnNcxyZm1Biuh56xNEJfbYL/Y1mumQHMpW2v +Cyq5GfwdUhMUJFNrQVZ0HsGtOPTObYghOxy1kKNGsyendra+AARWf8YzrP+yEgc1 +Wm878oalf4J2Gt0Jv+QEKDNBHUWh1dTbG+UyAnJxcoL+9QQ7+lKJt2oRpBgCRPC0 +zxeVc1A6+avz7/XnF8GQtfCzu4zXhi7kp+WnJOLu3BCOAXjALOLEt7v9WGRBvOtp +EBLfkZCg1JTzRPMKAJM5CiqISQQYEQIACQUCS1geWAIbDAAKCRBaZfiFPVCkslgG +AKDCE2bxV2FScEFsq+Bq+jCz1pzggACggovY/jhbCvj+NIlOXXMAANsqbdo= +=WjOT +-END PGP PUBLIC KEY BLOCK- + -- Best Regards, Delos
Re: Does maven provide any support for re-signing artifacts with longer keys?
meant to send this to a maven list... but any info great~ thanks david jencks On Nov 28, 2009, at 2:45 PM, David Jencks wrote: Apache has recently requested that all apache releases be signed with 4096 bit keys and SHA512, see http://www.apache.org/dev/openpgp.html I've released some artifacts using maven signed with an older 1024 bit key and most likely SHA1. Is there any maven support for re-signing these older artifacts with a new longer key? If not, does anyone have any advice for a non- maven way to do it? thanks david jencks
[jira] Created: (GERONIMO-4176) Documentation - Security - pluggable encryption system/custom keys
Documentation - Security - pluggable encryption system/custom keys -- Key: GERONIMO-4176 URL: https://issues.apache.org/jira/browse/GERONIMO-4176 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.x Reporter: Hernan Cunico Assignee: Hernan Cunico Provide documentation for the pluggable encryption system for passwords. This feature has been available since [GERONIMO-2925] but never documented. snip If you want to have a fixed key generated by geronimo you can add this gbean to the rmi-naming module in config.xml: gbean name=org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car?name=ConfiguredEncryption,j2eeType=GBean gbeanInfo=org.apache.geronimo.system.util.ConfiguredEncryption attribute name=pathvar/security/ConfiguredSecretKey.ser/attribute reference name=ServerInfopatternnameServerInfo/name/pattern/reference /gbean This will create a key the first time its started, after that it will keep using the saved key at the location specified. If you put a serialized SecretKeySpec there it will use it instead. Of course using something like this leaves your system open to the key file changing or disappearing and losing all the saved password info. /snip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
public keys for releases
When we publish a release we need to ensure that our public KEY Is available for validation. I had previously stored my public key in two locations: - Submitted to http://pgp.mit.edu/. - Added into https://svn.apache.org/repos/asf/geronimo/KEYS However, I was informed by ASF Infra back when I did my first release that my key wasn't available and I needed to add it to: - http://www.apache.org/dist/geronimo/KEYS The only way that I knew of to add this was to manually edit this file. Is there a better way? Was there once some automation that synced our svn version of the KEYS file to the distribution version but is no longer working? I was going to add the directions to update the file manually to our Geronimo Release Process doc but perhaps we need to fix some automation instead. Does anybody know? Joe
[jira] Resolved: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3865. --- Resolution: Fixed Committed the new patch to trunk (revision 629889) and branches/2.1 (revision 629892). Thanks again! unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865-1.patch, GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma reassigned GERONIMO-3865: Assignee: YunFeng Ma unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: YunFeng Ma There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma updated GERONIMO-3865: - Attachment: GERONIMO-3865.patch Thanks for pointing this out, a patch for this. unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: YunFeng Ma Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3865: - Assignee: Jarek Gawor (was: YunFeng Ma) unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3865. --- Resolution: Fixed Fix Version/s: 2.2 2.1.1 Committed the patch to trunk (revision 629507) and branches/2.1 (revision 629524). Thanks a lot! unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma updated GERONIMO-3865: - Attachment: GERONIMO-3865-1.patch GERONIMO-3865-1.patch fixed the unresolved keys in Security - Keystores - (open a keystore and edit the keystore) - Change keystore password unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865-1.patch, GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma reopened GERONIMO-3865: -- Another unresolved i18n keys unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3865) unresolved i18n keys
unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[YOKO] KEYS
I have removed all the keys but Rick's from the KEYS file since I do not recognize who they belong to. Yoko committers, please feel free to add your keys to this file. Regards, Alan
Re: KEYS ?
On 10/12/07, Kevan Miller [EMAIL PROTECTED] wrote: I don't know of any reason to maintain KEYS files in any other svn directory. I propose we delete them from all non-tagged branches/trunks in our svn tree. Thoughts? Was there a reason to keep them in the other places? I'd love to hear what it was so I could say for sure I'm +1 for the single place. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: KEYS ?
I think we should keep the KEYS file in trunk and copy it to dist when we're releasing... On Oct 12, 2007, at 12:07 AM, Kevan Miller wrote: On Aug 8, 2007, at 3:08 PM, Jason Dillon wrote: And... this is done. I don't know what else needs to be changed... if anyone runs into any problems lemme know. The new location for this puppy in svn is: https://svn.apache.org/repos/asf/geronimo/KEYS Props need to check the current trunk/* and branches/* (except for release in progress branches) bits for other KEYS files and nuke them. I just encountered our proliferation of KEYS files. From an Apache release signing perspective, I think the only important file is http://www.apache.org/dist/geronimo/KEYS. Probably makes sense to keep this file and https://svn.apache.org/repos/asf/geronimo/KEYS in sync (they are currently not in sync). I'm not sure if it's possible to automate this... Ideas? I don't know of any reason to maintain KEYS files in any other svn directory. I propose we delete them from all non-tagged branches/ trunks in our svn tree. Thoughts? --kevan
Re: KEYS ?
On Aug 8, 2007, at 3:08 PM, Jason Dillon wrote: And... this is done. I don't know what else needs to be changed... if anyone runs into any problems lemme know. The new location for this puppy in svn is: https://svn.apache.org/repos/asf/geronimo/KEYS Props need to check the current trunk/* and branches/* (except for release in progress branches) bits for other KEYS files and nuke them. I just encountered our proliferation of KEYS files. From an Apache release signing perspective, I think the only important file is http://www.apache.org/dist/geronimo/KEYS. Probably makes sense to keep this file and https://svn.apache.org/repos/asf/geronimo/KEYS in sync (they are currently not in sync). I'm not sure if it's possible to automate this... Ideas? I don't know of any reason to maintain KEYS files in any other svn directory. I propose we delete them from all non-tagged branches/ trunks in our svn tree. Thoughts? --kevan
Re: KEYS ?
And... this is done. I don't know what else needs to be changed... if anyone runs into any problems lemme know. The new location for this puppy in svn is: https://svn.apache.org/repos/asf/geronimo/KEYS Props need to check the current trunk/* and branches/* (except for release in progress branches) bits for other KEYS files and nuke them. --jason On 7/31/07, Jason Dillon [EMAIL PROTECTED] wrote: Well, I think we should probably consolidate all these ;-) --jason On Jul 31, 2007, at 8:16 AM, Matt Hogstrom wrote: Good point. I think we have the KEYs file in a couple of places. on people there is: /www/people.apache.org/ ./repo/m1-ibiblio-rsync-repository/geronimo/KEYS ./repo/m2-ibiblio-rsync-repository/org/apache/geronimo/KEYS ./repo/m1-ibiblio-rsync-repository/org.apache.xbean/KEYS ./repo/m2-ibiblio-rsync-repository/org/apache/xbean/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/geronimo/ genesis/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/geronimo/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/xbean/KEYS on /www/www.apache.org/dist/ .geronimo/KEYS We also have a web link from http://www.apache.org/dist/geronimo/KEYS Not sure if there are other references (and yes, I know these are outside svn :) On Jul 30, 2007, at 12:35 PM, Dain Sundstrom wrote: I'm not sure, but it may be mentioned in old binaries as the location for verifying the signatures. I could be completely wrong... I just have a memory of some external references. If you do move the file, I'd definitely search the website for references. -dain On Jul 27, 2007, at 12:35 PM, Jason Dillon wrote: What external references are you referring to? I believe that it does have symlink support, though I hardly ever use it. --jason On Jul 27, 2007, at 12:29 PM, Dain Sundstrom wrote: I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
Good point. I think we have the KEYs file in a couple of places. on people there is: /www/people.apache.org/ ./repo/m1-ibiblio-rsync-repository/geronimo/KEYS ./repo/m2-ibiblio-rsync-repository/org/apache/geronimo/KEYS ./repo/m1-ibiblio-rsync-repository/org.apache.xbean/KEYS ./repo/m2-ibiblio-rsync-repository/org/apache/xbean/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/geronimo/ genesis/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/geronimo/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/xbean/KEYS on /www/www.apache.org/dist/ .geronimo/KEYS We also have a web link from http://www.apache.org/dist/geronimo/KEYS Not sure if there are other references (and yes, I know these are outside svn :) On Jul 30, 2007, at 12:35 PM, Dain Sundstrom wrote: I'm not sure, but it may be mentioned in old binaries as the location for verifying the signatures. I could be completely wrong... I just have a memory of some external references. If you do move the file, I'd definitely search the website for references. -dain On Jul 27, 2007, at 12:35 PM, Jason Dillon wrote: What external references are you referring to? I believe that it does have symlink support, though I hardly ever use it. --jason On Jul 27, 2007, at 12:29 PM, Dain Sundstrom wrote: I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
Well, I think we should probably consolidate all these ;-) --jason On Jul 31, 2007, at 8:16 AM, Matt Hogstrom wrote: Good point. I think we have the KEYs file in a couple of places. on people there is: /www/people.apache.org/ ./repo/m1-ibiblio-rsync-repository/geronimo/KEYS ./repo/m2-ibiblio-rsync-repository/org/apache/geronimo/KEYS ./repo/m1-ibiblio-rsync-repository/org.apache.xbean/KEYS ./repo/m2-ibiblio-rsync-repository/org/apache/xbean/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/geronimo/ genesis/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/geronimo/KEYS ./repo/m2-ibiblio-rsync-repository.backup/org/apache/xbean/KEYS on /www/www.apache.org/dist/ .geronimo/KEYS We also have a web link from http://www.apache.org/dist/geronimo/KEYS Not sure if there are other references (and yes, I know these are outside svn :) On Jul 30, 2007, at 12:35 PM, Dain Sundstrom wrote: I'm not sure, but it may be mentioned in old binaries as the location for verifying the signatures. I could be completely wrong... I just have a memory of some external references. If you do move the file, I'd definitely search the website for references. -dain On Jul 27, 2007, at 12:35 PM, Jason Dillon wrote: What external references are you referring to? I believe that it does have symlink support, though I hardly ever use it. --jason On Jul 27, 2007, at 12:29 PM, Dain Sundstrom wrote: I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
I'm not sure, but it may be mentioned in old binaries as the location for verifying the signatures. I could be completely wrong... I just have a memory of some external references. If you do move the file, I'd definitely search the website for references. -dain On Jul 27, 2007, at 12:35 PM, Jason Dillon wrote: What external references are you referring to? I believe that it does have symlink support, though I hardly ever use it. --jason On Jul 27, 2007, at 12:29 PM, Dain Sundstrom wrote: I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
Aighty, I'll keep that in mind and try to look for dangling references when I move it. --jason On Jul 30, 2007, at 9:35 AM, Dain Sundstrom wrote: I'm not sure, but it may be mentioned in old binaries as the location for verifying the signatures. I could be completely wrong... I just have a memory of some external references. If you do move the file, I'd definitely search the website for references. -dain On Jul 27, 2007, at 12:35 PM, Jason Dillon wrote: What external references are you referring to? I believe that it does have symlink support, though I hardly ever use it. --jason On Jul 27, 2007, at 12:29 PM, Dain Sundstrom wrote: I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
+1 Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason smime.p7s Description: S/MIME Cryptographic Signature
Re: KEYS ?
+1 Jacek On 7/27/07, Jason Dillon [EMAIL PROTECTED] wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: KEYS ?
+1 to move. Vamsi On 7/27/07, Jason Dillon [EMAIL PROTECTED] wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
What external references are you referring to? I believe that it does have symlink support, though I hardly ever use it. --jason On Jul 27, 2007, at 12:29 PM, Dain Sundstrom wrote: I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: KEYS ?
I think there are external references to this file, but I'm not sure how we should deal with them. Does svn have symlink support? -dain On Jul 26, 2007, at 3:52 PM, Jason Dillon wrote: Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
KEYS ?
Should keys move up to a peer to the STATUS file too? Seems these are project global, not specific to the server bits... --jason
Re: Simpler config-substitutions.properties keys?
I fixed this as part of https://issues.apache.org/jira/browse/GERONIMO-2735 and documented some stuff at http://cwiki.apache.org/confluence/ display/GMOxDOC20/Multiple+Repositories PLEASE NOTE that I added a prefix for command line and system properties that you want to get into the substitution map. By default, you have to prefix substitution properties in the system environment or in system properties with org.apache.geronimo.config.substitution. so that we won't get accidental resetting of our ports or whatever from other programs settings. IIRC (which I may not) I proposed this when the feature was originally discussed and only realized it wasn't implemented when I came to examine the code again. thanks david jencks On Jul 22, 2007, at 3:29 PM, Matt Hogstrom wrote: go for it On Jul 22, 2007, at 1:48 PM, David Jencks wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
Simpler config-substitutions.properties keys?
I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
Re: Simpler config-substitutions.properties keys?
No objection. Vamsi On 7/22/07, David Jencks [EMAIL PROTECTED] wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
Re: Simpler config-substitutions.properties keys?
+1 Jacek On 7/22/07, David Jencks [EMAIL PROTECTED] wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Simpler config-substitutions.properties keys?
go for it On Jul 22, 2007, at 1:48 PM, David Jencks wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
[jira] Closed: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Joe Bohn closed GERONIMO-1531. -- Resolution: Fixed This issue is resolved with the fix for GERONIMO-2218 KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Vamsavardhana Reddy Assigned To: Joe Bohn Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Assigned: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Joe Bohn reassigned GERONIMO-1531: -- Assignee: Joe Bohn KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Vamsavardhana Reddy Assigned To: Joe Bohn Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=comments#action_12422984 ] Vamsavardhana Reddy commented on GERONIMO-1531: --- GERONIMO-1531.patch cannot be used with AG1.1 source. Issue addressed in patch provided to GERONIMO-2218. KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Sachin Patel updated GERONIMO-1531: --- Assignee: (was: Matt Hogstrom) KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Sachin Patel updated GERONIMO-1531: --- Fix Version/s: 1.1.1 (was: 1.1.x) Assignee: Matt Hogstrom This jira is unassigned but contains a patch that needs to be reviewed for inclusion in 1.1.1. KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Vamsavardhana Reddy Assigned To: Matt Hogstrom Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Alan Cabrera updated GERONIMO-1531: --- Fix Version/s: 1.1.x (was: 1.1.1) Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all probability, 1.1.2 patch. KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.1.x Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Aaron Mulder updated GERONIMO-1531: --- Assign To: (was: Aaron Mulder) KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: console Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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
No KEYS link on 1.1 download page
I noticed that the download page no longer has a KEYS link. Yesterday (before the update to the site) the KEYS link at the very bottom of the download page pointed to http://people.apache.org/dist/geronimo/KEYS but it seems there is a more up-to-date version in http://www.apache.org/dist/geronimo/KEYS . AFAIK, we should have the keys available so users can download it, as discussed in the Apache HTTP Server download page: http://httpd.apache.org/download.cgi#verify I am willing to update the download page so that it has a KEYS link, but can *someone confirm* which file it should be pointing to. I can also add a Verify the integrity of the files section on the download page, based upon the http://httpd.apache.org/download.cgi#verify page to help those users who aren't familiar with the tools used to verify releases. Would like some +1's before proceeding. John
Re: No KEYS link on 1.1 download page
+1 John. If you would do that it would be excellent. The KEYS file is http://www.apache.org/dist/geronimo/KEYS. John Sisson wrote: I noticed that the download page no longer has a KEYS link. Yesterday (before the update to the site) the KEYS link at the very bottom of the download page pointed to http://people.apache.org/dist/geronimo/KEYS but it seems there is a more up-to-date version in http://www.apache.org/dist/geronimo/KEYS . AFAIK, we should have the keys available so users can download it, as discussed in the Apache HTTP Server download page: http://httpd.apache.org/download.cgi#verify I am willing to update the download page so that it has a KEYS link, but can *someone confirm* which file it should be pointing to. I can also add a Verify the integrity of the files section on the download page, based upon the http://httpd.apache.org/download.cgi#verify page to help those users who aren't familiar with the tools used to verify releases. Would like some +1's before proceeding. John
Re: No KEYS link on 1.1 download page
+1 On Jun 27, 2006, at 3:31 PM, John Sisson wrote: I noticed that the download page no longer has a KEYS link. Yesterday (before the update to the site) the KEYS link at the very bottom of the download page pointed to http://people.apache.org/ dist/geronimo/KEYS but it seems there is a more up-to-date version in http://www.apache.org/dist/geronimo/KEYS . AFAIK, we should have the keys available so users can download it, as discussed in the Apache HTTP Server download page: http://httpd.apache.org/download.cgi#verify I am willing to update the download page so that it has a KEYS link, but can *someone confirm* which file it should be pointing to. I can also add a Verify the integrity of the files section on the download page, based upon the http://httpd.apache.org/ download.cgi#verify page to help those users who aren't familiar with the tools used to verify releases. Would like some +1's before proceeding. John
Re: No KEYS link on 1.1 download page
+1 On Jun 27, 2006, at 6:48 PM, David Blevins wrote: +1 On Jun 27, 2006, at 3:31 PM, John Sisson wrote: I noticed that the download page no longer has a KEYS link. Yesterday (before the update to the site) the KEYS link at the very bottom of the download page pointed to http:// people.apache.org/dist/geronimo/KEYS but it seems there is a more up-to-date version in http://www.apache.org/dist/geronimo/KEYS . AFAIK, we should have the keys available so users can download it, as discussed in the Apache HTTP Server download page: http://httpd.apache.org/download.cgi#verify I am willing to update the download page so that it has a KEYS link, but can *someone confirm* which file it should be pointing to. I can also add a Verify the integrity of the files section on the download page, based upon the http://httpd.apache.org/ download.cgi#verify page to help those users who aren't familiar with the tools used to verify releases. Would like some +1's before proceeding. John -sachin
Re: No KEYS link on 1.1 download page
Matt Hogstrom wrote: +1 John. If you would do that it would be excellent. The KEYS file is http://www.apache.org/dist/geronimo/KEYS. John Sisson wrote: I noticed that the download page no longer has a KEYS link. Yesterday (before the update to the site) the KEYS link at the very bottom of the download page pointed to http://people.apache.org/dist/geronimo/KEYS but it seems there is a more up-to-date version in http://www.apache.org/dist/geronimo/KEYS . AFAIK, we should have the keys available so users can download it, as discussed in the Apache HTTP Server download page: http://httpd.apache.org/download.cgi#verify I am willing to update the download page so that it has a KEYS link, but can *someone confirm* which file it should be pointing to. I can also add a Verify the integrity of the files section on the download page, based upon the http://httpd.apache.org/download.cgi#verify page to help those users who aren't familiar with the tools used to verify releases. Would like some +1's before proceeding. John I have committed these changes in rev 417662, but will hold off updating the site for a while to give time to people to review. It is pretty much the same as the Apache HTTP server documentation, just updated to reference Geronimo filenames and Matt's public key in examples. If anyone can help with the commented out section in verification.xml that would be great. Thanks, John
[jira] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Matt Hogstrom updated GERONIMO-1531: Fix Version: 1.1.1 (was: 1.1) KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: console Versions: 1.0 Reporter: Vamsavardhana Reddy Assignee: Aaron Mulder Priority: Minor Fix For: 1.1.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Assigned: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Vamsavardhana Reddy reassigned GERONIMO-1531: - Assign To: Aaron Mulder KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Type: Improvement Components: console Versions: 1.0 Reporter: Vamsavardhana Reddy Assignee: Aaron Mulder Priority: Minor Fix For: 1.x, 1.1, 1.0.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Vamsavardhana Reddy updated GERONIMO-1531: -- Geronimo Info: [Patch Available] Fix Version: 1.0.1 KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Type: Improvement Components: console Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.x, 1.1, 1.0.1 Attachments: GERONIMO-1531.patch KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Updated: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
[ http://issues.apache.org/jira/browse/GERONIMO-1531?page=all ] Matt Hogstrom updated GERONIMO-1531: Fix Version: 1.x (was: 1.0.1) KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Type: Improvement Components: console Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.x, 1.1 KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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] Created: (GERONIMO-1531) KeyStore portlet should support deletion of certificates and private keys
KeyStore portlet should support deletion of certificates and private keys - Key: GERONIMO-1531 URL: http://issues.apache.org/jira/browse/GERONIMO-1531 Project: Geronimo Type: Improvement Components: console Versions: 1.0 Reporter: Vamsavardhana Reddy Priority: Minor Fix For: 1.0.1, 1.1 KeyStore portlet currently supports generation of keypairs, adding trusted certificates to keystore and importing certificate issued by CA. It does not address deletion of any of these from the keystore. -- 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
