pkgsrc/security/dropbear, branch pkgsrc_2008Q1

Honor PKG_SYSCONFDIR. The default host keys for dropbear are now found in

2007-09-06T19:15:10Z

${PKG_SYSCONFDIR}/dropbear. Bump the PKGREVISION to 2.

Install the manual pages for dropbear. Bump the PKGREVISION to 1.

2007-09-06T16:31:55Z

Put variable declarations at beginning of a block to work with older

2007-09-06T16:07:51Z

compilers.

For the "pam" package option, one needs to include pam.buildlink3.mk.

2007-09-06T15:55:06Z

update to 0.50

2007-09-05T21:08:06Z

changes: - Add DROPBEAR_PASSWORD environment variable to specify a dbclient password - Use /dev/urandom by default, since that's what everyone does anyway - Exit with an exit code of 1 if dropbear can't bind to any ports - Improve network performance and add a -W argument for adjusting the tradeoff between network performance and memory consumption - Fix a problem where reply packets could be sent during key exchange, in violation of the SSH spec. This could manifest itself with connections being terminated after 8 hours with new TCP-forward connections being established - Add -K argument, ensuring that data is transmitted over the connection at least every N seconds - dropbearkey will no longer generate DSS keys of sizes other than 1024 bits, as required by the DSS specification. (Other sizes are still accepted for use to provide backwards compatibility)

update to 0.49

2007-03-23T20:07:02Z

change: warn strongly when a hostkey mismatch occurred

update to 0.48.1

2006-03-14T20:03:43Z

changes: -a security fix which was already in pkgsrc (0.46nb1) -bugfixes -zlib compression for dbclient -Set "low delay" TOS bit -client keyboard-interactive mode support -logging improvements -Added aes-256 cipher and sha1-96 hmac -allow connections to listening forwarded ports from remote machines

Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no

2006-03-04T21:28:51Z

developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.

Recursive revision bump / recommended bump for gettext ABI change.

2006-02-05T23:08:03Z

Prefer NAME_MAX over MAXNAMLEN.

2006-01-19T23:53:54Z