Commit graph

10 commits

Author SHA1 Message Date
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
salo
6791d8d836 Add options.mk, missed in the previous commit. 2005-04-08 15:45:24 +00:00
salo
cb86771f46 Update to version 0.9.13
Changes:
- convert to options.mk

0.9.13:
=======
After a long break the SILC Toolkit 0.9.13 is out.  This version finalizes
the SILC protocol version 1.2 development by including the few last features
that was missing from previous version.  One of the major features is the
support for UTF-8 encoded nicknames, channel names, user names and host
names.  The SILC Toolkit 0.9.13 API is compatible with the previous 0.9.12
version, however, several new functions has been added, and reading the
following summary of changes is recommended:

- Added UTF-8 encoded nicknames, channel names, server names, host names,
  usernames, crypto property names and algorithm names.  All strings
  library sends to application are always UTF-8 encoded.  All strings
  application sends to library must be UTF-8 encoded.

- Added SILC Stringprep API (RFC 3454) into silcstringprep.h.  It can
  be used to prepare strings into the correct format.  The format is
  specified by the SILC protocol, and those formats are supported by
  this API.

  The API can also be used to do other UTF-8 string preparation, such
  as case folding.  See the API for different features supported by
  the API.

- Added silc_identifier_check and silc_identifier_verify routines to
  help application easily format and verify the new UTF-8 encoded
  nicknames, channel names and other identifier strings.

  Ref:
  http://silcnet.org/docs/toolkit/silcstrutil-silc_identifier_check.html
  http://silcnet.org/docs/toolkit/silcstrutil-silc_identifier_verify.html

- Added SILC_STRING_LOCALE that now deprecates SILC_STRING_LANGUAGE.
  The old type is supported but may be removed in later versions.

  Ref:
  http://silcnet.org/docs/toolkit/silcstrutil-SilcStringEncoding.html

- Added new string encoding/decoding types: SILC_STRING_LOCALE,
  SILC_STRING_UTF8, SILC_STRING_PRINTABLE, SILC_STRING_VISIBLE,
  SILC_STRING_TELETEX, SILC_STRING_NUMERICAL, SILC_STRING_LDAP_DN and
  SILC_STRING_UTF8_ESCAPE.  These types can currently be used with
  the SILC UTF-8 API.

  Ref:
  http://silcnet.org/docs/toolkit/silcstrutil-SilcStringEncoding.html

- Splitted UTF-8 string routines from silcstrutil.h into own file
  silcutf8.h.

- Added silc_utf8_strcasecmp and silc_utf8_strncasecmp to do caseless
  UTF-8 string comparison.

  Ref:
  http://silcnet.org/docs/toolkit/silcutf8.html

- Added dont_register_crypto_library into SilcClientParams.  If set
  to TRUE the Client Library will not register/unregister cyprto library,
  and application is expected to do it.  By default this is set to FALSE.

  Ref:
  http://silcnet.org/docs/toolkit/silcclient-SilcClientParams.html

- All created log files by SILC Log API are now with 0600 mode.

  Ref:
  http://silcnet.org/docs/toolkit/silclog.html

- The bool type on Mac OS X is now _Bool.

  Ref:
  http://silcnet.org/docs/toolkit/silctypes-bool.html

- The silc_net_create_connection[_async] now revert to IPv4 address if
  IPv6 sockets are not supported.

- Added __SILC_XXX defines into silcincludes.h that third-party
  applications can check to determine how a binary version of the SILC
  Toolkit has been compiled.  The following defines may be set:

  __SILC_HAVE_PTHREAD           Compiled with threads support
  __SILC_HAVE_SIM               Compiled with SIM support
  __SILC_ENABLE_DEBUG           Compiled with debug enabled

  A third-party application can check these defines in configure.ac or
  in compile time to determine what libraries should be linked against
  the application.

- Install pkg-config .pc files for the SILC Core library and SILC Client
  library.  silc.pc and silcclient.pc will be installed.

- Several other minor bugfixes were made.
2005-04-08 15:15:17 +00:00
agc
4a3d2f7ce2 Add RMD160 digests. 2005-02-23 22:24:08 +00:00
grant
ca1dbb484e comment which file causes the ICE. 2004-12-18 18:13:53 +00:00
grant
2789a12d62 silc-toolkit causes xlc to bomb with an ICE, so mark this pkg
NOT_FOR_COMPILER=xlc.
2004-12-18 18:11:10 +00:00
tv
c487cb967a Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10
in the process.  (More information on tech-pkg.)

Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.

Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
2004-10-03 00:12:51 +00:00
jlam
1a280185e1 Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:

	lib/libfoo.a
	lib/libfoo.la
	lib/libfoo.so
	lib/libfoo.so.0
	lib/libfoo.so.0.1

one simply needs:

	lib/libfoo.la

and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.

Also make LIBTOOLIZE_PLIST default to "yes".
2004-09-22 08:09:14 +00:00
salo
1e88075dc3 Add patches from silc cvs repository.
Should fix build on Darwin/Mac OS X.
2004-06-11 10:05:06 +00:00
salo
21069efaa0 Initial import of silc-toolkit-0.9.12: Secure Internet Live Conferencing
(SILC) protocol Toolkit.

SILC (Secure Internet Live Conferencing) is a protocol which provides
secure conferencing services in the Internet over insecure channel.

SILC superficially resembles IRC, although they are very different
internally. SILC is much more than just about `encrypting the traffic'.
That is easy enough to do with IRC and SSL hybrids, but even then the
entire network cannot be secured, only part of it.

SILC provides security services, such as sending private messages entirely
secure; noone can see the message except you and the real receiver of the
message. SILC also provides same functionality for channels; noone except
those clients joined to the channel may see the messages destined to the
channel. Communication between client and server is also secured with
session keys and all commands, authentication data (such as passwords etc.)
and other traffic is entirely secured. The entire network, and all parts of
it, is secured.

SILC has secure key exchange protocol that is used to create the session keys
for each connection. SILC also provides strong authentication based on either
passwords or public key authentication. All authentication data is always
encrypted in the SILC network. Each connection has their own session keys,
all channels have channel specific keys, and all private messages can be
secured with private message specific keys.
2004-06-06 12:23:17 +00:00