Looking at http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/cmd-inet/usr.sbin/in.rexecd.c
in.rexecd does not log to wtmpx or utmpx, but, if auditing is enabled, does create audit records for both success and failure(s). Very little is done with syslog though, I think I only saw one early failure case logged. I believe that's very similar to what rsh does, although I haven't looked at the current in.rshd, which by the man page can be used either regular or with Kerberos support. xterm will create a utmpx entry, unless the -ut option (to suppress that) is used, but it will AFAIK (after trying, but not looking at the code) never create a wtmpx entry. On the other hand, ssh does appear to log to wtmpx, even when no terminal is assigned (in which case it uses "sshd" instead of the device name). If client availability of ssh and performance (CPU usage) of the encryption aren't a problem, it would be much better to switch to ssh if possible. All the old r* services are rather evil anyway, either depending on "trusted" IP addresses, or sending passwords over the network in the clear. As such, I suspect they get very little attention. Not to say it wouldn't be nice if there were an option to create wtmpx entries like sshd does. Feel free to submit code yourself... -- This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
