SecureRandom best practice?

Maybe someone can help me with this.

So far I found that SecureRandom is better than Math.rand, but is hard to find something like a best practice for SecureRandom, for example:

1. How long the seed must be?

2. I am going to use the SecureRandom for multiple games, should I use a global SecureRandom or I should use one per game.

3. For how long the SecureRandom is good, how many numbers can I generate before change the seed?

Articles or books recommendations will be great too.

Thanks.

Message was edited by:

LuisKarlos

[579 byte] By [LuisKarlosa] at [2007-10-3 6:01:58]
# 1
If you just want a random "behaviour" in a game or similar, you don't need to worry about a thing. Java class Random will provide you with totally sufficient random behaviour. SecureRandom and alikes are needed for encryption, security and such.
gilroittoa at 2007-7-15 0:44:06 > top of Java-index,Other Topics,Algorithms...