Tickets :: Comment on [#7447] Audit for inappropriate use of mt

* Your Email Address
* Spam protection	Enter the letters below: . ..__..__..__..___. \|\/\|\| \|\| \|[__] \| \| \|\|__\\|__\|\| \| \|
Comment	> The question is, what else to we use (additionally?) as a secret or > source of randomness? /dev/urandom is not available on all systems. > Our pre-generated secret_key doesn't change. > In Horde_Support we use: > - php_uname('n') or ip address (not random, only to avoid collisions) > - uniqid() (with the more-entropy parameter a good candidate) > - zend_thread_id()/getmypid() (short) > - microtime() (predictable) > > Horde_Oauth and Horde_Token use microtime() resp. time() for Nonces. > > This needs to applied to: > Horde_Auth::getSalt(), genRandomPassword() (salt and password generation) > Horde_ActiveSync_State_Base::generatePolicyKey() > Horde_Secret::setKey() > Shout::genDeviceAuth() > > And probably to share and object ids and resources too, since they > could be used to share hidden shares/objects through a secret url: > Horde_Core_Imsp_Utils::synchShares() > Kronolith_Resource::addResource() > Turba_Driver::_makeKey() > > I'm unsure about: > Kolab_Storage > > Only if being anal for: > Horde_Form_Type_image::getRandomId() > Horde_Util::createTempDir() > Gollem_Api::setSelectlist()
Attachment
Watch this ticket