Dear All I have a centos server with super user password access. There are a number of users on the same net accessing it via telnet with their dedicated id/pwd . For the supervision purposes, I need to know which user is issuing what command on the server . In other words , monitoring their activities . Can you please let me know how it can be done on the centos? Thank you in advance
Telnet? (insane-non-encrypted-security-hole-protocol) please replace it with openssh. You can use auditd / user accounting / sudosh /rootsh/ or similar tools .. -- Eero 2016-01-19 11:45 GMT+02:00 Hadi Motamedi <motamedi24 at gmail.com>:> Dear All > I have a centos server with super user password access. There are a > number of users on the same net accessing it via telnet with their > dedicated id/pwd . For the supervision purposes, I need to know which > user is issuing what command on the server . In other words , > monitoring their activities . Can you please let me know how it can be > done on the centos? > Thank you in advance > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >
On 1/19/16, Eero Volotinen <eero.volotinen at iki.fi> wrote:> Telnet? (insane-non-encrypted-security-hole-protocol) please replace it > with openssh. > > You can use auditd / user accounting / sudosh /rootsh/ or similar tools .. > > -- > Eero > > 2016-01-19 11:45 GMT+02:00 Hadi Motamedi <motamedi24 at gmail.com>: > >> Dear All >> I have a centos server with super user password access. There are a >> number of users on the same net accessing it via telnet with their >> dedicated id/pwd . For the supervision purposes, I need to know which >> user is issuing what command on the server . In other words , >> monitoring their activities . Can you please let me know how it can be >> done on the centos? >> Thank you in advance >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos >> >Thank you for your reply . This post solved my problem . Thank you again