[JBoss JIRA] Created: (JBESB-2121) Replace crypto util with sealed object

[JBoss JIRA] Created: (JBESB-2086)...

[JBoss JIRA] Created: (JBESB-2135)...

Kevin Conner (JIRA)

Wednesday, 15 October 2008 Wed, 15 Oct '08

12:53 p.m.

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Daniel Bevenius (JIRA)

Thursday, 16 October Thu, 16 Oct

8:09 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Daniel Bevenius commented on JBESB-2121: ----------------------------------------

...

The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the >session information.

If we generate keys upon startup the keys will only be known to that ESB node. If the message switches to a different node then using that solution will not work. That is why we are currently using a keystore so that users can configure a key pair that can be installed on all nodes and they will be abe to decrypt a security context encrypted by other nodes. Is this not what we want?

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Daniel Bevenius (JIRA)

8:09 a.m.

New subject: [JBoss JIRA] Work started: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Work on JBESB-2121 started by Daniel Bevenius.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

10:43 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2121: ------------------------------------- This is precisely what we want, a new node should verify the credentials passed in. It also forces a rebooted system to reverify its own security context, just in case it has changed. As a related issue, we should be specifying an expiry for the encrypted content.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

10:45 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2121: ------------------------------------- Sorry, clarifying my last. The secured object should be private to the issuing instance and should not be decrypted by other instances.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

6:30 p.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2121: ------------------------------------- Hiya Daniel. I have just been going over this again and realised that you are encrypting everything, so a failure to decrypt leaves the other systems without any means of authentication. Lets talk about this further before doing anything.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Daniel Bevenius (JIRA)

10:17 p.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Daniel Bevenius commented on JBESB-2121: ---------------------------------------- If you mean that I'm encrypting the SecurityContext by "encrypting everything" then yes that is correct. And yes, other systems will not be able to decrypt it, at least not after this task is completed. At the moment other systems can decrypt the security context. Is what you are after that the security context should be encrypted per node, and if the message is routed to a different node, it should re-authenticate. Is that correct?

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

Friday, 17 October Fri, 17 Oct

9:27 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2121: ------------------------------------- Even as it stands we have a situation where only a specific set of servers would be able to reauthenticate, those with the correct credentials in their kestore. If the message were to be sent to another set of ESBs or even to clients without access to those credentials then they have no means of authenticating them. This also brings up the question of how to treat unauthenticated requests, we should include the ability to assign those to a specific (default) identity. We need to think about this further, lets talk later this morning.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

9:31 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2121: ------------------------------------- The other question that spring to mind with the current code is what is the reason for sending credentials around? At present the pipeline will decrypt the context and, if successful, will do no authentication. If this is unsuccessful then it has no access to the credentials to perform an authentication.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Daniel Bevenius (JIRA)

9:44 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Daniel Bevenius commented on JBESB-2121: ----------------------------------------

...

Even as it stands we have a situation where only a specific set of servers would be able to reauthenticate, those with the correct credentials in their kestore. If the >message were to be sent to another set of ESBs or even to clients without access to those credentials then they have no means of authenticating them.

Yes, this is intentional. The requirement here is that the correct credentials exist in the keystores and that the ESBs have these in common.

...

The other question that spring to mind with the current code is what is the reason for sending credentials around?

The reason is that the subject is used when executing the pipeline.

...

At present the pipeline will decrypt the context and, if successful, will do no authentication. If this is unsuccessful then it has no access to the credentials to perform an authentication.

Yes, that is correct. But this has sort of been a moving target and this was not always the case. I'm really not sure anymore what should be passed between the ESB and what requirements we have for interoperability :( So I definitely think that we should talk and see if we can get the requirements set and then take it from there.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

9:55 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2121: -------------------------------------

...

Yes, this is intentional. The requirement here is that the correct credentials exist in the keystores and that the ESBs have these in common.

I believe it was intentional, but was not what I thought you were doing :)

...

The reason is that the subject is used when executing the pipeline.

But why the credentials? The only aspect used for the authorisation are the Principals associated with the subject and not its credentials.

...

Yes, that is correct. But this has sort of been a moving target and this was not always the case.

Well, lets make sure it isn't moving any more and make it explicit. The introduction of the encryption appears to have removed one ability.

...

I'm really not sure anymore what should be passed between the ESB and what requirements we have for interoperability :( So I definitely think that we should talk and see if we can get the requirements set and then take it from there.

Definitely, lets get together and flesh everything out once and for all.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Daniel Bevenius (JIRA)

Monday, 20 October Mon, 20 Oct

11:10 a.m.

New subject: [JBoss JIRA] Closed: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Daniel Bevenius closed JBESB-2121. ---------------------------------- Resolution: Done Committed to JBESB_4_4_GA_CP with revision 23518.

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

Monday, 3 November Mon, 3 Nov

7:53 p.m.

New subject: [JBoss JIRA] Closed: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner closed JBESB-2121. ------------------------------- Fix Version/s: 4.4 CP2 (was: 4.4 CP1) Resolution: Done

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP2 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

Kevin Conner (JIRA)

7:53 p.m.

New subject: [JBoss JIRA] Reopened: (JBESB-2121) Replace crypto util with sealed object

[ https://jira.jboss.org/jira/browse/JBESB-2121?page=com.atlassian.jira.plu... ] Kevin Conner reopened JBESB-2121: ---------------------------------

...

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP2 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue.

5703

days inactive

5722

days old

esb-issues@lists.jboss.org

Manage subscription

13 comments

2 participants

tags (0)

participants (2)

Daniel Bevenius (JIRA)
Kevin Conner (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[JBoss JIRA] Created: (JBESB-2121) Replace crypto util with sealed object