Commit 55fb9496 authored by Niels Möller's avatar Niels Möller

*** empty log message ***

Rev: ChangeLog:1.152
Rev: NEWS:1.40
Rev: doc/TODO:1.68
parent 9ed591cc
2000-02-02 Niels Mller <nisse@lysator.liu.se>
* configure.in: Added check for inline.
Bumped version to 0.2.7.
2000-02-02 Niels Mller <nisse@lysator.liu.se>
* src/testsuite/functions.sh, src/testsuite/lsh-1-test,
......
News for the 0.2.7 release
Bug fixes for compialtion on Solaris.
News for the 0.2.6 release
Bugfixes for tcp forwarding functions.
......
......@@ -298,3 +298,32 @@ Without this, it is impossible to use non-constant messages, for
instance messages supplied by the peer.
See if we can do without the "reason" argument to close callbacks.
Current bugs (Bazsi):
I've encountered a bug in remote (-R) forwarding in lshd. My proxy didn't
handle forwarded-tcpip channels, and refused to open such a channel. lshd
crashes if this channel cannot be opened with an unhandled exception.
* 0.2.6 doesn't remember the listening socket of an -L option as a resource,
so when the connection is closed (logout from the shell), lsh hangs on the
listening socket, and connecting to it results in a segfault (most
probably because the connection struct had been freed by the gc)
* the client side of pty allocation request should catch exceptions.
(currently only a continuation is installed, no exception handler) In my
proxy patches I made this possible adding a struct exception_handler **e to
channel_request_command's format method.
/* FIXME: The new fd object should be added to the same resource list
* as the old one. Perhaps the conenction code in io.c should reuse
* the fd object in some way? */
static void
do_connect_continue(struct fd_callback **s, int fd)
static void do_free_zstream(z_stream *z)
{
/* FIXME: Let opaque be a pointer to a struct, as it is not portable
* to cast between void * and a function pointer. */
/* Call deflateEnd() or inflateEnd(). But which? We use the opague
* pointer, as we don't use that for anything else. */
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment