Hej.

Det virker som om, der er opst�et et lille problem. Med mail listen!

Den kommunikation der foreg�r lige nu, burde v�re i et forum og ikke sendes
til alle p� maillisten. Det begynder at antage form som spam (jeg har
omkring 30 mails fra kbhkol, i dag). S� vi b�r nok overveje at �ndre m�den
vi g�r det her p�.

Hilsen

Anders Feerup
(indk�bsgruppen)

-----Oprindelig meddelelse-----
Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]P� vegne af
Espen J�rgensen
Sendt: 27. november 2002 13:40
Til: [EMAIL PROTECTED]
Emne: Re: [Kbhkol] hvordan laver i andre authentication


> > Mon ikke sshd kan s�ttes til at kappe d�de forbindelser efter fx 5 min
> (sshd_config: ClientAliveInterval)
>
> Jo, m�ske, men er den d�d forbindelse en der ikke bliver brugt ?
>

Fra man-pagen (man sshd_config):

ClientAliveInterval
             Sets a timeout interval in seconds after which if no data has
             been received from the client, sshd will send a message through
             the encrypted channel to request a response from the client.
The
             default is 0, indicating that these messages will not be sent
to
             the client.  This option applies to protocol version 2 only.

ClientAliveCountMax
             Sets the number of client alive messages (see above) which may
be
             sent without sshd receiving any messages back from the client.
If
             this threshold is reached while client alive messages are being
             sent, sshd will disconnect the client, terminating the session.
             It is important to note that the use of client alive messages
is
             very different from KeepAlive (below). The client alive
messages
             are sent through the encrypted channel and therefore will not
be
             spoofable. The TCP keepalive option enabled by KeepAlive is
             spoofable. The client alive mechanism is valuable when the
client
             or server depend on knowing when a connection has become inac�
             tive.

             The default value is 3. If ClientAliveInterval (above) is set
to
             15, and ClientAliveCountMax is left at the default,
unresponsive
             ssh clients will be disconnected after approximately 45
seconds.
_______________________________________________
kbhkol mailing list
[EMAIL PROTECTED]
http://kbhkol.dk/mailman/listinfo/kbhkol


_______________________________________________
kbhkol mailing list
[EMAIL PROTECTED]
http://kbhkol.dk/mailman/listinfo/kbhkol

Besvar via email