Commit Graph

8 Commits

Author SHA1 Message Date
Paul Howarth
e702365826 Don't need Crypt::Random if Bytes::Random::Secure is available
Crypt::PWSafe3 already prefers Bytes::Random::Secure over Crypt::Random but
still has a hard dependency on it, via an unconditional "use Crypt::Random".
This is no longer necessary since Crypt::Random will be require-d if a
suitably recent version of Bytes::Random::Secure cannot be found.

The Makefile.PL is also updated to reflect this approach.
2020-05-29 09:18:34 +01:00
git@daemon.de
71239e46ee added some meta 2016-03-14 08:35:06 +01:00
git@daemon.de
f8308c72c4 added license to META 2015-02-12 15:32:52 +01:00
git@daemon.de
6597804217 re-licensed to artistic2 2015-02-12 15:18:18 +01:00
git@daemon.de
2bd22cfca6 fixed issue#8, now using File::Temp 2015-01-12 11:17:34 +01:00
git@daemon.de
3d80bb1608 made Bytes::Random::Secure optional, version++ 2012-11-19 11:57:15 +01:00
Marcin Kasperski
3bbb724b08 (needs careful review)
Attempt to improve performance.

Previous implementation happened to be very slow (on my laptop it took 5
minutes to read small pwsafe file and save it back). I profiled the code
and it turned out, this cost was totally dominated by the
Crypt::PWSafe3::random function (which on every call accesses system
random seed).

I replaced it with Bytes::Random::Secure which seeds using OS crypto but
afterwards uses embedded generator. Performance improvement is drastical,
the same read&save takes about half a second on the same laptop.
2012-11-18 00:46:34 +01:00
TLINDEN
5c28e1f954 first commit 2012-07-20 12:58:07 +02:00