The changes to the code include:
* A '-f' flag to destry with force any type of file that isn't a Regular
File or a Directory.
* Bug fixes.
* Code Clean-up.
under IRIX. Other OS regen the catman page.
This addresses PR pkg/23452.
Since just depending on textproc/groff would pull in a large number of
packages (such as perl, ghostscript, tiff etc.), and since this is a very
important package that should NOT depend on all this gunk, Jeremy C. Reed
suggested this solution.
Ok agc.
This is to make sure that libexec/gnupg/gpgkeys_mailto is
installed. (Okay'd by wiz.)
This assumes that /usr/sbin/sendmail is sendmail.
PKGREVISION is not bumped because package couldn't be made
in first place if libexec/gnupg/gpgkeys_mailto was missing.
private mail, ok'd by lukem. Changes:
> Use the URL node and {head,tail}URL edge-attribute and link
> to "Web of trust statistics and pathfinder"-Site.
>
> This site provides a statistical analysis of the key (linked behind
> each node) and a path between to keys (linked behind tail and
> head of a edge).
>
> Those URL statements take only affect if one generates IMAP or CMAP
> output and uses this on a HTML-Site as imagemap.
gnome-keyring is a program that keeps passwords and other secrets for
users. It is run as a damon in the session, similar to ssh-agent, and
other applications can locate it by an environment variable.
The program can manage several keyrings, each with its own master
password, and there is also a session keyring which is never stored to
disk, but forgotten when the session ends.
The library libgnome-keyring is used by applications to integrate with
the gnome keyring system. However, at this point the library hasn't
been tested and used enough to consider the API to be publically exposed.
Therefore use of libgnome-keyring is at the moment limited to internal
use in the gnome desktop. However, we hope that the gnome-keyring API
will turn out useful and good, so that later it can be made public for
any application to use.
* Support for AES in GSSAPI has been implemented. This corresponds to the
in-progress work in the IETF (CFX).
* To avoid compatibility problems, unrecognized TGS options will now be
ignored.
* 128-bit AES has been added to the default enctypes.
* AES cryptosystem now chains IVs. This WILL break backwards compatibility
for the kcmd applications, if they are using AES session keys.
* Assorted minor bug fixes and plugged memory leaks.
on the wip/mit-krb5 package by Jeremy Reed, but heavily modified by me to
libtoolize the build.
Kerberos V5 is an authentication system developed at MIT. It is a network
authentication protocol designed to provide strong authentication for
client/server applications by using secret-key cryptography. (Kerberos
5 is discussed in RFC 1510.)
This package provides Kerberos and GSSAPI (Generic Security Services
Application Programming Interface) development headers and libraries.
It also includes Kerberos ticket and principal tools, and Kerberized
r-services, telnet and ftp services.
bug gnupg/293, so grant has blessed it for inclusion in pkgsrc.
No more GNU sed build dependency, but the binaries do not change; thus
PKGREVISION untouched.
hashcash-0.30 - 04-Mar-2004 - Adam Back <adam@cypherspace.org>
* make -cX check multiple X-Hashcash lines until it finds the
right one. Bug reported by Kyle Hasselbacher <kyle@toehold.com>.
hashcash-0.29 - 04-Mar-2004 - Adam Back <adam@cypherspace.org>
* fix prototype mismatch of function hashcash_check in
hashcash.h vs libhc.c which caused compile failure on
openBSD and freeBSD
* change to make it compile on MAC OSX (need to recognize OSX
and treat as unix like for headers to include)
* change to make it compile on solaris 9 (and POSIX / SVR
systems in general). Turns out putenv(3) is more portable
than setenv(3) / unsetenv(3)
* update sha1 man page to name it sha1-hashcash to avoid collision
with openssl sha1(1). By default with openssl there is not
actually any program named sha1, rather sha1 is a subprogram of
openssl invoked "openssl sha1". However I think it may still be
possible to compile that as a separate program or symlink sha1 to
openssl to get that.
* update sha1 man pages to refer to the other common sha1
implementations.
* update LICENSE request
