What is the best way to keep a object bound in memory for stateless session bean use?

Specifically, I have a java.security.Key that I need to make available to very 
specific stateless session bean.
Since the key is the private RSA key for the credit card database, I do not want to 
put it in the DB
or on the file system.  I do not want it available should the server be compromised.  
I realize that
having it in memory is still somewhat accessable for a hacked system, but it is the 
only thing I have come
up with to make the key available to the bean and still make it difficult for a hacker.

The original thought is to put the key into a private static variable within the bean 
so that all copies of the
bean in the JVM would have access to the same key.  The question is, wouldn't there 
come a time when all copies
of the bean are removed for lack of access and the key would be lost?  This is not a 
huge problem since the first
user to receive an error would simply request that the manager upload the key again.  
That is unless it happens
frequently throughout the day.  The idea is that the manager would also specify a 
timeout when uploading the key
so that it would drop from memory after a certain amount of time.

I am open to any suggestions.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Stuff, things, and much much more.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to