Revisiting two old ssh points:-
- Smart Tricks with ssh mentioned
ServerAliveInterval 3600and the page I referenced for it mentionsClientAliveIntervalon the server-side. Is there any reason not to use that? - ssh security mentioned sslh to put ssh on port 443, but it seems Top J2ME MIDP Application MidpSSH can’t connect to ssh on other ports. The instructions in the manual about port numbers don’t work for me if I put in 443. I get
java.lang.SecurityException. Anyone know why?
Turning DebianPlanet into a support tool?
(Why not using debian-user mailing list ?)
Ad 1: I don’t think so, I use both on my server and also wonder why these aren’t enabled by default. (I’d be interested in any reasoning on this, too.)
Your blog software doesn’t specify which fields are required, then produces an error page if they are not filled in, from which the only recourse is to click ‘back’ and discover that the contents of the comment box have been mysteriously eaten.
Short recap: turning on keepalives in situations of discontinuous network connectivity causes TCP sessions to terminate when they otherwise might have remained open until the connection is resumed, if only you had not tried to send data down them.
@Franklin – as you can see from the back-link, it started on planets, so it continues on planets.
@Aneurin Price – I’ll look into that required fields problem. It looks like the message which used to say which fields were required and other comments about comments has got lost in some upgrade. On the disconnects: OK, but if the client has gone dark for a few hours, it seems fair to stop wasting resources on them.
I now set a default timeout in MirBSD’s ssh and sshd of
200*3 seconds = 10 minutes, which I think is reasonable
as a generic default. (My P-233MMX server already has
been using a somewhat lower limit, but this will now be
the default for all installs of that OS.)