summaryrefslogtreecommitdiff
path: root/security/sshpass
AgeCommit message (Collapse)AuthorFilesLines
2021-10-26security: Replace RMD160 checksums with BLAKE2s checksumsnia1-2/+2
All checksums have been double-checked against existing RMD160 and SHA512 hashes Unfetchable distfiles (fetched conditionally?): ./security/cyrus-sasl/distinfo cyrus-sasl-dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d.patch.v2
2021-10-07security: Remove SHA1 hashes for distfilesnia1-2/+1
2020-03-20*: Convert broken sourceforge HOMEPAGEs back to httpnia1-2/+2
2020-01-18all: migrate several HOMEPAGEs to httpsrillig1-2/+2
pkglint --only "https instead of http" -r -F With manual adjustments afterwards since pkglint 19.4.4 fixed a few indentations in unrelated lines. This mainly affects projects hosted at SourceForce, as well as freedesktop.org, CTAN and GNU.
2018-05-06sshpass: update to 1.06 and patch to fix tty issuegavan3-7/+22
Changes since 1.0.5: Version 1.06 * Add -P for overriding the password prompt we search for * Add -v for verbose logging of the prompt detection prompt. * Allow packagers and compilers to change the default password prompt. * When giving -V, also print the default password prompt. Also, add patch from FreeBSD to fix tty issue which prevents sshpass from seeing the password prompt.
2017-09-16Reset maintainerwiz1-2/+2
2015-11-04Add SHA512 digests for distfiles for security categoryagc1-1/+2
Problems found locating distfiles: Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz Package libidea: missing distfile libidea-0.8.2b.tar.gz Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2 Package uvscan: missing distfile vlp4510e.tar.Z Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2013-05-26Import sshpass-1.05 as security/sshpass.rodent4-0/+26
Sshpass is a tool for non-interactively performing password authentication with SSH's so called "interactive keyboard password authentication". Most users should use SSH's more secure public key authentication instead.