summaryrefslogtreecommitdiff
path: root/security
AgeCommit message (Collapse)AuthorFilesLines
2004-08-31Update to 3.9p1:wiz14-89/+89
* Added new "IdentitiesOnly" option to ssh(1), which specifies that it should use keys specified in ssh_config, rather than any keys in ssh-agent(1) * Make sshd(8) re-execute itself on accepting a new connection. This security measure ensures that all execute-time randomisations are reapplied for each connection rather than once, for the master process' lifetime. This includes mmap and malloc mappings, shared library addressing, shared library mapping order, ProPolice and StackGhost cookies on systems that support such things * Add strict permission and ownership checks to programs reading ~/.ssh/config NB ssh(1) will now exit instead of trying to process a config with poor ownership or permissions * Implemented the ability to pass selected environment variables between the client and the server. See "AcceptEnv" in sshd_config(5) and "SendEnv" in ssh_config(5) for details * Added a "MaxAuthTries" option to sshd(8), allowing control over the maximum number of authentication attempts permitted per connection * Added support for cancellation of active remote port forwarding sessions. This may be performed using the ~C escape character, see "Escape Characters" in ssh(1) for details * Many sftp(1) interface improvements, including greatly enhanced "ls" support and the ability to cancel active transfers using SIGINT (^C) * Implement session multiplexing: a single ssh(1) connection can now carry multiple login/command/file transfer sessions. Refer to the "ControlMaster" and "ControlPath" options in ssh_config(5) for more information * The sftp-server has improved support for non-POSIX filesystems (e.g. FAT) * Portable OpenSSH: Re-introduce support for PAM password authentication, in addition to the keyboard-interactive driver. PAM password authentication is less flexible, and doesn't support pre-authentication password expiry but runs in-process so Kerberos tokens, etc are retained * Improved and more extensive regression tests * Many bugfixes and small improvements
2004-08-31Updated dropbear to 0.43martti3-14/+10
- SECURITY: Don't try to free() uninitialised variables in DSS verification code. Thanks to Arne Bernin for pointing out this bug. This is possibly exploitable, all users with DSS and pubkey-auth compiled in are advised to upgrade. - Clean up agent forwarding socket files correctly, patch from Gerrit Pape. - Don't go into an infinite loop when portforwarding to servers which don't send any initial data/banner. Patch from Nikola Vladov - Fix for network vs. host byte order in logging remote TCP ports, also from Gerrit Pape. - Initialise many pointers to NULL, for general safety. Also checked cleanup code for mp_ints (related to security issues above).
2004-08-30Fix paths to tclsh and wish, which were being found in the buildlinkjmmv3-6/+15
directory. Bump PKGREVISION to 4. From Ryo HAYASAKA in PR pkg/26808.
2004-08-28Back out previous... unintended commit.jlam1-3/+3
2004-08-28Use the new BUILDLINK_TRANSFORM commands to more precisely state thejlam1-3/+3
intended transformation: use "rm" to remove an option, "rmdir" to remove all options containing a path starting with a given directory name, and "rename" to rename options to something else.
2004-08-27+xmlsec1drochner1-1/+2
2004-08-27import xmlsec1-1.2.6, an XML signature and encryption librarydrochner4-0/+244
2004-08-27update to 1.0.20drochner3-13/+15
changes: -bugfixes -adds some limits to the verification functions to avoid denial of service attacks -selftests added
2004-08-27update to 0.5.5drochner3-8/+8
changes: Severeal cleanups and Libgcrypt 1.2.0 adjustments.
2004-08-27Replace RPATH_FLAG with LINKER_RPATH_FLAG and COMPILER_RPATH_FLAG,jlam1-2/+2
which are the full option names used to set rpath directives for the linker and the compiler, respectively. In places were we are invoking the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is inserted in case the flag is a word, e.g. -rpath. The default values of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the compiler that you use. They may be overridden on a ${OPSYS}-specific basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG, respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
2004-08-26add back idea.c.gz (from USE_IDEA=yes). (hi wiz!)lukem1-1/+3
2004-08-26Update to 1.2.6:wiz3-21/+5
* Updated the included gettext. This also fixes the installation problem from 1.2.5 * Fixed a race condition possibly leading to deleted keys.
2004-08-24Restore USE_LIBTOOL which was silently removed recently (hi xtraeme!).cube3-7/+17
Fix build with recent libtool. Not bumping PKGREVISION, it's in the flow of current PLIST fixes and such...
2004-08-24visudo(8) is still in ${PREFIX}/sbin, at least on NetBSD 2.0_BETA.schmonz1-2/+2
2004-08-24Add missing files.xtraeme2-4/+6
2004-08-23Update security/sudo to 1.6.8 and convert to use bsd.options.mk, whichxtraeme6-43/+44
adds two new options, ldap and pam. Changes: * Sudo now supports storing sudoers info in LDAP (optionally using TLS). * There is a new -e option to edit files the with uid of the invoking user. This makes it possible to give users to ability to safely edit files without the possibility of editing other files or running commands as the target user. If sudo is run as "sudoedit" the -e flag is implied. * A new tag, NOEXEC, will prevent a dynamically-linked program being run by sudo from executing another program (think shell escapes). Because this uses LD_PRELOAD it has no effect on static binaries. * A uid specified in sudoers now matches the user specified by the -u flag even if the -u flag specified a name, not a uid. * Added a -i option to simulate an initial login similar to "su -". * If sudo is used to run as root shell, further sudo commands will be logged as run by the user specified by the SUDO_USER environment variable. In -e mode (sudoedit), SUDO_USER is used to determine what user to run the editor when the real uid is 0. * The sudoers file is now parsed as the runas user in all cases instead of root. This fixes some issues with running NFS-mounted commands. * If the target user == invoking user a password is no longer required. * Sudo now produces a sensible error message when the targetpw Defaults option is set and a non-existent uid is specified via the -u option. * A negated user/uid in a runas list is now treated the same as a negated command and overrides a previously allowed entry. * PAM support now uses Use pam_acct_mgmt() to check for disabled accounts. * Added a check in visudo for runas_default being used before it was set. * Fixed several issues when closing all open descriptors. Sudo now uses closefrom() if it exists, otherwise it uses /proc/$$/fd if that exists with a fallback of closing all possible descriptors. * Quoting globbing characters with a backslash now works as documented. * Fixed a problem on FreeBSD (and perhaps others) when the user is only listed in NIS (not master.passwd) and netgroups are used in the master.passwd file. * The username in a log entry is no longer truncated at 8 characters. * Added a "sudo_lecture" option that can point to a file containing a custom lecture. * The timeout for password reading is now done via alarm(), not select(). * /tmp/.odus is no longer used for timestamps by default. * Sudo now works on the nsr-tandem-nsk platform. * Fixed the --with-stow configure option. * TIS fwtk authentication now supports fwtk 2.0 and higher. * Added Stan Lee / Uncle Ben quote to the lecture from RedHat. * Added the --with-pc-insults configure to replace politically incorrect insults with other ones.
2004-08-22Change the way that legacy USE_* and FOO_USE_* options are convertedjlam9-84/+28
into the bsd.options.mk framework. Instead of appending to ${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes the default options to be the union of PKG_DEFAULT_OPTIONS and any old USE_* and FOO_USE_* settings. This fixes PR pkg/26590.
2004-08-22Bump PKGREVISION to 2 for the gpgme BUILDLINK_DEPENDS change.recht1-2/+2
2004-08-22update to gpgme-0.9.0recht5-17/+17
Noteworthy changes in version 0.9.0 (unreleased) ------------------------------------------------ * The type gpgme_key_t has now a new field keylist_mode that contains the keylist mode that was active at the time the key was retrieved. * The type gpgme_decrypt_result_t has a new field "wrong_key_usage" that contains a flag indicating that the key should not have been used for encryption. * Verifying a signature of a revoked key gives the correct result now (GPG_ERR_CERT_REVOKED error code). * Clarified that the error code GPG_ERR_NO_DATA from the decrypt & verify operations still allows you to look at the signature verification result. * Clarified that patterns in keylisting operations have an upper limit, and thus are not suited to list many keys at once by their fingerprint. Also improve the error message if the pattern is too long for the CMS protocol to handle. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_key_t EXTENDED: New field keylist_mode. gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Set the 0.9.0 versions as BUILDLINK_DEPENDS in the buildlink3.mk for the library major version changes.
2004-08-21Update to 0.4.7.markd4-18/+18
Noteworthy changes in version 0.4.7 (2004-04-29) ------------------------------------------------ * Correctly initialize the fields expired, revoked, invalid, and disabled in the gpgme_key_t structures. * A bug fix: The flag wrong_key_usage of gpgme_signature_t was accidently of type int instead unsigned int. Noteworthy changes in version 0.4.6 (2004-04-06) ------------------------------------------------ * Bug fixes Noteworthy changes in version 0.4.5 (2004-03-07) ------------------------------------------------ * GPGME is now compiled with LFS (large file support) by default. * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of the listed keys. * New interface gpgme_cancel() that can be used to cancel asynchronous operations. Noteworthy changes in version 0.4.4 (2004-01-12) ------------------------------------------------ * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has been renamed to "sig_class", to avoid clash with C++ compilers. In the C API, the old name "class" has been preserved for backwards compatibility, but is deprecated.
2004-08-19Whitespace nit.jlam1-2/+2
2004-08-17- Update to scanssh 2.0adrianp4-16/+20
- ok'ed snj@/wiz@ From the ChangeLog: Supports open proxy detection. High performance by using libevent.
2004-08-14- Update to 2.0.4adrianp7-69/+34
- Replace SED with SUBST.* - Improve DESCR - ok'ed snj@/wiz@ From the Changelog: Verison 2.0.4: -------------- More signatures. Improved documentation, mentions of p0f_db, etc. [BUG] Fixed a minor problem with installation on systems w/o /usr/man/. [BUG] Fixed a DLT_NULL problem, added a new loopback signature. Multiple timestamp options, timestamps now read from pcap dumps. Sync with new Windows port code. [BUG] Fixed one-line reporting for masquerade detection.
2004-08-13Add and enable the cy2-* plugins.jlam1-1/+7
2004-08-13Initial import of security/cy2-plain, the SASL PLAIN AUTH plugin.jlam3-0/+34
2004-08-13Initial import of security/cy2-otp, the SASL OTP AUTH plugin.jlam3-0/+37
2004-08-13Initial import of security/cy2-gssapi, the SASL GSSAPI AUTH plugin.jlam3-0/+40
2004-08-13Initial import of security/cy2-digestmd5, the SASL DIGEST-MD5 AUTH plugin.jlam3-0/+38
2004-08-13Initial import of security/cy2-crammd5, the SASL CRAM-MD5 AUTH plugin.jlam3-0/+34
2004-08-13Initial import of security/cy2-anonymous, the SASL ANONYMOUS AUTH plugin.jlam3-0/+34
2004-08-13Split out the plugins into individual packages. This allows us tojlam6-111/+49
explicitly add only those plugins for SASL support for servers that won't let us exclude any found SASL plugins. Also, don't bother building the static library since the static library is useless until the build mechanism is fixed by the Cyrus maintainers. Bump the PKGREVISION.
2004-08-13- Include readline to fix Linux buildsadrianp1-3/+8
- Add Python support - Include an extra library on Linux to fix builds on some distros. Last two issues submitted by Roland Illig in PR# 26620
2004-08-13Add and enable hydanagc1-1/+2
2004-08-13Initial import of hydan-0.13 into the Packages Collection.agc4-0/+59
Hydan steganographically conceals a message into an application. It exploits redundancy in the i386 instruction set by defining sets of functionally equivalent instructions. It then encodes information in machine code by using the appropriate instructions from each set. Features: - Application filesize remains unchanged - Message is blowfish encrypted with a user-supplied passphrase before being embedded - Encoding rate: 1/110 Primary uses for Hydan: - Covert Communication: embedding data into binaries creates a covert channel that can be used to exchange secret messages. - Signing: a program's cryptographic signature can be embedded into itself. The recipient of the binary can then verify that it has not been tampered with (virus or trojan), and is really from who it claims to be from. This check can be built into the OS for user transparency. - Watermarking: a watermark can be embedded to uniquely identify binaries for copyright purposes, or as part of a DRM scheme. Note: this usage is not recommended as Hydan implements fragile watermarks.
2004-08-13Cosmetic changes.jlam2-9/+7
2004-08-13The name of this package is "cy2-sql".jlam1-5/+4
2004-08-12First cut at supporting the built-in PAM on MacOS X. It's not thejlam1-1/+20
same as Linux-PAM, but it's close enough for the purposes of compiling programs.
2004-08-09Fix PLIST.tv1-2/+2
2004-08-08Update shared library version.taca1-2/+2
2004-08-07Update samba2 package to 2.2.10jdolecek2-4/+4
Changes in 2.2.10: A buffer overrun has been located in the code used to support the 'mangling method = hash' smb.conf option. Affected Samba 2.2 installations can avoid this possible security bug by using the hash2 mangling method. Server installations requiring the hash mangling method are encouraged to upgrade to Samba v2.2.10 or v3.0.5. Changes in 2.2.9: This is a maintenance release of Samba 2.2.8a to address the problem with user password changes after applying the Microsoft hotfix described in KB828741 to Windows NT 4.0/200x/XP clients. Also updated dependant packages pam-smbpass and winbind.
2004-08-07fix DEPENDS to use ../../net/samba2 (this is samba2-only pkg)jdolecek1-2/+2
2004-08-06Append to CFLAGS on SunOS to avoid recursion. Fixes pkg/23475.sketch2-4/+4
2004-08-06Reorder conditions so that if make does short-circuit boolean evalutation,jlam1-3/+3
then we avoid hitting the disk if we don't need to.
2004-08-06Accidentally reversed meaning of test.jlam1-2/+2
2004-08-06Redo previous to say what we really want: we don't care if ${LOCALBASE}jlam1-2/+7
is "/usr", what we really want to check is if the pam_appl.h header found is within the ${LOCALBASE} hierarchy, which implies that it's a pkgsrc-controlled file, and hence not built-in.
2004-08-06Add and enable amavisd-new.jlam1-1/+2
2004-08-06Reimport mail/amavisd-new as security/amavisd-new.jlam9-0/+404
amavisd-new is an interface between message transfer agent (MTA) and one or more content checkers, e.g. virus scanners, SpamAssassin, etc. It is a performance-enhanced and feature-enriched version of amavisd (which in turn is a daemonized version of AMaViS or amavis-perl). amavisd-new is normally positioned at or near a central mailer, not necessarily where user's mailboxes and final delivery takes place. If you are looking for fully per-user configurable and/or low-message-rate solution to be placed at the final stage of mail delivery (e.g. called from procmail), there may be other solutions more appropriate for your needs. Package created and maintained by Julian Dunn in pkgsrc-wip.
2004-08-06There is no way for libtool to generate a convenience library thatjlam6-3/+145
can be used to create shared libraries _and_ be linked into a statically linked program. Instead of trying to hack libtool to do this, just accept the fact and do what you want another way! Remove the ugly hack in sasldb/Makefile.am that regenerated the static archive from the non-PIC object files. While this was fine for linking into programs, it breaks things when you link this into the sasldb plugin. Leaving it the other way, where the static archive from the PIC object files, is also unacceptable because there are potential problems on some platforms when linking an archive of of PIC objects into an executable. The solution: let the static archive contain PIC objects and be used to link into the sasldb plugin, but for the programs in the utils directory, explicitly add the non-PIC object files listed in $(SASL_DB_BACKEND_STATIC) to the files used to generate the programs. This is easy because SASL_DB_BACKEND_STATIC is already generated properly by config/sasldb.m4, so make use if it. This should fix problems with using Cyrus SASL on non-i386 platforms noted in PR pkg/26492 by Matt Dainty. Bump the PKGREVISION.
2004-08-06In the rare case when LOCALBASE is /usr, don't let this thinkreed1-2/+2
that /usr/include/security/pam_appl.h means that PAM is builtin. (This is so a dependency can be registered correctly.)
2004-08-05Regen to make GNU patch happy.minskim2-11/+5
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-11 18:08:40 +0000