05-21-2008
If you are using putty, then you can put some value (say 5) in the keepalive text box in the connection field.
Go to Change settings > connection > keepalive
9 More Discussions You Might Find Interesting
1. Cybersecurity
does any one know how to kill an idle session?
I want to kill any idle sessions after 30 min... Local or remote....
i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure.....
ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies
2. AIX
HI,
Do we have a command in AIX which will let us know when is the user id password getting expired!!
Any advice will be of great help!!
Thanks,
Siddharth (0 Replies)
Discussion started by: siddhhuu
0 Replies
3. Shell Programming and Scripting
Hi All,
I am running a ftp script which is running fine even with crontab. But the problem is that when I connect to ftp server and transfer files , i observe that ftp session expires after few minutes and the file transfer is not completed as there are alot of files to be transfered .
... (4 Replies)
Discussion started by: aarora_98
4 Replies
4. Solaris
Hi all,
Anyway to reset the passwd expiring time without user having to reset it themselve? Beside altering the maximum number of days the password is valid in the shadow file, is there any other ways?
Reason, user forgot passwd and the account passwd cannot be reset, same passwd is need for... (3 Replies)
Discussion started by: egls
3 Replies
5. UNIX for Dummies Questions & Answers
Still it is not working.
I had given 200 in putty but still it is expiring within 1 minute. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies
6. Solaris
Hi,
i need to kill the idle dt sessions through script, can anyone tell me how to do?
RJS (2 Replies)
Discussion started by: rajasekg
2 Replies
7. UNIX for Dummies Questions & Answers
Which files store the information about user with non expiring password in case of HP-UNIX like /etc/shadow in linux
Two threads by Anu_1 merged (3 Replies)
Discussion started by: Anu_1
3 Replies
8. Shell Programming and Scripting
Hi, I've been trying to develop a script that performs the parsing of a log every 1 minute and then generating some statistics. I'm fairly new to programming and this is why I come to ask if I can lend a hand.
this is my log:
xxxx 16/04/2012 17:00:52 - xxxx714 - E234 - Time= 119 ms.... (8 Replies)
Discussion started by: jockx
8 Replies
9. Solaris
I have a Solaris 10 server that notified one of my users/database administrators of another users account expiring within X amount of days. It attempted to email the user@ server.com, which failed and was forwarded from the mailer-daemon@ server.com, to the DBA. She's not listed as an alias for... (2 Replies)
Discussion started by: Nvizn
2 Replies
LEARN ABOUT PHP
ssl_clear
SSL_clear(3SSL) OpenSSL SSL_clear(3SSL)
NAME
SSL_clear - reset SSL object to allow another connection
SYNOPSIS
#include <openssl/ssl.h>
int SSL_clear(SSL *ssl);
DESCRIPTION
Reset ssl to allow another connection. All settings (method, ciphers, BIOs) are kept.
NOTES
SSL_clear is used to prepare an SSL object for a new connection. While all settings are kept, a side effect is the handling of the current
SSL session. If a session is still open, it is considered bad and will be removed from the session cache, as required by RFC2246. A
session is considered open, if SSL_shutdown(3) was not called for the connection or at least SSL_set_shutdown(3) was used to set the
SSL_SENT_SHUTDOWN state.
If a session was closed cleanly, the session object will be kept and all settings corresponding. This explicitly means, that e.g. the
special method used during the session will be kept for the next handshake. So if the session was a TLSv1 session, a SSL client object will
use a TLSv1 client method for the next handshake and a SSL server object will use a TLSv1 server method, even if SSLv23_*_methods were
chosen on startup. This will might lead to connection failures (see SSL_new(3)) for a description of the method's properties.
WARNINGS
SSL_clear() resets the SSL object to allow for another connection. The reset operation however keeps several settings of the last sessions
(some of these settings were made automatically during the last handshake). It only makes sense for a new connection with the exact same
peer that shares these settings, and may fail if that peer changes its settings between connections. Use the sequence SSL_get_session(3);
SSL_new(3); SSL_set_session(3); SSL_free(3) instead to avoid such failures (or simply SSL_free(3); SSL_new(3) if session reuse is not
desired).
RETURN VALUES
The following return values can occur:
0 The SSL_clear() operation could not be performed. Check the error stack to find out the reason.
1 The SSL_clear() operation was successful.
SSL_new(3), SSL_free(3), SSL_shutdown(3), SSL_set_shutdown(3), SSL_CTX_set_options(3), ssl(3), SSL_CTX_set_client_cert_cb(3)
1.0.1e 2013-02-11 SSL_clear(3SSL)