[
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 rena
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
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
: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
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
[
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
+ 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
[
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
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
[
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
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
- Security - pluggable encryption system/custom keys
--
Key: GERONIMO-4176
URL: https://issues.apache.org/jira/browse/GERONIMO-4176
Project: Geronimo
Issue Type: Task
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
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
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
Documentation - Security - pluggable encryption system/custom keys
--
Key: GERONIMO-4176
URL: https://issues.apache.org/jira/browse/GERONIMO-4176
Project: Geronimo
Issue Type
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
(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
[
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
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
[
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
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
[
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
[
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
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
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
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
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
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
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
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
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
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
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
+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
+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
+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
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
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
Should keys move up to a peer to the STATUS file too? Seems these
are project global, not specific to the server bits...
--jason
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
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
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
+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
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
[ 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
[ 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
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
[ 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
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
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
[ 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
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
+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
+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
+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
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
[ 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
[ 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
[ 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
[ 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
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
62 matches
Mail list logo
