Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
LSH
lsh
Commits
0441f01c
Commit
0441f01c
authored
Jun 14, 1999
by
Niels Möller
Browse files
Removed fixed items.
Rev: doc/TODO:1.48
parent
ce6f95a6
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/TODO
View file @
0441f01c
...
...
@@ -35,9 +35,6 @@ KEYS
Code is needed to generate, store and read dss keys. Preferably in a
SPKI/s-expression form.
Fix the dss signature mess (obsolete draft format, new draft format,
format actually used by ssh2).
Fix compliance with the (next) SPKI draft. In particular, the order of
fields and the encoding of numbers needs updating.
...
...
@@ -99,8 +96,6 @@ instance, a writing to a file associated with a channel may fail. In
that case, the channel should be closed, but the connection should not
die. Handle the LSH_CHANNEL_FINISHED code properly.
Fix the flow control (it's broken on the receiving end).
CHANNEL CLOSE
...
...
@@ -179,8 +174,6 @@ crypto code.
Use UNUSED where parameters are unused intentionally.
Fix shadow passwd support.
Make it cleaner wrt. more gcc warnings.
Fix desTest.c to use proper declarations of its function pointers, and
...
...
@@ -213,8 +206,6 @@ Currently, using a shared libz.so doesn't work.
Fix the src/symmetric/desTest program. It doesn't complain if the
desCode is compiled with empty keymap.h, parity.h and rotors.h files.
Integrate tcp-forward support.
About POLLHUP:
I've found something that can either be an io.c or a linux kernel bug.
...
...
@@ -253,5 +244,3 @@ write on a connection. When the limit is exceeded, the connection
should be dropped. The problem: if a client connects and sends a lot
of packets, without ever reading anything from its socket, the server
will eventually run out of memory.
Make sure tty modes are restored on exit.
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment