SILC Toolkit 0.9.12
Pekka Riikonen <[email protected]> Sun, 29 Feb 2004 15:20:49 +0100 (CET)
| Newsgroups | gmane.network.silc.announce |
|---|---|
| Message-ID | <[email protected]> |
The new version of the SILC Toolkit is now available! The source package
of the software is available from the following sources:
http://silcnet.org/
ftp://ftp.silcnet.org/
The SILC Toolkit 0.9.12 is out. A long time has passed since the last
Toolkit. In this version you will find quite a lot new features, some
slight API changes and a lot of bugfixes. If you are doing application
with the SILC Toolkit I suggest reading the summary of changes as it will
list all changes, and helps you to notice what changes you need to make
into your application.
Summary of Changes
------------------
o Added the user's public key to SilcClientEntry.
Ref:
http://silcnet.org/docs/toolkit/silcclient-SilcClientEntry.html
o The channel topic has been added to SilcChannelEntry. Added also
the channel founder's public key to SilcChannelEntry. Added also
the channel user limit to SilcChannelEntry.
Ref:
http://silcnet.org/docs/toolkit/silcclient-SilcChannelEntry.html
o The user limit on channel is now delivered in the JOIN command reply
and CMODE command reply.
o Added support for watching users by their public key in the WATCH
comand in client library. Can be called via silc_client_command_call.
o Added support for using channel private keys in Client Library even
if the private key mode is not set on the channel. Application can
set private keys and use them regardless of the mode on the channel.
The silc_client_add_channel_private_key now also returns the key
pointer to application. Programmers must update their code because
of this interface change.
Ref:
http://silcnet.org/docs/toolkit/silcclient-silc_client_add_channel_private_key.html
o The channel private key used to decrypt the message is now delivered
to the 'channel_message' client operation. Programmers must update
their code because of this interface change. Application is able to
see which private key was used to decrypt the incoming message.
If private key was not used it is set to NULL.
Ref:
http://silcnet.org/docs/toolkit/silcclient-SilcClientOperations.html
o Added support to the new private message key request indicator packet.
Added silc_client_send_private_message_key_request function.
Application may use it to indicate remote user that static private
key (not Key Agreement) should be used. The receiver of the packet
understands that it is the responder side of the key. Added
'prv_resp' boolean to the SilcClientEntry. If it is TRUE application
knows that user is responder and must set the 'responder' argument
to TRUE in silc_client_add_private_message. The sender of that
packet must set it to FALSE. This way it is possible to set the
initiator/responder status in the keys without asking it from
end user.
Ref:
http://silcnet.org/docs/toolkit/silcclient-silc_client_send_private_message_key_request.html
http://silcnet.org/docs/toolkit/silcclient-SilcClientEntry.html
http://silcnet.org/docs/toolkit/silcclient-silc_client_add_private_message_key.html
o Added silc_client_get_clients_whois function. It is same as the
silc_client_get_clients except resolves information with WHOIS. It
also supports requested attributes.
Ref:
http://silcnet.org/docs/toolkit/silcclient-silc_client_get_clients.html
o Added new connection status errors. Added SILC_CLIENT_CONN_ERROR_KE,
SILC_CLIENT_CONN_ERROR_AUTH, SILC_CLIENT_CONN_ERROR_RESUME and
SILC_CLIENT_CONN_ERROR_TIMEOUT. These are delivered to the 'connected'
client operation. Application should handle all errors.
Ref:
http://silcnet.org/docs/toolkit/silcclient-SilcClientConnectionStatus.html
http://silcnet.org/docs/toolkit/silcclient-SilcClientOperations.html
o Added SilcClientFileAskName callback to the silc_client_file_receive
function. If it is provided the library will call it and application
can define there to which file the received data should be saved.
Programmers must update their code because of this interface change.
Ref:
http://silcnet.org/docs/toolkit/silcclient-SilcClientFileAskName.html
http://silcnet.org/docs/toolkit/silcclient-silc_client_file_receive.html
o When application calls the silc_client_file_close to close or cancel
the file transfer the monitor callback, if it is defined, is now
called with the status SILC_CLIENT_FILE_MONITOR_CLOSED. Application
need to handle it. It is guaranteed it is the last time the monitor
callback is called after that status is received in the monitor
callback.
Ref:
http://silcnet.org/docs/toolkit/silcclient-SilcClientMonitorStatus.html
http://silcnet.org/docs/toolkit/silcclient-SilcClientFileMonitor.html
http://silcnet.org/docs/toolkit/silcclient-silc_client_file_close.html
o Added SILC_STRFMT_END. Use that instead of SILC_STR_END with the
silc_buffer_strformat function.
Ref:
http://silcnet.org/docs/toolkit/silcbuffmt-SILC_STRFMT_END.html
http://silcnet.org/docs/toolkit/silcbuffmt-silc_buffer_strformat.html
o Added SILC_32_TO_PTR, SILC_PTR_TO_32, SILC_64_TO_PTR and
SILC_PTR_TO_64 macros. Use these when you are type casting integers
to pointers and vice versa, to avoid compiler warnings on 64-bit
systems.
o The SILC_LOG_* macros can now be safely used in if-statement, and
others, without braces.
o Resuming data handling error was fixed.
o Several other minor bugfixes were made.
The full list of changes is available on the website and in CHANGES file
in the source package.
Installation
------------
The source package is compiled and installed as instructed in the INSTALL
file found from the package. Refer also to the building instructions in
the Toolkit Reference Manual:
http://silcnet.org/docs/toolkit/building.html
Quick installation:
./configure
make
make install
Known Issues
------------
- Known platform specific issues
- silc_net_create_connection_async is not actually asynchronous on
Win32. It works synchronously and blocks the process.
_________________________________________________________
Info: http://lists.silcnet.org/listinfo/silc-announce
Archive: http://lists.silcnet.org/pipermail/silc-announce
FAQ: http://silcnet.org/?page=faq