unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
* [ANN] Guile-SSH 0.7.2 released
@ 2015-02-24 21:09 Artyom Poptsov
  0 siblings, 0 replies; only message in thread
From: Artyom Poptsov @ 2015-02-24 21:09 UTC (permalink / raw)
  To: Guile Users' Mailing List

[-- Attachment #1: Type: text/plain, Size: 3256 bytes --]

Hello Guilers!

I'm pleased to announce Guile-SSH 0.7.2:
  https://github.com/artyom-poptsov/guile-ssh/releases/tag/v0.7.2

Signed package can be found here:
  - ftp://memory-heap.org/software/guile-ssh/guile-ssh-0.7.2.tar.gz
  - ftp://memory-heap.org/software/guile-ssh/guile-ssh-0.7.2.tar.gz.sig

Guile-SSH is a library that provides access to the SSH protocol for GNU
Guile programs.  Guile-SSH 0.7.2 API is sufficient for building of SSH
servers and SSH clients.  In addition, it provides key management
facilities that allow to read and manipulate private and public keys,
and generate new keypairs.

This release includes bugfixes (eg. fixed double freeing of memory
during GC'ing of keys in some cases) and adds some new procedures to
(ssh server) and (ssh channel) API.  Full list of user-visible changes
is shown below.  The release does not change the existing API so
applications that use Guile-SSH 0.7.1 API should work flawlessly with
0.7.2.

Please *note* that Guile-SSH fails if libssh 0.6.3 is compiled with
GCrypt cryptographic library instead of OpenSSL.  There is a patch [1]
that fixes the issue.  The patch was included in libssh 0.6.4 -- please
use this version if you can.

Here's an excerpt from the NEWS file:

--8<---------------cut here---------------start------------->8---
* Changes in version 0.7.2 (2015-02-24)
** Remove dependency on libgcrypt added by a mistake
** Fix "double free or corruption" error on GC'ing of keys
   Fix "double free or corruption" error that occures in case when a key was
   derived from an authentication message by means of `message-get-req'.  When
   such a key is GC'ed then GC'ing of its parent message leads to error, or
   vice versa.
** Fix a bug in the channel implementation
   The bug could occasionally manifest itself on channel reading as the
   following error:
#+BEGIN_EXAMPLE
guile: ports.c:1476: scm_i_fill_input: Assertion `pt->read_pos == pt->read_end' failed.
#+END_EXAMPLE
** New `server-get' procedure in (ssh server)
   The procedure can be used to retrieve server options.
** New `channel-get-exit-status' procedure in (ssh channel)
   The procedure allows to get exit status of an executed command from a
   channel.
** New `channel-request-send-exit-status' procedure in (ssh channel)
   The procedure can be used to send the exit status to a client.
** Improve printing of Guile-SSH server objects
   Print the bind address of a server object and its bind port.  Example:
#+BEGIN_EXAMPLE
#<server 127.0.0.1:12345 9b70ff0>
#+END_EXAMPLE
** Update examples
*** sssh
    - Check exit status of an executed command.
*** ssshd
    - Send exit status to the client according to the result of command
      execution.
*** echo server and client
    - Some cosmetic changes aimed to make the code cleaner.
** Update documentation
   - Add description of the new procedures.
   - Update examples.
--8<---------------cut here---------------end--------------->8---

Thanks,

- Artyom

[1] http://git.libssh.org/projects/libssh.git/commit/?h=v0-6&id=a033b93c616f4a81afc3fc6a017396d507d96c19

-- 
Artyom V. Poptsov <poptsov.artyom@gmail.com>;  GPG Key: 0898A02F
Home page: http://poptsov-artyom.narod.ru/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-02-24 21:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-24 21:09 [ANN] Guile-SSH 0.7.2 released Artyom Poptsov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).