python - os.urandom or ssl.RAND_bytes? -

-

os.urandom or ssl.rand_bytes: when generating random bytes cryptographic purposes, more recommended?

if neither 1 better, tradeoffs , expected each in terms of differences?

note ssl.rand_bytes exists in python 3.

ssl.rand_bytes needs seeded before can used. cannot rely on ssl.rand_bytes alone. both os.urandom , `ssl.rand_bytes pseudo random number generators. prng's deterministic; when seeded same data, return same stream of pseudo random number bytes. these bytes should indistinguishable true random if observer not know seed value. os.urandom (re-)seeded using source of entropy within operating system.

using os.urandom should therefore preferred on ssl.rand_bytes. first of all, seeded (and reseeded operating system). furthermore, not require additional dependency on ssl library. drawback performance. faster use ssl.rand_bytes seeded big enough value os.urandom os.urandom requires system call time retrieve data.


Comments

Post a Comment

Popular posts from this blog

Need help in packaging app using TideSDK on Windows -

-
i developed application using tidesdk on windows , when click launchapp works fine. moved package , installed imagemagick , wix 3.0 required packaging on windows. clicked on package runtime , cannot guess packaged app is? found file 'installer' in workspace when click on it says installer not find application path . think application not being packaged properly. here log see in tidesdk: preparing package desktop app runtime. 1 moment... staging trial -> copying contents d:\lab\tidesdk\trial d:\lab\tidesdk\trial\packages\win32\bundle\trial -> copying installer c:\programdata\tidesdk\sdk\win32\1.3.1-beta\installer d:\lab\tidesdk\trial\packages\win32\bundle\trial -> copying runtime d:\lab\tidesdk\trial\packages\win32\bundle\trial -> date: d:\lab\tidesdk\trial\packages\win32\bundle\trial\modules\app\1.3.1-beta -> date: d:\lab\tidesdk\trial\packages\win32\bundle\trial\modules\codec\1.3.1-beta -> date: d:\lab\tidesdk\trial\packages\win32\bundle\trial\mod...
Read more

c++ - boost interprocess mutex in managed_shared_memory -

-
i have thread in process 1 create boost::interprocess::managed_shared_memory segment. in segment allocate boost::interprocess::deque using custom allocator , create boost::interprocess::interprocess_mutex , 2 boost::interprocess::interprocess_condition variables using default allocator. use find_or_construct method create these. i have process (process 2) opens these using find method on boost::interprocess::managed_shared_memory segment have opened in process 2. i understand managed_shared_memory segments have kernel or filesystem persistency , interprocess_mutex/interprocess_condition variables have process level persistency. the scenario getting stuck. 1) process 1 starts thread creates everything. 2) process 2 starts , opens everything, @ stage shared memory , synchronization working well. 3) process 1 restarts thread tries create again (i believe shouldnt though using find_or_construct) 4) process 2 stuck on wait call condition variable though thread in process 1...
Read more