Summary: | [maintainer-update] update security/p5-Crypt-PWSafe3 to 1.22 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | alexander.4mail | ||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Some People | CC: | arved | ||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
committed, thanks. Please remember to reset PORTREVISION on next update A commit references this bug: Author: arved Date: Wed May 11 14:00:42 UTC 2016 New revision: 414994 URL: https://svnweb.freebsd.org/changeset/ports/414994 Log: Update to 1.22 PR: 209451 Submitted by: maintainer Changes: head/security/p5-Crypt-PWSafe3/Makefile head/security/p5-Crypt-PWSafe3/distinfo |
Created attachment 170209 [details] p5-Crypt-PWSafe3-1.22.diff Update to version 1.22. From changelog: Records created by Crypt::PWSafe3 (eg. the ones fetched with getrecords) are now associated with the parent object, so that you can modify them directly and call $vault->save afterwards without using $vault->modifyrecord. Erase passwd from memory using zeros instead of random bytes. fixes github#9. Fixed rt.cpan.org#112975: Crypt::ECB (which we use) have been reworked and among other issues it fixed handline of padding. PWSafe3.pm did not specify a padding scheme (because it doesn't use it) and therefore Crypt::ECB enforced a default scheme which lead to an invalid key size. Now we specify explicitly padding:none, as suggested by Christoph Appel.