[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2020-08-28T17:24:17Z 2020-08-28T17:24:17Z wiz wiz@pkgsrc.org 2020-08-28T17:24:17Z urn:sha1:667d49348a83a674cb5b9322da1b093717ce7809 Changes not found. 2020-02-28T11:19:53Z wiz wiz@pkgsrc.org 2020-02-28T11:19:53Z urn:sha1:5dd40cd2b27979d85e1c29224b1999db0941e57d Enable libscrypt-kdf. Add bl3.mk file. 2020-01-18T21:48:19Z jperkin jperkin@pkgsrc.org 2020-01-18T21:48:19Z urn:sha1:8930f4c9f76a4da06832827313f3853309f92baf 2019-11-04T21:12:51Z rillig rillig@pkgsrc.org 2019-11-04T21:12:51Z urn:sha1:805b440f10356ac31240fdb9960107d1f547f52f pkglint -Wall -F --only aligned --only indent -r No manual corrections. 2019-09-16T05:13:28Z wiz wiz@pkgsrc.org 2019-09-16T05:13:28Z urn:sha1:912c39ae2d9fba3f7a18c27f7dd7a22c96de4e82 Significant changes since 1.2.1: * In addition to the scrypt command-line utility, a library "libscrypt-kdf" can now be built and installed by passing the --enable-libscrypt-kdf option to configure. * On x86 CPUs which support them, RDRAND and SHA extensions are used to provide supplemental entropy and speed up hash computations respectively. * When estimating the amount of available RAM, scrypt ignores RLIMIT_DATA on systems which have mmap. * A new command "scrypt info encfile" prints information about an encrypted file without decrypting it. 2017-04-26T14:54:59Z wiz wiz@pkgsrc.org 2017-04-26T14:54:59Z urn:sha1:38a53e14b9ed0e053e2ec373d6d58ca774ab6cf9 Significant changes since 1.2.0: * A new -v option instructs scrypt to print the key derivation parameters it has selected. * A new --version option prints the version number of the scrypt utility. * A new -P option make scrypt read the passphrase from standard input; this is designed for scripts which pipe a passphrase in from elsewhere. * A new -f option makes 'scrypt dec' ignore the amount of memory or CPU time it thinks decrypting a file will take, and proceed anyway; this may be useful in cases where scrypt's estimation is wrong. * The '-M maxmem' option now accepts "humanized" inputs, e.g., "-M 1GB". There are also a variety of less visible changes: Performance improvements in the SHA256 routines, minor bug and compiler warning fixes, the addition of a test suite, and some minor code reorganization. 2016-03-05T11:27:40Z jperkin jperkin@pkgsrc.org 2016-03-05T11:27:40Z urn:sha1:ee3e800374a703dffb75012abfd6460dc7e71dbb 2015-08-23T14:42:30Z wiz wiz@pkgsrc.org 2015-08-23T14:42:30Z urn:sha1:5f1dff4b361d57ce59cc9b28160f209aead38b75 Significant changes since 1.1.6: * You can now specify "-" as the input file, meaning standard input. * Lots and lots of code reorganization, including changes to the build system. * scrypt now consults the hw.memsize sysctl on relevant platforms to figure out how much memory is available. (This should help on OS X.) * scrypt now detects and uses AESNI instructions for encryption/decryption. * scrypt now detects and uses SSE2 instructions automatically (and thus there is no longer an --enable-sse2 option to the configure script). 2014-02-26T18:20:11Z wiedi wiedi@pkgsrc.org 2014-02-26T18:20:11Z urn:sha1:fd9db286ac8686c2db9629ab26a9e29c31e99a1e 2012-10-17T22:17:47Z pettai pettai@pkgsrc.org 2012-10-17T22:17:47Z urn:sha1:2281e8547b4bff4640601653596216adcfdee187 of the scrypt key derivation function. On modern hardware and with default parameters, the cost of cracking the password on a file encrypted by scrypt enc is approximately 100 billion times more than the cost of cracking the same password on a file encrypted by openssl enc; this means that a five- character password using scrypt is stronger than a ten-character password using openssl