| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
security/libgcrypt: security fix
Revisions pulled up:
- security/libgcrypt/Makefile 1.74
- security/libgcrypt/distinfo 1.62
---
Module Name: pkgsrc
Committed By: wiz
Date: Thu Feb 11 13:36:37 UTC 2016
Modified Files:
pkgsrc/security/libgcrypt: Makefile distinfo
Log Message:
Update libgcrypt to 1.6.5:
Noteworthy changes in version 1.6.5 (2016-02-09) [C20/A0/R5]
------------------------------------------------
* Mitigate side-channel attack on ECDH with Weierstrass curves
[CVE-2015-7511]. See http://www.cs.tau.ac.IL/~tromer/ecdh/ for
details.
* Fix build problem on Solaris.
|
|
security/sudo: build fix
Revisions pulled up:
- security/sudo/Makefile 1.148-1.149
- security/sudo/PLIST 1.9
- security/sudo/distinfo 1.85-1.86
- security/sudo/options.mk 1.19
- security/sudo/patches/patch-aa 1.32
---
Module Name: pkgsrc
Committed By: adam
Date: Tue Jan 5 17:05:00 UTC 2016
Modified Files:
pkgsrc/security/sudo: Makefile distinfo
Log Message:
Fix building on OS X; cosmetic changes; fix distinfo
---
Module Name: pkgsrc
Committed By: adam
Date: Sat Jan 9 11:22:12 UTC 2016
Modified Files:
pkgsrc/security/sudo: Makefile PLIST distinfo options.mk
pkgsrc/security/sudo/patches: patch-aa
Log Message:
Add nls as an option, but also fix builds where system gettext gets detected and used.
|
|
security/sudo: security fix
Revisions pulled up:
- security/sudo/Makefile 1.147
- security/sudo/PLIST 1.8
- security/sudo/distinfo 1.84
- security/sudo/patches/patch-aa 1.31
- security/sudo/patches/patch-af 1.32
- security/sudo/patches/patch-ag 1.23
- security/sudo/patches/patch-logging.c deleted
- security/sudo/patches/patch-plugins_sudoers_Makefile.in 1.1
- security/sudo/patches/patch-plugins_sudoers_logging.c 1.1
- security/sudo/patches/patch-src_Makefile.in 1.1
---
Module Name: pkgsrc
Committed By: spz
Date: Fri Jan 1 17:00:49 UTC 2016
Modified Files:
pkgsrc/security/sudo: Makefile PLIST distinfo
pkgsrc/security/sudo/patches: patch-aa patch-af patch-ag
Added Files:
pkgsrc/security/sudo/patches: patch-plugins_sudoers_Makefile.in
patch-plugins_sudoers_logging.c patch-src_Makefile.in
Removed Files:
pkgsrc/security/sudo/patches: patch-logging.c
Log Message:
Update to 1.8.15, which fixes CVE-2015-5602, a symlink vulnerability in
sudoedit.
Note that it's a fairly large step and the package has only been tested
on NetBSD and there may be further breakage.
Testing on non-NetBSD would be appreciated.
Upstream changelog:
Major changes between version 1.8.15 and 1.8.14p3:
Fixed a bug that prevented sudo from building outside the source
tree on some platforms. Bug #708.
Fixed the location of the sssd library in the RHEL/Centos
packages. Bug #710.
Fixed a build problem on systems that don't implicitly include
sys/types.h from other header files. Bug #711.
Fixed a problem on Linux using containers where sudo would
ignore signals sent by a process in a different container.
Sudo now refuses to run a command if the PAM session module
returns an error.
When editing files with sudoedit, symbolic links will no longer
be followed by default. The old behavior can be restored by
enabling the sudoedit_follow option in sudoers or on a per-command
basis with the FOLLOW and NOFOLLOW tags. Bug #707.
Fixed a bug introduced in version 1.8.14 that caused the last
valid editor in the sudoers "editor" list to be used by visudo
and sudoedit instead of the first. Bug #714.
Fixed a bug in visudo that prevented the addition of a final
newline to edited files without one.
Fixed a bug decoding certain base64 digests in sudoers when
the intermediate format included a '=' character.
Individual records are now locked in the time stamp file instead
of the entire file. This allows sudo to avoid prompting for a
password multiple times on the same terminal when used in a
pipeline. In other words, sudo cat foo | sudo grep bar now only
prompts for the password once. Previously, both sudo processes
would prompt for a password, often making it impossible to
enter. Bug #705.
Fixed a bug where sudo would fail to run commands as a non-root
user on systems that lack both setresuid() and setreuid().
Bug #713.
Fixed a bug introduced in sudo 1.8.14 that prevented visudo
from re-editing the correct file when a syntax error was
detected.
Fixed a bug where sudo would not relay a SIGHUP signal to the
command when the terminal is closed and the command is not run
in its own pseudo-tty. Bug #719.
If some, but not all, of the LOGNAME, USER or USERNAME environment
variables have been preserved from the invoking user's
environment, sudo will now use the preserved value to set the
remaining variables instead of using the runas user. This
ensures that if, for example, only LOGNAME is present in the
env_keep list, that sudo will not set USER and USERNAME to the
runas user.
When the command sudo is running dies due to a signal, sudo
will now send itself that same signal with the default signal
handler installed instead of exiting. The bash shell appears
to ignore some signals, e.g. SIGINT, unless the command being
run is killed by that signal. This makes the behavior of commands
run under sudo the same as without sudo when bash is the shell.
Bug #722.
Slovak translation for sudo from translationproject.org.
Hungarian and Slovak translations for sudoers from
translationproject.org. Previously, when env_reset was enabled
(the default) and the -s option was not used, the SHELL
environment variable was set to the shell of the invoking user.
Now, when env_reset is enabled and the -s option is not used,
SHELL is set based on the target user.
Fixed challenge/response style BSD authentication.
Added the sudoedit_checkdir Defaults option to prevent sudoedit
from editing files located in a directory that is writable by
the invoking user.
Added the always_query_group_plugin Defaults option to control
whether groups not found in the system group database are passed
to the group plugin. Previously, unknown system groups were
always passed to the group plugin.
When creating a new file, sudoedit will now check that the
file's parent directory exists before running the editor.
Fixed the compiler stack protector test in configure for
compilers that support -fstack-protector but don't actually
have the ssp library available.
Major changes between version 1.8.14p3 and 1.8.14p2:
Fixed a bug introduced in sudo 1.8.14p2 that prevented sudo
from working when no tty was present. Bug #706.
Fixed tty detection on newer AIX systems where dev_t is 64-bit.
Major changes between version 1.8.14p2 and 1.8.14p1:
Fixed a bug introduced in sudo 1.8.14 that prevented the lecture
file from being created. Bug #704.
Major changes between version 1.8.14p1 and 1.8.14:
Fixed a bug introduced in sudo 1.8.14 that prevented the sssd
backend from working. Bug #703.
Major changes between version 1.8.14 and 1.8.13:
Log messages on Mac OS X now respect sudoers_locale when sudo
is build with NLS support.
The sudo manual pages now pass mandoc -Tlint with no warnings.
Fixed a compilation problem on systems with the sig2str()
function that do not define SIG2STR_MAX in signal.h.
Worked around a compiler bug that resulted in unexpected behavior
when returning an int from a function declared to return bool
without an explicit cast.
Worked around a bug in Mac OS X 10.10 BSD auditing where the
au_preselect() fails for AUE_sudo events but succeeds for
AUE_DARWIN_sudo.
Fixed a hang on Linux systems with glibc when sudo is linked
with jemalloc.
When the user runs a command as a user ID that is not present
in the password database via the -u flag, the command is now
run with the group ID of the invoking user instead of group ID 0.
Fixed a compilation problem on systems that don't pull in
definitions of uid_t and gid_t without sys/types.h or unistd.h.
Fixed a compilation problem on newer AIX systems which use a
struct st_timespec for time stamps in struct stat that differs
from struct timespec. Bug #702.
The example directory is now configurable via --with-exampledir
and defaults to DATAROOTDIR/examples/sudo on BSD systems.
The /usr/lib/tmpfiles.d/sudo.conf file is now installed as part
of "make install" when systemd is in use.
Fixed a linker problem on some systems with libintl. Bug #690.
Fixed compilation with compilers that don't support __func__
or __FUNCTION__.
Sudo no longer needs to uses weak symbols to support localization
in the warning functions. A registration function is used
instead.
Fixed a setresuid() failure in sudoers on Linux kernels where
uid changes take the nproc resource limit into account.
Fixed LDAP netgroup queries on AIX.
Sudo will now display the custom prompt on Linux systems with
PAM even if the "Password: " prompt is not localized by the
PAM module. Bug #701.
Double-quoted values in an LDAP sudoOption are now supported
for consistency with file-based sudoers.
Fixed a bug that prevented the btime entry in /proc/stat from
being parsed on Linux.
Major changes between version 1.8.13 and 1.8.12:
The examples directory is now a subdirectory of the doc dir to
conform to Debian guidelines. Bug #682.
Fixed a compilation error for siglist.c and signame.c on some
systems. Bug #686.
Weak symbols are now used for sudo_warn_gettext() and
sudo_warn_strerror() in libsudo_util to avoid link errors when
-Wl,--no-undefined is used in LDFLAGS. The --disable-weak-symbols
configure option can be used to disable the user of weak symbols.
Fixed a bug in sudo's mkstemps() replacement function that
prevented the file extension from being preserved in sudoedit.
A new mail_all_cmnds sudoers flag will send mail when a user
runs a command (or tries to). The behavior of the mail_always
flag has been restored to always send mail when sudo is run.
New MAIL and NOMAIL command tags have been added to toggle mail
sending behavior on a per-command (or Cmnd_Alias) basis.
Fixed matching of empty passwords when sudo is configured to
use passwd (or shadow) file authentication on systems where
the crypt() function returns NULL for invalid salts.
On AIX, sudo now uses the value of the auth_type setting in
/etc/security/login.cfg to determine whether to use LAM or PAM
for user authentication.
The all setting for listpw and verifypw now works correctly
with LDAP and sssd sudoers.
The sudo timestamp directory is now created at boot time on
platforms that use systemd.
Sudo will now restore the value of the SIGPIPE handler before
executing the command.
Sudo now uses struct timespec instead of struct timeval for
time keeping when possible. If supported, sudoedit and visudo
now use nanosecond granularity time stamps.
Fixed a symbol name collision with systems that have their own
SHA2 implementation. This fixes a problem where PAM could use
the wrong SHA2 implementation on Solaris 10 systems configured
to use SHA512 for passwords.
The editor invoked by sudoedit once again uses an unmodified
copy of the user's environment as per the documentation. This
was inadvertantly changed in sudo 1.8.0. Bug #688.
Major changes between version 1.8.12 and 1.8.11p2:
The embedded copy of zlib has been upgraded to version 1.2.8
and is now installed as a shared library where supported.
Debug settings for the sudo front end and sudoers plugin are
now configured separately.
Multiple sudo.conf Debug entries may now be specified per
program (or plugin).
The plugin API has been extended such that the path to the
plugin that was loaded is now included in the settings array.
This path can be used to register with the debugging subsystem.
The debug_flags setting is now prefixed with a file name and
may be specified multiple times if there is more than one
matching Debug setting in sudo.conf.
The sudoers regression tests now run with the locale set to C
since some of the tests compare output that includes
locale-specific messages. Bug #672.
Fixed a bug where sudo would not run commands on Linux when
compiled with audit support if audit is disabled. Bug #671.
Added __BASH_FUNC< to the environment blacklist to match Apple's
syntax for newer-style bash functions.
The default password prompt now includes a trailing space after
"Password:" for consistency with su(1) on most systems. Bug
#663.
Fixed a problem on DragonFly BSD where SIGCHLD could be ignored,
preventing sudo from exiting. Bug #676.
Visudo will now use the optional sudoers_file, sudoers_mode,
sudoers_uid and sudoers_gid arguments if specified on the
sudoers.so Plugin line in the sudo.conf file.
Fixed a problem introduced in sudo 1.8.8 that prevented the
full host name from being used when the fqdn sudoers option is
used. Bug #678.
French and Russian translations for sudoers from
translationproject.org.
Sudo now installs a handler for SIGCHLD signal handler immediately
before stating the process that will execute the command (or
start the monitor). The handler used to be installed earlier
but this causes problems with poorly behaved PAM modules that
install their own SIGCHLD signal handler and neglect to restore
sudo's original handler. Bug #657.
Removed a limit on the length of command line arguments expanded
by a wild card using sudo's version of the fnmatch() function.
This limit was introduced when sudo's version of fnmatch() was
replaced in sudo 1.8.4.
LDAP-based sudoers can now query an LDAP server for a user's
netgroups directly. This is often much faster than fetching
every sudoRole object containing a sudoUser that begins with
a `+' prefix and checking whether the user is a member of any
of the returned netgroups.
The mail_always sudoers option no longer sends mail for sudo
-l or sudo -v unless the user is unable to authenticate
themselves.
Fixed a crash when sudo is run with an empty argument vector.
Fixed two potential crashes when sudo is run with very low
resource limits.
The TZ environment variable is now checked for safety instead
of simply being copied to the environment of the command. This
fixes a potential security issue.
Major changes between version 1.8.11p2 and 1.8.11p1:
Fixed a bug where dynamic shared objects loaded from a plugin
could use the hooked version of getenv() but not the hooked
versions of putenv(), setenv() or unsetenv(). This can cause
problems for PAM modules that use those functions.
Major changes between version 1.8.11p1 and 1.8.11:
Fixed a compilation problem on some systems when the
--disable-shared-libutil configure option was specified.
The user can no longer interrupt the sleep after an incorrect
password on PAM systems using pam_unix. Bug #666.
Fixed a compilation problem on Linux systems that do not use
PAM. Bug #667.
"make install" will now work with the stock GNU autotools
install-sh script. Bug #669.
Fixed a crash with "sudo -i" when the current working directory
does not exist. Bug #670.
Fixed a potential crash in the debug subsystem when logging a
message larger that 1024 bytes.
Fixed a "make check" failure for ttyname when stdin is closed
and stdout and stderr are redirected to a different tty. Bug #643.
Added BASH_FUNC_* to environment blacklist to match newer-style
bash functions.
Major changes between version 1.8.11 and 1.8.10p3:
The sudoers plugin no longer uses setjmp/longjmp to recover
from fatal errors. All errors are now propagated to the caller
via return codes.
When running a command in the background, sudo will now forward
SIGINFO to the command (if supported).
Sudo will now use the system versions of the sha2 functions
from libc or libmd if available.
Visudo now works correctly on GNU Hurd. Bug #647.
Fixed suspend and resume of curses programs on some system when
the command is not being run in a pseudo-terminal. Bug #649.
Fixed a crash with LDAP-based sudoers on some systems when
Kerberos was enabled.
Sudo now includes optional Solaris audit support.
Catalan translation for sudoers from translationproject.org.
Norwegian Bokmaal translation for sudo from
translationproject.org.
Greek translation for sudoers from translationproject.org
The sudo source tree has been reorganized to more closely
resemble that of other gettext-enabled packages.
Sudo and its associated programs now link against a shared
version of libsudo_util. The --disable-shared-libutil configure
option may be used to force static linking if the
--enable-static-sudoers option is also specified.
The passwords in ldap.conf and ldap.secret may now be encoded
in base64.
Audit updates. SELinux role changes are now audited. For
sudoedit, we now audit the actual editor being run, instead of
just the sudoedit command.
Fixed bugs in the man page post-processing that could cause
portions of the manuals to be removed.
Fixed a crash in the system_group plugin. Bug #653.
Fixed sudoedit on platforms without a native version of the
getprogname() function. Bug #654.
Fixed compilation problems with some pre-C99 compilers.
Fixed sudo's -C option which was broken in version 1.8.9.
It is now possible to match an environment variable's value as
well as its name using env_keep and env_check. This can be used
to preserve bash functions which would otherwise be removed
from the environment.
New files created via sudoedit as a non-root user now have the
proper group id. Bug #656.
Sudoedit now works correctly in conjunction with sudo's SELinux
RBAC support. Temporary files are now created with the proper
security context.
The sudo I/O logging plugin API has been updated. If a logging
function returns an error, the command will be terminated and
all of the plugin's logging functions will be disabled. If a
logging function rejects the command's output it will no longer
be displayed to the user's terminal.
Fixed a compilation error on systems that lack openpty(),
_getpty() and grantpt(). Bug #660.
Fixed a hang when a sudoers source is listed more than once in
a single sudoers nsswitch.conf entry.
On AIX, shell scripts without a #! magic number are now passed
to /usr/bin/sh, not /usr/bin/bsh. This is consistent with what
the execvp() function on AIX does and matches historic sudo
behavior. Bug #661.
Fixed a cross-compilation problem building mksiglist and
mksigname. Bug #662.
Major changes between version 1.8.10p3 and 1.8.10p2:
Fixed expansion of the %p escape in the prompt for "sudo -l"
when rootpw, runaspw or targetpw is set. Bug #639.
Fixed matching of uids and gids which was broken in version
1.8.9. Bug #640.
PAM credential initialization has been re-enabled. It was
unintentionally disabled by default in version 1.8.8. The way
credentials are initialized has also been fixed. Bug #642.
Fixed a descriptor leak on Linux when determing boot time. Sudo
normally closes extra descriptors before running a command so
the impact is limited. Bug #645.
Fixed flushing of the last buffer of data when I/O logging is
enabled. This bug, introduced in version 1.8.9, could cause
incomplete command output on some systems. Bug #646.
Major changes between version 1.8.10p2 and 1.8.10p1:
Fixed a hang introduced in sudo 1.8.10 when timestamp_timeout
is set to zero. Bug #638.
Major changes between version 1.8.10p1 and 1.8.10:
Fixed a bug introduced in sudo 1.8.10 that prevented the
disabling of tty-based tickets.
Fixed a bug with netgated commands in "sudo -l command" that
could cause the command to be listed even when it was explicitly
denied. This only affected list mode when a command was specified.
Bug #636.
Major changes between version 1.8.10 and 1.8.9p5:
It is now possible to disable network interface probing in
sudo.conf by changing the value of the probe_interfaces setting.
When listing a user's privileges (sudo -l), the sudoers plugin
will now prompt for the user's password even if the targetpw,
rootpw or runaspw options are set.
The sudoers plugin uses a new format for its time stamp files.
Each user now has a single file which may contain multiple
records when per-tty time stamps are in use (the default). The
time stamps use a monotonic timer where available and are once
again located in a directory under /var/run. The lecture status
is now stored separately from the time stamps in a different
directory. Bug #616.
sudo's -K option will now remove all of the user's time stamps,
not just the time stamp for the current terminal. The -k option
can be used to only disable time stamps for the current terminal.
If sudo was started in the background and needed to prompt for
a password, it was not possible to suspend it at the password
prompt. This now works properly.
LDAP-based sudoers now uses a default search filter of
(objectClass=sudoRole) for more efficient queries. The netgroup
query has been modified to avoid falling below the minimum
length for OpenLDAP substring indices.
The new use_netgroups sudoers option can be used to explicitly
enable or disable netgroups support. For LDAP-based sudoers,
netgroup support requires an expensive substring match on the
server. If netgroups are not needed, this option can be disabled
to reduce the load on the LDAP server.
Sudo is once again able to open the sudoers file when the group
on sudoers doesn't match the expected value, so long as the
file is not group writable.
Sudo now installs an init.d script to clear the time stamp
directory at boot time on AIX and HP-UX systems. These systems
either lack /var/run or do not clear it on boot.
The JSON format used by visudo -x now properly supports the
negation operator. In addition, the Options object is now the
same for both Defaults and Cmnd_Specs.
Czech and Serbian translations for sudoers from
translationproject.org.
Catalan translation for sudo from translationproject.org.
Major changes between version 1.8.9p5 and 1.8.9p4:
Fixed a compilation error on AIX when LDAP support is enabled.
Fixed parsing of the "umask" defaults setting in sudoers. Bug
#632.
Fixed a failed assertion when the "closefrom_override" defaults
setting is enabled in sudoers and sudo's -C flag is used. Bug
#633.
Major changes between version 1.8.9p4 and 1.8.9p3:
Fixed a bug where sudo could consume large amounts of CPU while
the command was running when I/O logging is not enabled. Bug #631.
Fixed a bug where sudo would exit with an error when the debug
level is set to util@debug or all@debug and I/O logging is not
enabled. The command would continue runnning after sudo exited.
Major changes between version 1.8.9p3 and 1.8.9p2:
Fixed a bug introduced in sudo 1.8.9 that prevented the tty
name from being resolved properly on Linux systems. Bug #630.
Major changes between version 1.8.9p2 and 1.8.9p1:
Updated config.guess, config.sub and libtool to support the
ppc64le architecture (IBM PowerPC Little Endian).
Major changes between version 1.8.9p1 and 1.8.9:
Fixed a problem with gcc 4.8's handling of bit fields that
could lead to the noexec flag being enabled even when it was
not explicitly set.
Major changes between version 1.8.9 and 1.8.8:
Reworked sudo's main event loop to use a simple event subsystem
using poll(2) or select(2) as the back end.
It is now possible to statically compile the sudoers plugin
into the sudo binary without disabling shared library support.
The sudo.conf file may still be used to configure other plugins.
Sudo can now be compiled again with a C preprocessor that does
not support variadic macros.
Visudo can now export a sudoers file in JSON format using the
new -x flag.
The locale is now set correctly again for visudo and sudoreplay.
The plugin API has been extended to allow the plugin to exclude
specific file descriptors from the closefrom range.
There is now a workaround for a Solaris-specific problem where
NOEXEC was overriding traditional root DAC behavior.
Add user netgroup filtering for SSSD. Previously, rules for a
netgroup were applied to all even when they did not belong to
the specified netgroup.
On systems with BSD login classes, if the user specified a
group (not a user) to run the command as, it was possible to
specify a different login class even when the command was not
run as the super user.
The closefrom() emulation on Mac OS X now uses /dev/fd if
possible.
Fixed a bug where sudoedit would not update the original file
from the temporary when PAM or I/O logging is not enabled.
When recycling I/O logs, the log files are now truncated
properly.
Fixes bugs #617, #621, #622, #623, #624, #625, #626
Major changes between version 1.8.8 and 1.8.7:
Removed a warning on PAM systems with stacked auth modules
where the first module on the stack does not succeed.
Sudo, sudoreplay and visudo now support GNU-style long options.
The -h (--host) option may now be used to specify a host name.
This is currently only used by the sudoers plugin in conjunction
with the -l (--list) option.
Program usage messages and manual SYNOPSIS sections have been
simplified.
Sudo's LDAP SASL support now works properly with Kerberos.
Previously, the SASL library was unable to locate the user's
credential cache.
It is now possible to set the nproc resource limit to unlimited
via pam_limits on Linux (bug #565).
New pam_service and pam_login_service sudoers options that can
be used to specify the PAM service name to use.
New pam_session and pam_setcred sudoers options that can be
used to disable PAM session and credential support.
The sudoers plugin now properly supports UIDs and GIDs that
are larger than 0x7fffffff on 32-bit platforms.
Fixed a visudo bug introduced in sudo 1.8.7 where per-group
Defaults entries would cause an internal error.
If the tty_tickets sudoers option is enabled (the default),
but there is no tty present, sudo will now use a ticket file
based on the parent process ID. This makes it possible to
support the normal timeout behavior for the session.
Fixed a problem running commands that change their process
group and then attempt to change the terminal settings when
not running the command in a pseudo-terminal. Previously, the
process would receive SIGTTOU since it was effectively a
background process. Sudo will now grant the child the controlling
tty and continue it when this happens.
The closefrom_override sudoers option may now be used in a
command-specified Defaults entry (bug #610).
Sudo's BSM audit support now works on Solaris 11.
Brazilian Portuguese translation for sudo and sudoers from
translationproject.org.
Czech translation for sudo from translationproject.org.
French translation for sudo from translationproject.org.
Sudo's noexec support on Mac OS X 10.4 and above now uses
dynamic symbol interposition instead of setting
DYLD_FORCE_FLAT_NAMESPACE=1 which causes issues with some
programs.
Fixed visudo's -q (--quiet) flag, broken in sudo 1.8.6.
Root may no longer change its SELinux role without entering a
password.
Fixed a bug introduced in Sudo 1.8.7 where the indexes written
to the I/O log timing file are two greater than they should
be. Sudoreplay now contains a work-around to parse those files.
In sudoreplay's list mode, the this qualifier in fromdate or
todate expressions now behaves more sensibly. Previously, it
would often match a date that was "one more" than expected.
For example, "this week" now matches the current week instead
of the following week.
Major changes between version 1.8.7 and 1.8.6p8:
The non-Unix group plugin is now supported when sudoers data
is stored in LDAP.
Sudo now uses a workaround for a locale bug on Solaris 11.0
that prevents setuid programs like sudo from fully using locales.
User messages are now always displayed in the user's locale,
even when the same message is being logged or mailed in a
different locale.
Log files created by sudo now explicitly have the group set to
group ID 0 rather than relying on BSD group semantics (which
may not be the default).
A new exec_background sudoers option can be used to initially
run the command without read access to the terminal when running
a command in a pseudo-tty. If the command tries to read from
the terminal it will be stopped by the kernel (via SIGTTIN or
SIGTTOU) and sudo will immediately restart it as the forground
process (if possible). This allows sudo to only pass terminal
input to the program if the program actually is expecting it.
Unfortunately, a few poorly-behaved programs (like "su" on most
Linux systems) do not handle SIGTTIN and SIGTTOU properly.
Sudo now uses an efficient group query to get all the groups
for a user instead of iterating over every record in the group
database on HP-UX and Solaris.
Sudo now produces better error messages when there is an error
in the sudo.conf file.
Two new settings have been added to sudo.conf to give the admin
better control of how group database queries are performed.
The group_source specifies how the group list for a user will
be determined. Legal values are static (use the kernel groups
list), dynamic (perform a group database query) and adaptive
(only perform a group database query if the kernel list is
full). The max_groups setting specifies the maximum number of
groups a user may belong to when performing a group database
query.
The sudo.conf file now supports line continuation by using a
backslash as the last character on the line.
There is now a standalone sudo.conf manual page.
Sudo now stores its libexec files in a sudo subdirectory instead
of in libexec itself. For backwards compatibility, if the plugin
is not found in the default plugin directory, sudo will check
the parent directory if the default directory ends in /sudo.
The sudoers I/O logging plugin now logs the terminal size.
A new sudoers option maxseq can be used to limit the number of
I/O log entries that are stored.
The system_group and group_file sudoers group provider plugins
are now installed by default.
The list output (sudo -l) output from the sudoers plugin is
now less ambiguous when an entry includes different runas users.
The long list output (sudo -ll) for file-based sudoers is now
more consistent with the format of LDAP-based sudoers.
A uid may now be used in the sudoRunAsUser attributes for LDAP
sudoers.
Minor plugin API change: the close and version functions are
now optional. If the policy plugin does not provide a close
function and the command is not being run in a new pseudo-tty,
sudo may now execute the command directly instead of in a child
process.
A new sudoers option pam_session can be used to disable sudo's
PAM session support.
On HP-UX systems, sudo will now use the pstat() function to
determine the tty instead of ttyname().
Turkish translation for sudo and sudoers from
translationproject.org.
Dutch translation for sudo and sudoers from
translationproject.org.
Tivoli Directory Server client libraries may now be used with
HP-UX where libibmldap has a hidden dependency on libCsup.
The sudoers plugin will now ignore invalid domain names when
checking netgroup membership. Most Linux systems use the string
"(none)" for the NIS-style domain name instead of an empty
string.
New support for specifying a SHA-2 digest along with the command
in sudoers. Supported hash types are sha224, sha256, sha384
and sha512. See the description of Digest_Spec in the sudoers
manual or the description of sudoCommand in the sudoers.ldap
manual for details.
The paths to ldap.conf and ldap.secret may now be specified as
arguments to the sudoers plugin in the sudo.conf file.
Fixed potential false positives in visudo's alias cycle detection.
Fixed a problem where the time stamp file was being treated as
out of date on Linux systems where the change time on the
pseudo-tty device node can change after it is allocated.
Sudo now only builds Position Independent Executables (PIE) by
default on Linux systems and verifies that a trivial test
program builds and runs.
On Solaris 11.1 and higher, sudo binaries will now have the
ASLR tag enabled if supported by the linker.
Major changes between version 1.8.6p8 and 1.8.6p7:
Terminal detection now works properly on 64-bit AIX kernels.
This was broken by the removal of the ttyname() fallback in
Sudo 1.8.6p6. Sudo is now able to map an AIX 64-bit device
number to the corresponding device file in /dev.
Sudo now checks for crypt() returning NULL when performing
passwd-based authentication.
Major changes between version 1.8.6p7 and 1.8.6p6:
A time stamp file with the date set to the epoch by sudo -k is
now completely ignored regardless of what the local clock is
set to. Previously, if the local clock was set to a value
between the epoch and the time stamp timeout value, a time
stamp reset by sudo -k would be considered current. This is
a potential security issue.
The tty-specific time stamp file now includes the session ID
of the sudo process that created it. If a process with the same
tty but a different session ID runs sudo, the user will now be
prompted for a password (assuming authentication is required
for the command). This is a potential security issue.
Major changes between version 1.8.6p6 and 1.8.6p5:
On systems where the controlling tty can be determined via
/proc or sysctl(), sudo will no longer fall back to using
ttyname() if the process has no controlling tty. This prevents
sudo from using a non-controlling tty for logging and time
stamp purposes. This is a potential security issue.
Major changes between version 1.8.6p5 and 1.8.6p4:
Fixed a potential crash in visudo's alias cycle detection.
Improved performance on Solaris when retrieving the group list
for the target user. On systems with a large number of groups
where the group database is not local (NIS, LDAP, AD), fetching
the group list could take a minute or more.
Major changes between version 1.8.6p4 and 1.8.6p3:
The -fstack-protector is now used when linking visudo, sudoreplay
and testsudoers.
Avoid building PIE binaries on FreeBSD/ia64 as they don't run
properly.
Fixed a crash in visudo strict mode when an unknown Defaults
setting is encountered.
Do not inform the user that the command was not permitted by
the policy if they do not successfully authenticate. This is
a regression introduced in sudo 1.8.6.
Allow sudo to be build with sss support without also including
ldap support.
Fix running commands that need the terminal in the background
when I/O logging is enabled. E.g. sudo vi &. When the command
is foregrounded, it will now resume properly.
Major changes between version 1.8.6p3 and 1.8.6p2:
Fixed post-processing of the man pages on systems with legacy
versions of sed.
Fixed sudoreplay -l on Linux systems with file systems that
set DT_UNKNOWN in the d_type field of struct dirent.
Major changes between version 1.8.6p2 and 1.8.6p1:
Fixed suspending a command after it has already been resumed
once when I/O logging (or use_pty) is not enabled. This was a
regression introduced in version 1.8.6.
Major changes between version 1.8.6p1 and 1.8.6:
Fixed the setting of LOGNAME, USER and USERNAME variables in
the command's environment when env_reset is enabled (the
default). This was a regression introduced in version 1.8.6.
Sudo now honors SUCCESS=return in /etc/nsswitch.conf.
Major changes between version 1.8.6 and 1.8.5p3:
Sudo is now built with the -fstack-protector flag if the the
compiler supports it. Also, the -zrelro linker flag is used if
supported. The --disable-hardening configure option can be used
to build sudo without stack smashing protection.
Sudo is now built as a Position Independent Executable (PIE)
if supported by the compiler and linker.
If the user is a member of the exempt group in sudoers, they
will no longer be prompted for a password even if the -k flag
is specified with the command. This makes sudo -k command
consistent with the behavior one would get if the user ran sudo
-k immediately before running the command.
The sudoers file may now be a symbolic link. Previously, sudo
would refuse to read sudoers unless it was a regular file.
The sudoreplay command can now properly replay sessions where
no tty was present.
The sudoers plugin now takes advantage of symbol visibility
controls when supported by the compiler or linker. As a result,
only a small number of symbols are exported which significantly
reduces the chances of a conflict with other shared objects.
Improved support for the Tivoli Directory Server LDAP client
libraries. This includes support for using LDAP over SSL (ldaps)
as well as support for the BIND_TIMELIMIT, TLS_KEY and TLS_CIPHERS
ldap.conf options. A new ldap.conf option, TLS_KEYPW can be
used to specify a password to decrypt the key database.
When constructing a time filter for use with LDAP sudoNotBefore
and sudoNotAfter attributes, the current time now includes
tenths of a second. This fixes a problem with timed entries on
Active Directory.
If a user fails to authenticate and the command would be rejected
by sudoers, it is now logged with command not allowed instead
of N incorrect password attempts. Likewise, the mail_no_perms
sudoers option now takes precedence over mail_badpass
The sudo manuals are now formatted using the mdoc macros.
Versions using the legacy man macros are provided for systems
that lack mdoc.
New support for Solaris privilege sets. This makes it possible
to specify fine-grained privileges in the sudoers file on
Solaris 10 and above. A Runas_Spec that contains no Runas_Lists
can be used to give a user the ability to run a command as
themselves but with an expanded privilege set.
Fixed a problem with the reboot and shutdown commands on some
systems (such as HP-UX and BSD). On these systems, reboot sends
all processes (except itself) SIGTERM. When sudo received
SIGTERM, it would relay it to the reboot process, thus killing
reboot before it had a chance to actually reboot the system.
Support for using the System Security Services Daemon (SSSD)
as a source of sudoers data.
Slovenian translation for sudo and sudoers from
translationproject.org.
Visudo will now warn about unknown Defaults entries that are
per-host, per-user, per-runas or per-command.
Fixed a race condition that could cause sudo to receive SIGTTOU
(and stop) when resuming a shell that was run via sudo when
I/O logging (and use_pty) is not enabled.
Sending SIGTSTP directly to the sudo process will now suspend
the running command when I/O logging (and use_pty) is not
enabled.
Major changes between version 1.8.5p3 and 1.8.5p2:
Fixed the loading of I/O plugins that conform to a plugin API
version older than 1.2.
Major changes between version 1.8.5p2 and 1.8.5p1:
Fixed use of the SUDO_ASKPASS environment variable which was
broken in Sudo 1.8.5.
Fixed a problem reading the sudoers file when the file mode is
more restrictive than the expected mode. For example, when the
expected sudoers file mode is 0440 but the actual mode is 0400.
Major changes between version 1.8.5p1 and 1.8.5:
Fixed a bug that prevented files in an include directory from
being evaluated.
Major changes between version 1.8.5 and 1.8.4p5:
When "noexec" is enabled, sudo_noexec.so will now be prepended
to any existing LD_PRELOAD variable instead of replacing it.
The sudo_noexec.so shared library now wraps the execvpe(),
exect(), posix_spawn() and posix_spawnp() functions.
The user/group/mode checks on sudoers files have been relaxed.
As long as the file is owned by the sudoers uid, not
world-writable and not writable by a group other than the
sudoers gid, the file is considered OK. Note that visudo will
still set the mode to the value specified at configure time.
It is now possible to specify the sudoers path, uid, gid and
file mode as options to the plugin in the sudo.conf file.
Croatian, Galician, German, Lithuanian, Swedish and Vietnamese
translations from translationproject.org.
/etc/environment is no longer read directly on Linux systems
when PAM is used. Sudo now merges the PAM environment into the
user's environment which is typically set by the pam_env module.
The initial evironment created when env_reset is in effect now
includes the contents of /etc/environment on AIX systems and
the "setenv" and "path" entries from /etc/login.conf on BSD
systems.
The plugin API has been extended in three ways. First, options
specified in sudo.conf after the plugin pathname are passed to
the plugin's open function. Second, sudo has limited support
for hooks that can be used by plugins. Currently, the hooks
are limited to environment handling functions. Third, the
init_session policy plugin function is passed a pointer to the
user environment which can be updated during session setup.
The plugin API version has been incremented to version 1.2.
See the sudo_plugin manual for more information.
The policy plugin's init_session function is now called by the
parent sudo process, not the child process that executes the
command. This allows the PAM session to be open and closed in
the same process, which some PAM modules require.
Fixed parsing of "Path askpass" and "Path noexec" in sudo.conf,
which was broken in version 1.8.4.
On systems with an SVR4-style /proc file system, the
/proc/pid/psinfo file is now uses to determine the controlling
terminal, if possible. This allows tty-based tickets to work
properly even when, e.g. standard input, output and error are
redirected to /dev/null.
The output of "sudoreplay -l" is now sorted by file name (or
sequence number). Previously, entries were displayed in the
order in which they were found on the file system.
Sudo now behaves properly when I/O logging is enabled and the
controlling terminal is revoked (e.g. the running sshd is
killed). Previously, sudo may have exited without calling the
I/O plugin's close function which can lead to an incomplete
I/O log.
Sudo can now detect when a user has logged out and back in
again on Solaris 11, just like it can on Solaris 10.
The built-in zlib included with Sudo has been upgraded to
version 1.2.6.
Setting the SSL parameter to start_tls in ldap.conf now works
properly when using Mozilla-based SDKs that support the
ldap_start_tls_s() function.
The TLS_CHECKPEER parameter in ldap.conf now works when the
Mozilla NSS crypto backend is used with OpenLDAP.
A new group provider plugin, system_group, is included which
performs group look ups by name using the system groups database.
This can be used to restore the pre-1.7.3 sudo group lookup
behavior.
Major changes between version 1.8.4p5 and 1.8.4p4:
Fixed a potential security issue in the matching of hosts
against an IPv4 network specified in sudoers. The flaw may
allow a user who is authorized to run commands on hosts belonging
to one IPv4 network to run commands on a different host.
Major changes between version 1.8.4p4 and 1.8.4p3:
Fixed a bug introduced in Sudo 1.8.4 which prevented sudo -v
from working.
Major changes between version 1.8.4p3 and 1.8.4p2:
Fixed a crash on FreeBSD when there is no tty present.
When visudo is run with the -c (check) option, the sudoers
file(s) owner and mode are now also checked unless the -f option
was specified.
Major changes between version 1.8.4p2 and 1.8.4p1:
Fixed a bug introduced in Sudo 1.8.4 where insufficient space
was allocated for group IDs in the LDAP filter.
Fixed a bug introduced in Sudo 1.8.4 where the path to sudo.conf
was /sudo.conf instead of etc/sudo.conf.
Fixed a bug introduced in Sudo 1.8.4 which could cause a hang
when I/O logging is enabled and input is from a pipe or file.
Major changes between version 1.8.4p1 and 1.8.4:
Fixed a bug introduced in sudo 1.8.4 that broke adding to or
deleting from the env_keep, env_check and env_delete lists in
sudoers on some platforms.
Major changes between version 1.8.4 and 1.8.3p2:
The -D flag in sudo has been replaced with a more general
debugging framework that is configured in sudo.conf.
Fixed a false positive in visudo strict mode when aliases are
in use.
Fixed a crash with sudo -i when a runas group was specified
without a runas user.
The line on which a syntax error is reported in the sudoers
file is now more accurate. Previously it was often off by a
line.
Fixed a bug where stack garbage could be printed at the end of
the lecture when the lecture_file option was enabled.
make install now honors the LINGUAS environment variable.
The #include and #includedir directives in sudoers now support
relative paths. If the path is not fully qualified it is expected
to be located in the same directory of the sudoers file that
is including it.
New Serbian and Spanish translations for sudo from
translationproject.org.
LDAP-based sudoers may now access by group ID in addition to
group name.
visudo will now fix the mode on the sudoers file even if no
changes are made unless the -f option is specified.
The use_loginclass sudoers option works properly again.
On systems that use login.conf, sudo -i now sets environment
variables based on login.conf.
For LDAP-based sudoers, values in the search expression are
now escaped as per RFC 4515.
The plugin close function is now properly called when a login
session is killed (as opposed to the actual command being
killed). This can happen when an ssh session is disconnected
or the terminal window is closed.
The deprecated "noexec_file" sudoers option is no longer
supported.
Fixed a race condition when I/O logging is not enabled that
could result in tty-generated signals (e.g. control-C) being
received by the command twice.
If none of the standard input, output or error are connected
to a tty device, sudo will now check its parent's standard
input, output or error for the tty name on systems with /proc
and BSD systems that support the KERN_PROC_PID sysctl. This
allows tty-based tickets to work properly even when, e.g.
standard input, output and error are redirected to /dev/null.
Added the --enable-kerb5-instance configure option to allow
people using Kerberos V authentication to specify a custom
instance so the principal name can be, e.g. "username/sudo"
similar to how ksu uses "username/root".
Fixed a bug where a pattern like /usr/* included /usr/bin/ in
the results, which would be incorrectly be interpreted as if
the sudoers file had specified a directory.
visudo -c will now list any include files that were checked in
addition to the main sudoers file when everything parses OK.
Users that only have read-only access to the sudoers file may
now run visudo -c. Previously, write permissions were required
even though no writing is down in check-only mode.
It is now possible to prevent the disabling of core dumps from
within sudo itself by adding a line to the sudo.conf file like
Set disable_coredump false.
Major changes between version 1.8.3p2 and 1.8.3p1:
Fixed a format string vulnerability when the sudo binary (or
a symbolic link to the sudo binary) contains printf format
escapes and the -D (debugging) flag is used.
Major changes between version 1.8.3p1 and 1.8.3:
Fixed a crash in the monitor process on Solaris when NOPASSWD
was specified or when authentication was disabled.
Fixed matching of a Runas_Alias in the group section of a
Runas_Spec.
Major changes between version 1.8.3 and 1.8.2:
Fixed expansion of strftime() escape sequences in the log_dir
sudoers setting.
Esperanto, Italian and Japanese translations from
translationproject.org.
Sudo will now use PAM by default on AIX 6 and higher.
Added --enable-werror configure option for gcc's -Werror flag.
Visudo no longer assumes all editors support the +linenumber
command line argument. It now uses a whitelist of editors known
to support the option.
Fixed matching of network addresses when a netmask is specified
but the address is not the first one in the CIDR block.
The configure script now check whether or not errno.h declares
the errno variable. Previously, sudo would always declare errno
itself for older systems that don't declare it in errno.h.
The NOPASSWD tag is now honored for denied commands too, which
matches historic sudo behavior (prior to sudo 1.7.0).
Sudo now honors the DEREF setting in ldap.conf which controls
how alias dereferencing is done during an LDAP search.
A symbol conflict with the pam_ssh_agent_auth PAM module that
would cause a crash been resolved.
The inability to load a group provider plugin is no longer a
fatal error.
A potential crash in the utmp handling code has been fixed.
Two PAM session issues have been resolved. In previous versions
of sudo, the PAM session was opened as one user and closed as
another. Additionally, if no authentication was performed, the
PAM session would never be closed.
Sudo will now work correctly with LDAP-based sudoers using TLS
or SSL on Debian systems.
The LOGNAME, USER and USERNAME environment variables are
preserved correctly again in sudoedit mode.
Major changes between version 1.8.2 and 1.8.1p2:
Sudo, visudo, sudoreplay and the sudoers plug-in now have
natural language support (NLS). Sudo will use gettext(), if
available, to display translated messages. This can be disabled
by passing configure the --disable-nls option. All translations
are coordinated via The Translation Project,
translationproject.org. Sudo 1.8.2 includes translations for
Basque, Chinese (simplified), Danish, Finish, Polish, Russian
and Ukranian.
Plug-ins are now loaded with the RTLD_GLOBAL flag instead of
RTLD_LOCAL. This fixes missing symbol problems in PAM modules
on certain platforms, such as FreeBSD and SuSE Linux Enterprise.
I/O logging is now supported for commands run in background
mode (using sudo's -b flag).
Group ownership of the sudoers file is now only enforced when
the file mode on sudoers allows group readability or writability.
Visudo now checks the contents of an alias and warns about
cycles when the alias is expanded.
If the user specifes a group via sudo's -g option that matches
the target user's group in the password database, it is now
allowed even if no groups are present in the Runas_Spec.
The sudo Makefiles now have more complete dependencies which
are automatically generated instead of being maintained manually.
The use_pty sudoers option is now correctly passed back to the
sudo front end. This was missing in previous versions of sudo
1.8 which prevented use_pty from being honored.
sudo -i command now works correctly with the bash version 2.0
and higher. Previously, the .bash_profile would not be sourced
prior to running the command unless bash was built with
NON_INTERACTIVE_LOGIN_SHELLS defined.
When matching groups in the sudoers file, sudo will now match
based on the name of the group instead of the group ID. This
can substantially reduce the number of group lookups for sudoers
files that contain a large number of groups.
Multi-factor authentication is now supported on AIX.
Added support for non-RFC 4517 compliant LDAP servers that
require that seconds be present in a timestamp, such as Tivoli
Directory Server.
If the group vector is to be preserved, the PATH search for
the command is now done with the user's original group vector.
For LDAP-based sudoers, the runas_default sudoOption now works
properly in a sudoRole that contains a sudoCommand.
Spaces in command line arguments for sudo -s and sudo -i are
now escaped with a backslash when checking the security policy.
Major changes between version 1.8.1p2 and 1.8.1p1:
Two-character CIDR-style IPv4 netmasks are now matched correctly
in the sudoers file.
A build error with MIT Kerberos V has been resolved.
A crash on HP-UX in the sudoers plugin when wildcards are
present in the sudoers file has been resolved.
Sudo now works correctly on Tru64 Unix again.
Major changes between version 1.8.1p1 and 1.8.1:
Fixed a problem on AIX where sudo was unable to set the final
uid if the PAM module modified the effective uid.
A non-existent includedir is now treated the same as an empty
directory and not reported as an error.
Removed extraneous parens in LDAP filter when
sudoers_search_filter is enabled that can cause an LDAP search
error.
Fixed a make -j problem for make install
Major changes between version 1.8.1 and 1.8.0:
A new LDAP setting, sudoers_search_filter, has been added to
ldap.conf. This setting can be used to restrict the set of
records returned by the LDAP query. Based on changes from
Matthew Thomas.
White space is now permitted within a User_List when used in
conjunction with a per-user Defaults definition.
A group ID (%#gid) may now be specified in a User_List or
Runas_List. Likewise, for non-Unix groups the syntax is %:#gid.
Support for double-quoted words in the sudoers file has been
fixed. The change in 1.7.5 for escaping the double quote
character caused the double quoting to only be available at
the beginning of an entry.
The fix for resuming a suspended shell in 1.7.5 caused problems
with resuming non-shells on Linux. Sudo will now save the
process group ID of the program it is running on suspend and
restore it when resuming, which fixes both problems.
A bug that could result in corrupted output in "sudo -l" has
been fixed.
Sudo will now create an entry in the utmp (or utmpx) file when
allocating a pseudo-tty (e.g. when logging I/O). The "set_utmp"
and "utmp_runas" sudoers file options can be used to control
this. Other policy plugins may use the "set_utmp" and "utmp_user"
entries in the command_info list.
The sudoers policy now stores the TSID field in the logs even
when the "iolog_file" sudoers option is defined to a value
other than %{sessid}. Previously, the TSID field was only
included in the log file when the "iolog_file" option was set
to its default value.
The sudoreplay utility now supports arbitrary session IDs.
Previously, it would only work with the base-36 session IDs
that the sudoers plugin uses by default.
Sudo now passes "run_shell=true" to the policy plugin in the
settings list when sudo's -s command line option is specified.
The sudoers policy plugin uses this to implement the "set_home"
sudoers option which was missing from sudo 1.8.0.
The "noexec" functionality has been moved out of the sudoers
policy plugin and into the sudo front-end, which matches the
behavior documented in the plugin writer's guide. As a result,
the path to the noexec file is now specified in the sudo.conf
file instead of the sudoers file.
On Solaris 10, the PRIV_PROC_EXEC privilege is now used to
implement the "noexec" feature. Previously, this was implemented
via the LD_PRELOAD environment variable.
The exit values for "sudo -l", "sudo -v" and "sudo -l command"
have been fixed in the sudoers policy plugin.
The sudoers policy plugin now passes the login class, if any,
back to the sudo front-end.
The sudoers policy plugin was not being linked with requisite
libraries in certain configurations.
Sudo now parses command line arguments before loading any
plugins. This allows "sudo -V" or "sudo -h" to work even if
there is a problem with sudo.conf
Plugins are now linked with the static version of libgcc to
allow the plugin to run on a system where no shared libgcc is
installed, or where it is installed in a different location.
Major changes between version 1.8.0 and 1.7.5:
Sudo has been refactored to use a modular framework that can
support third-party policy and I/O logging plugins. The default
plugin is "sudoers" which provides the traditional sudo
functionality. See the sudo_plugin manual for details on the
plugin API and the sample in the plugins directory for a simple
example.
|
|
|
|
Changelog:
Noteworthy changes in version 1.4.20 (2015-12-20)
-------------------------------------------------
* Reject signatures made using the MD5 hash algorithm unless the
new option --allow-weak-digest-algos or --pgp2 are given.
* New option --weak-digest to specify hash algorithms which
should be considered weak.
* Changed default cipher for symmetric-only encryption to AES-128.
* Fix for DoS when importing certain garbled secret keys.
* Improved error reporting for secret subkey w/o corresponding public
subkey.
* Improved error reporting in decryption due to wrong algorithm.
* Fix cluttering of stdout with trustdb info in double verbose mode.
* Pass a DBUS envvar to gpg-agent for use by gnome-keyring.
|
|
|
|
|
|
|
|
Changelog:
Noteworthy changes in version 2.1.10 (2015-12-04)
-------------------------------------------------
* gpg: New trust models "tofu" and "tofu+pgp".
* gpg: New command --tofu-policy. New options --tofu-default-policy
and --tofu-db-format.
* gpg: New option --weak-digest to specify hash algorithms which
should be considered weak.
* gpg: Allow the use of multiple --default-key options; take the last
available key.
* gpg: New option --encrypt-to-default-key.
* gpg: New option --unwrap to only strip the encryption layer.
* gpg: New option --only-sign-text-ids to exclude photo IDs from key
signing.
* gpg: Check for ambigious or non-matching key specification in the
config file or given to --encrypt-to.
* gpg: Show the used card reader with --card-status.
* gpg: Print export statistics and an EXPORTED status line.
* gpg: Allow selecting subkeys by keyid in --edit-key.
* gpg: Allow updating the expiration time of multiple subkeys at
once.
* dirmngr: New option --use-tor. For full support this requires
libassuan version 2.4.2 and a patched version of libadns
(e.g. adns-1.4-g10-7 as used by the standard Windows installer).
* dirmngr: New option --nameserver to specify the nameserver used in
Tor mode.
* dirmngr: Keyservers may again be specified by IP address.
* dirmngr: Fixed problems in resolving keyserver pools.
* dirmngr: Fixed handling of premature termination of TLS streams so
that large numbers of keys can be refreshed via hkps.
* gpg: Fixed a regression in --locate-key [since 2.1.9].
* gpg: Fixed another bug for keyrings with legacy keys.
* gpgsm: Allow combinations of usage flags in --gen-key.
* Make tilde expansion work with most options.
* Many other cleanups and bug fixes.
|
|
Changelog:
Noteworthy changes in version 2.4.2 (2015-12-02) [C7/A7/R2]
------------------------------------------------
* The nPth version of the connect system hook does now wrap the call
with npth_unprotec/npth_protect to avoid blocking during a connect.
* Add feature to assuan_sock_connect_byname to test for SOCKS5
availability.
Noteworthy changes in version 2.4.1 (2015-11-23) [C7/A7/R1]
------------------------------------------------
* In Tor mode fallback to port 9150 if 9050 is not listening.
* Allow building with older mingw-w64 versions.
Noteworthy changes in version 2.4.0 (2015-11-03) [C7/A7/R0]
------------------------------------------------
* New flags "socks" and "tor-mode" for assuan_sock_{set,get}_flag.
* New function assuan_sock_connect_byname.
* Require at least libgpg-error 1.17.
* Interface changes relative to the 2.3.0 release:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
assuan_sock_connect_byname NEW.
ASSUAN_SOCK_TOR NEW.
ASSUAN_SOCK_SOCKS NEW.
assuan_sock_set_flag EXTENDED.
assuan_sock_get_flag EXTENDED.
Noteworthy changes in version 2.3.0 (2015-08-28) [C6/A6/R0]
------------------------------------------------
* Now wipes out the memory of the context structure before freeing.
The context may have stored sensitive data in its line buffers.
* Fixed a problem with the data length limit in assuan_inquire.
* Returns GPG_ERR_SOURCE_ASSUAN with errors from functions w/o a
context.
* Two new functions to tweak the behaviour of the socket wrappers.
* Experimental code to support Cygwin's local sockets.
* By default build without a build timestamp.
* Interface changes relative to the 2.2.1 release:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
assuan_sock_set_flag NEW.
assuan_sock_get_flag NEW.
|
|
|
|
Noteworthy changes in version 0.9.7 (2015-12-07)
------------------------------------------------
* Fix regressions in the Qt pinentry.
* Fix minor problems pinnetyr-tty.
* New option --invisible-char.
|
|
Noteworthy changes in version 1.21 (2015-12-12) [C17/A17/R0]
-----------------------------------------------
* New functions gpgrt_poll and gpgrt_set_nonblock. For now only
pipes and sockets on Unix are supported.
* Fixes gettext output encoding problems on Windows.
* Interface changes relative to the 1.20 release:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gpgrt_set_nonblock NEW.
gpgrt_get_nonblock NEW.
gpgrt_poll NEW.
gpgrt_poll_t NEW type.
es_poll_t NEW type.
es_set_nonblock NEW macro.
es_get_nonblock NEW macro.
es_poll NEW macro.
GPG_ERR_TRUE NEW.
GPG_ERR_FALSE NEW.
GPG_ERR_NO_NAME NEW.
GPG_ERR_NO_KEY NEW.
GPG_ERR_SERVER_FAILED NEW.
|
|
1.1.2 - 2015-12-10
~~~~~~~~~~~~~~~~~~
* Fixed a SIGBUS crash with the OS X wheels caused by redefinition of a
method.
* Fixed a runtime error ``undefined symbol EC_GFp_nistp224_method`` that
occurred with some OpenSSL installations.
* Updated Windows and OS X wheels to be compiled against OpenSSL 1.0.2e.
|
|
|
|
## 1.8.1
* Change license to MIT, thanks to all the patient contributors who gave
their permissions.
## 1.8.0
* add SSHKit::Backend::ConnectionPool#close_connections
[PR #285](https://github.com/capistrano/sshkit/pull/285)
@akm
* Clean up rubocop lint warnings
[PR #275](https://github.com/capistrano/sshkit/pull/275)
@cshaffer
* Prepend unused parameter names with an underscore
* Prefer “safe assignment in condition”
* Disambiguate regexp literals with parens
* Prefer `sprintf` over `String#%`
* No longer shadow `caller_line` variable in `DeprecationLogger`
* Rescue `StandardError` instead of `Exception`
* Remove useless `private` access modifier in `TestAbstract`
* Disambiguate block operator with parens
* Disambiguate between grouped expression and method params
* Remove assertion in `TestHost#test_assert_hosts_compare_equal` that compares something with itself
* Export environment variables and execute command in a subshell.
[PR #273](https://github.com/capistrano/sshkit/pull/273)
@kuon
* Introduce `log_command_start`, `log_command_data`, `log_command_exit` methods on `Formatter`
[PR #257](https://github.com/capistrano/sshkit/pull/257)
@robd
* Deprecate `@stdout` and `@stderr` accessors on `Command`
* Add support for deprecation logging options.
[README](README.md#deprecation-warnings),
[PR #258](https://github.com/capistrano/sshkit/pull/258)
@robd
* Quote environment variable values.
[PR #250](https://github.com/capistrano/sshkit/pull/250)
@Sinjo - Chris Sinjakli
* Simplified formatter hierarchy.
[PR #248](https://github.com/capistrano/sshkit/pull/248)
@robd
* `SimpleText` formatter now extends `Pretty`, rather than duplicating.
* Hide ANSI color escape sequences when outputting to a file.
[README](README.md#output-colors),
[Issue #245](https://github.com/capistrano/sshkit/issues/245),
[PR #246](https://github.com/capistrano/sshkit/pull/246)
@robd
* Now only color the output if it is associated with a tty,
or the `SSHKIT_COLOR` environment variable is set.
* Removed broken support for assigning an `IO` to the `output` config option.
[Issue #243](https://github.com/capistrano/sshkit/issues/243),
[PR #244](https://github.com/capistrano/sshkit/pull/244)
@robd
* Use `SSHKit.config.output = SSHKit::Formatter::SimpleText.new($stdin)` instead
* Added support for `:interaction_handler` option on commands.
[PR #234](https://github.com/capistrano/sshkit/pull/234),
[PR #242](https://github.com/capistrano/sshkit/pull/242)
@robd
* Removed partially supported `TRACE` log level.
[2aa7890](https://github.com/capistrano/sshkit/commit/2aa78905f0c521ad9f697e7a4ed04ba438d5ee78)
@robd
* Add support for the `:strip` option to the `capture` method and strip by default on the `Local` backend.
[PR #239](https://github.com/capistrano/sshkit/pull/239),
[PR #249](https://github.com/capistrano/sshkit/pull/249)
@robd
* The `Local` backend now strips by default to be consistent with the `Netssh` one.
* This reverses change [7d15a9a](https://github.com/capistrano/sshkit/commit/7d15a9aebfcc43807c8151bf6f3a4bc038ce6218) to the `Local` capture API to remove stripping by default.
* If you require the raw, unstripped output, pass the `strip: false` option: `capture(:ls, strip: false)`
* Simplified backend hierarchy.
[PR #235](https://github.com/capistrano/sshkit/pull/235),
[PR #237](https://github.com/capistrano/sshkit/pull/237)
@robd
* Moved duplicate implementations of `make`, `rake`, `test`, `capture`, `background` on to `Abstract` backend.
* Backend implementations now only need to implement `execute_command`, `upload!` and `download!`
* Removed `Printer` from backend hierarchy for `Local` and `Netssh` backends (they now just extend `Abstract`)
* Removed unused `Net::SSH:LogLevelShim`
* Removed dependency on the `colorize` gem. SSHKit now implements its own ANSI color logic, with no external dependencies. Note that SSHKit now only supports the `:bold` or plain modes. Other modes will be gracefully ignored. [#263](https://github.com/capistrano/sshkit/issues/263)
* New API for setting the formatter: `use_format`. This differs from `format=` in that it accepts options or arguments that will be passed to the formatter's constructor. The `format=` syntax will be deprecated in a future release. [#295](https://github.com/capistrano/sshkit/issues/295)
* SSHKit now immediately raises a `NameError` if you try to set a formatter that does not exist. [#295](https://github.com/capistrano/sshkit/issues/295)
|
|
## 1.8.1
* Change license to MIT, thanks to all the patient contributors who gave
their permissions.
## 1.8.0
* add SSHKit::Backend::ConnectionPool#close_connections
[PR #285](https://github.com/capistrano/sshkit/pull/285)
@akm
* Clean up rubocop lint warnings
[PR #275](https://github.com/capistrano/sshkit/pull/275)
@cshaffer
* Prepend unused parameter names with an underscore
* Prefer “safe assignment in condition”
* Disambiguate regexp literals with parens
* Prefer `sprintf` over `String#%`
* No longer shadow `caller_line` variable in `DeprecationLogger`
* Rescue `StandardError` instead of `Exception`
* Remove useless `private` access modifier in `TestAbstract`
* Disambiguate block operator with parens
* Disambiguate between grouped expression and method params
* Remove assertion in `TestHost#test_assert_hosts_compare_equal` that compares something with itself
* Export environment variables and execute command in a subshell.
[PR #273](https://github.com/capistrano/sshkit/pull/273)
@kuon
* Introduce `log_command_start`, `log_command_data`, `log_command_exit` methods on `Formatter`
[PR #257](https://github.com/capistrano/sshkit/pull/257)
@robd
* Deprecate `@stdout` and `@stderr` accessors on `Command`
* Add support for deprecation logging options.
[README](README.md#deprecation-warnings),
[PR #258](https://github.com/capistrano/sshkit/pull/258)
@robd
* Quote environment variable values.
[PR #250](https://github.com/capistrano/sshkit/pull/250)
@Sinjo - Chris Sinjakli
* Simplified formatter hierarchy.
[PR #248](https://github.com/capistrano/sshkit/pull/248)
@robd
* `SimpleText` formatter now extends `Pretty`, rather than duplicating.
* Hide ANSI color escape sequences when outputting to a file.
[README](README.md#output-colors),
[Issue #245](https://github.com/capistrano/sshkit/issues/245),
[PR #246](https://github.com/capistrano/sshkit/pull/246)
@robd
* Now only color the output if it is associated with a tty,
or the `SSHKIT_COLOR` environment variable is set.
* Removed broken support for assigning an `IO` to the `output` config option.
[Issue #243](https://github.com/capistrano/sshkit/issues/243),
[PR #244](https://github.com/capistrano/sshkit/pull/244)
@robd
* Use `SSHKit.config.output = SSHKit::Formatter::SimpleText.new($stdin)` instead
* Added support for `:interaction_handler` option on commands.
[PR #234](https://github.com/capistrano/sshkit/pull/234),
[PR #242](https://github.com/capistrano/sshkit/pull/242)
@robd
* Removed partially supported `TRACE` log level.
[2aa7890](https://github.com/capistrano/sshkit/commit/2aa78905f0c521ad9f697e7a4ed04ba438d5ee78)
@robd
* Add support for the `:strip` option to the `capture` method and strip by default on the `Local` backend.
[PR #239](https://github.com/capistrano/sshkit/pull/239),
[PR #249](https://github.com/capistrano/sshkit/pull/249)
@robd
* The `Local` backend now strips by default to be consistent with the `Netssh` one.
* This reverses change [7d15a9a](https://github.com/capistrano/sshkit/commit/7d15a9aebfcc43807c8151bf6f3a4bc038ce6218) to the `Local` capture API to remove stripping by default.
* If you require the raw, unstripped output, pass the `strip: false` option: `capture(:ls, strip: false)`
* Simplified backend hierarchy.
[PR #235](https://github.com/capistrano/sshkit/pull/235),
[PR #237](https://github.com/capistrano/sshkit/pull/237)
@robd
* Moved duplicate implementations of `make`, `rake`, `test`, `capture`, `background` on to `Abstract` backend.
* Backend implementations now only need to implement `execute_command`, `upload!` and `download!`
* Removed `Printer` from backend hierarchy for `Local` and `Netssh` backends (they now just extend `Abstract`)
* Removed unused `Net::SSH:LogLevelShim`
* Removed dependency on the `colorize` gem. SSHKit now implements its own ANSI color logic, with no external dependencies. Note that SSHKit now only supports the `:bold` or plain modes. Other modes will be gracefully ignored. [#263](https://github.com/capistrano/sshkit/issues/263)
* New API for setting the formatter: `use_format`. This differs from `format=` in that it accepts options or arguments that will be passed to the formatter's constructor. The `format=` syntax will be deprecated in a future release. [#295](https://github.com/capistrano/sshkit/issues/295)
* SSHKit now immediately raises a `NameError` if you try to set a formatter that does not exist. [#295](https://github.com/capistrano/sshkit/issues/295)
|
|
2.022 2015/12/10
- fix stringification of IPv6 inside subjectAltNames in Utils::CERT_asHash.
Thanks to Mark.Martinec[AT]ijs[DOT]si for reporting in #110253
|
|
Perl Compatible Regular Expressions, revamped on-access scanning
for Linux, and other new features join the many great features of ClamAV:
- Processing of YARA rules(some limitations- see signatures.pdf).
- Support in ClamAV logical signatures for many of the features
added for YARA, such as Perl Compatible Regular Expressions,
alternate strings, and YARA string attributes. See signatures.pdf
for full details.
- New and improved on-access scanning for Linux. See the recent blog
post and clamdoc.pdf for details on the new on-access capabilities.
- A new ClamAV API callback function that is invoked when a virus
is found. This is intended primarily for applications running in
all-match mode. Any applications using all-match mode must use
the new callback function to record and report detected viruses.
- Configurable default password list to attempt zip file decryption.
- TIFF file support.
- Upgrade Windows pthread library to 2.9.1.
- A new signature target type for designating signatures to run
against files with unknown file types.
- Improved fidelity of the "data loss prevention" heuristic
algorithm. Code supplied by Bill Parker.
- Support for LZMA decompression within Adobe Flash files.
- Support for MSO attachments within Microsoft Office 2003 XML files.
- A new sigtool option(--ascii-normalize) allowing signature authors
to more easily generate normalized versions of ascii files.
- Windows installation directories changed from \Program Files\Sourcefire\
ClamAV to \Program Files\ClamAV or \Program Files\ClamAV-x64.
|
|
|
|
KeePassX 2.0 is using the new .kdbx (same as KeePass 2) database
format. You can import your .kdb database from 0.4 from the Database
> Import KeePass 1 database. This is a one-way process though.
You cant migrate back to the .kdb format.
New features include:
Multiple attachments per entry
Add custom key/value pairs to entries
Open multiple database in one window
KeePassX 2.0 has been rewritten from scratch so some features (like
showing expired passwords) are still missing.
|
|
new major version.
KeePass is a free/open-source password manager or safe which helps you to
manage your passwords in a secure way. You can put all your passwords in one
database, which is locked with one master key or a key-disk. So you only have
to remember one single master password or insert the key-disk to unlock the
whole database. The databases are encrypted using the best and most secure
encryption algorithms currently known (AES and Twofish).
This package contains v0.4.x of the program with KeePass v1 database
format (kdb) support.
|
|
2015-Feb-08 v2.8 - Fixed cli_copy bug; refresh paths and ask to save.
Fixed a cli_mv bug; double path-normalization.
Fixed a path display bug, if done after a cli_mv.
Protect users from editing in the $FOUND_DIR.
Keep file opened, read-only, to show up in lsof.
Added inactivity locking (--timeout parameter).
Added shell expansion support to cli_ls, with the
ability to manage _all_ listed entries by number.
Added shell expansion support to cli_mv.
Added [y/N] option to list entries after a find.
2015-Jun-19 v3.0 - Added Password Safe v3 file importing; requires
optional Crypt::PWSafe3 from CPAN.
Added $FORCED_READLINE global variable.
Attachments sanity check; SourceForge bug #17.
Endianness fix in magic_file_type(); SF bug #19.
|
|
|
|
All tests pass.
Crypt::PWSafe3 provides read and write access to password database
files created by Password Safe V3 (and up).
|
|
|
|
due to the default being set later in the environment.
|
|
|
|
Non-Windows CVE mentioned below was already fixed in pkgsrc.
Changes:
Two security flaws have been discovered in KeePassX 0.4.3.
Version 2.0 has a different codebase and is not affected.
* CVE-2015-8359: DLL Preloading vulnerability on Windows
The version of Qt bundled with KeePassX 0.4.3 is vulnerable to
a DDL preloading attack. This vulnerability only affects
KeePassX on Windows. If successfully exploited, arbitrary code
can be executed in the context of KeePassX. KeePassX 0.4.4
ships with Qt 4.8.7 and employs additional hardening measures.
Thanks to Trenton Ivey from SecureWorks for reporting this
vulnerability to us.
* CVE-2015-8378: Canceling XML export function creates export as ".xml"file
When canceling the "Export to > KeePassX XML file" function
the cleartext passwords were still exported. In this case the
password database was exported as the file ".xml" in the current
working directory (often $HOME or the directory of the database).
Originally reported as Debian bug #791858
KeePassX 0.4.4 fixes both vulnerabilities.
|
|
|
|
bootstrap-mk-files). OpenSSL specifically checks for CC=gcc before using it as
a makedepend replacement, whereas CC=cc will fall back to requiring a real
'makedepend' which may not be installed. Tested on Linux by kamil@
|
|
pkgsrc changes:
- We now need to run 'make depend' after configure to pick up algorithm
selection changes.
Upstream changes:
Changes between 1.0.2d and 1.0.2e [3 Dec 2015]
*) BN_mod_exp may produce incorrect results on x86_64
There is a carry propagating bug in the x86_64 Montgomery squaring
procedure. No EC algorithms are affected. Analysis suggests that attacks
against RSA and DSA as a result of this defect would be very difficult to
perform and are not believed likely. Attacks against DH are considered just
feasible (although very difficult) because most of the work necessary to
deduce information about a private key may be performed offline. The amount
of resources required for such an attack would be very significant and
likely only accessible to a limited number of attackers. An attacker would
additionally need online access to an unpatched system using the target
private key in a scenario with persistent DH parameters and a private
key that is shared between multiple clients. For example this can occur by
default in OpenSSL DHE based SSL/TLS ciphersuites.
This issue was reported to OpenSSL by Hanno Böck.
(CVE-2015-3193)
[Andy Polyakov]
*) Certificate verify crash with missing PSS parameter
The signature verification routines will crash with a NULL pointer
dereference if presented with an ASN.1 signature using the RSA PSS
algorithm and absent mask generation function parameter. Since these
routines are used to verify certificate signature algorithms this can be
used to crash any certificate verification operation and exploited in a
DoS attack. Any application which performs certificate verification is
vulnerable including OpenSSL clients and servers which enable client
authentication.
This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG).
(CVE-2015-3194)
[Stephen Henson]
*) X509_ATTRIBUTE memory leak
When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
memory. This structure is used by the PKCS#7 and CMS routines so any
application which reads PKCS#7 or CMS data from untrusted sources is
affected. SSL/TLS is not affected.
This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
libFuzzer.
(CVE-2015-3195)
[Stephen Henson]
*) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
This changes the decoding behaviour for some invalid messages,
though the change is mostly in the more lenient direction, and
legacy behaviour is preserved as much as possible.
[Emilia Käsper]
*) In DSA_generate_parameters_ex, if the provided seed is too short,
return an error
[Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
|
|
Bump PKGREVISION.
While here, clean up pkglint.
|
|
use php-mysql package.
|
|
2.021 2015/12/02
- Fixes for documentation and typos thanks to DavsX and jwilk.
- Update PublicSuffx with latest version from publicsuffix.org
|
|
|
|
|
|
A HTTPS client implementation for httplib and urllib2 based on
PyOpenSSL. PyOpenSSL provides a more fully featured SSL
implementation over the default provided with Python and
importantly enables full verification of the SSL peer.
|
|
Some of the upstream changes for 0.9.2 :
- various typo in config files
- filter.d/postfix-sasl.conf - tweak failregex and add ignoreregex to
ignore system authentication issues
- some fixes for EL7
New features :
- New filters:
- postfix-rbl
- apache-fakegooglebot.conf
- nginx-botsearch
- drupal-auth
- New actions:
- action.d/firewallcmd-multiport and action.d/firewallcmd-allports
- action.d/sendmail-geoip-lines.conf
- action.d/nsupdate to update DNSBL
- New status argument for fail2ban-client
Some of the upstream changes for 0.9.3 :
- IMPORTANT incompatible changes:
* filter.d/roundcube-auth.conf
- Changed logpath to 'errors' log (was 'userlogins')
* action.d/iptables-common.conf
- All calls to iptables command now use -w switch introduced in
iptables 1.4.20 (some distribution could have patched their
earlier base version as well) to provide this locking mechanism
useful under heavy load to avoid contesting on iptables calls.
If you need to disable, define 'action.d/iptables-common.local'
with empty value for 'lockingopt' in `[Init]` section.
* mail-whois-lines, sendmail-geoip-lines and sendmail-whois-lines
actions now include by default only the first 1000 log lines in
the emails. Adjust <grepopts> to augment the behavior.
- New Features:
* New filters:
- froxlor-auth - Thanks Joern Muehlencord
- apache-pass - filter Apache access log for successful authentication
* New actions:
- shorewall-ipset-proto6 - using proto feature of the Shorewall.
Still requires manual pre-configuration of the shorewall.
See the action file for detail.
* New jails:
- pass2allow-ftp - allows FTP traffic after successful
HTTP authentication
|
|
The find-prefix infrastructure was required in a pkgviews world where
packages installed from pkgsrc could have different installation
prefixes, and this was a way for a dependency prefix to be determined.
Now that pkgviews has been removed there is no longer any need for the
overhead of this infrastructure. Instead we use BUILDLINK_PREFIX.pkg
for dependencies pulled in via buildlink, or LOCALBASE/PREFIX where the
dependency is coming from pkgsrc.
Provides a reasonable performance win due to the reduction of `pkg_info
-qp` calls, some of which were redundant anyway as they were duplicating
the same information provided by BUILDLINK_PREFIX.pkg.
|
|
[2015/10/06]
* Version 2.5.0
- fixes for compiling for rubinius, at long last
- TESTS
- add a few method aliases
|
|
1.1.1 - 2015-11-19
~~~~~~~~~~~~~~~~~~
* Fixed several small bugs related to compiling the OpenSSL bindings with
unusual OpenSSL configurations.
* Resolved an issue where, depending on the method of installation and
which Python interpreter they were using, users on El Capitan (OS X 10.11)
may have seen an ``InternalError`` on import.
|
|
Provided by csosstudy in PR 50455.
Version 1.0.6
Optimized implementations of Blake2 have been added for modern Intel platforms. crypto_generichash() is now faster than MD5 and SHA1 implementations while being far more secure.
Functions for which the return value should be checked have been tagged with __attribute__ ((warn_unused_result)). This will intentionally break code compiled with -Werror that didn't bother checking critical return values.
The crypto_sign_edwards25519sha512batch_*() functions have been tagged as deprecated.
Undocumented symbols that were exported, but were only useful for internal purposes have been removed or made private: sodium_runtime_get_cpu_features(), the implementation-specific crypto_onetimeauth_poly1305_donna() symbols, crypto_onetimeauth_poly1305_set_implementation(), crypto_onetimeauth_poly1305_implementation_name() and crypto_onetimeauth_pick_best_implementation().
sodium_compare() now works as documented, and compares numbers in little-endian format instead of behaving like memcmp().
The previous changes should not break actual applications, but to be safe, the library version major was incremented.
sodium_runtime_has_ssse3() and sodium_runtime_has_sse41() have been added.
The library can now be compiled with the CompCert compiler.
Version 1.0.5
This release only fixes compilation issues on some platforms.
If 1.0.4 compiled and installed fine on your system, upgrading to this version is not required.
There are no functional changes.
Compilation issues on some platforms were fixed: missing alignment directives were added (required at least on RHEL-6/i386), a workaround for a VRP bug on gcc/armv7 was added, and the library can now be compiled with the SunPro compiler.
Javascript target: io.js is not supported any more. Use nodejs.
Version 1.0.4
Support for AES256-GCM has been added. This requires a CPU with the aesni and pclmul extensions, and is accessible via the crypto_aead_aes256gcm_*() functions.
The Javascript target doesn't use eval() any more, so that the library can be used in Chrome packaged applications.
QNX and CloudABI are now supported.
Support for NaCl has finally been added.
ChaCha20 with an extended (96 bit) nonce and a 32-bit counter has been implemented as crypto_stream_chacha20_ietf(), crypto_stream_chacha20_ietf_xor() and crypto_stream_chacha20_ietf_xor_ic(). An IETF-compatible version of ChaCha20Poly1305 is available as crypto_aead_chacha20poly1305_ietf_npubbytes(), crypto_aead_chacha20poly1305_ietf_encrypt() and crypto_aead_chacha20poly1305_ietf_decrypt().
The sodium_increment() helper function has been added, to increment an arbitrary large number (such as a nonce).
The sodium_compare() helper function has been added, to compare arbitrary large numbers (such as nonces, in order to prevent replay attacks).
Version 1.0.3
In addition to sodium_bin2hex(), sodium_hex2bin() is now a constant-time function.
crypto_stream_xsalsa20_ic() has been added.
crypto_generichash_statebytes(), crypto_auth_*_statebytes() and crypto_hash_*_statebytes() have been added in order to retrieve the size of structures keeping states from foreign languages.
The JavaScript target doesn't require /dev/urandom or an external randombytes() implementation any more. Other minor Emscripten-related improvements have been made in order to support libsodium.js
Custom randombytes implementations do not need to provide their own implementation of randombytes_uniform() any more. randombytes_stir() and randombytes_close() can also be NULL pointers if they are not required.
On Linux, getrandom(2) is being used instead of directly accessing /dev/urandom, if the kernel supports this system call.
crypto_box_seal() and crypto_box_seal_open() have been added.
A solutions for Visual Studio 2015 was added.
|
|
Changelog:
2015-11-07 PuTTY 0.66 released, fixing a SECURITY HOLE
PuTTY 0.66, released today, fixes a security hole in 0.65 and before:
vuln-ech-overflow. It also contains a few other small bug fixes and minor
features.
|
|
|
|
|
|
|
|
|
|
|
|
From upstream via Petar Bogdanovic on pkgsrc-users.
Bump PKGREVISION.
|
