similar to: [SUMMARY] Problems with 'last' (when OpenSSH compiled 64-bit)

Previously 3.2.2 would not compile under Solaris, then 3.2.3 came out with a bug fix for the problem. Now 3.2.3 won't compile under IRIX 6.5.14. I've tried using both gcc 3.0.1 and the IRIX MIPSpro 7.1 compilers. I've been compiling previous versions of OpenSSH for years using these same compilers (we haven't updated the MIPSpro compiler for 3 years, and I've been using it on

Note that this wasn't necessary on previous versions of OpenSSH under SunOS 4.1.4. Dave Foster ------------- Begin Forwarded Message ------------- Date: Mon, 1 Jul 2002 11:21:25 -0700 (PDT) From: spl at camshaft.ucsd.edu To: foster at dim.ucsd.edu Subject: Re: Oh SunOS guru... (OpenSSH compile on Pitstop) > Ok, I FINALLY GET OpenSSH to configure on Pitstop, getting around > the

greetings list, i am creating a new thread because of comment made by; From: Nicolas Thierry-Mieg <Nicolas.Thierry-Mieg at imag.fr> in thread "Subject: [CentOS] erase disk". in past readings about; erasing an hdd, forensics of hard disk drives, dban, destroying hdd i submit these links for those who may wish to further their knowledge on primaries of hdd forensics;

On SCO 5.0.7 and openssh 3.8.1p1, two entries are written to /etc/wtmp and /etc/wtmpx each time a user logs in via ssh. This can be demonstrated using the last(C) command. Any user connected via ssh will have two identical login and logout entries. On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined). wtmp_write_entry()

sessreg is used by display managers such as xdm and gdm to record X sessions in utmp, wtmp, and lastlog files. This release attempts to clean up some inconsistencies around the handling of the various files. Long long ago, Unix systems had a utmp file to record who was currently logged in, and a wtmp file to record login history. Long ago, extended versions of the files & APIs for them were

Hello When I was using OpenSSH-2.9p2 in Solaris 8 sparcv9 (64bit) environment, I found some trouble that wtmpx has broken. The size of utmpx structure object becomes larger than 32 bit environment in sparcv9 environment.Therefore, instead of using utmpx structure object, using futmpx structure object is better. In sparcv9 environment, futmpx structure object is used instead of utmpx structure

http://bugzilla.mindrot.org/show_bug.cgi?id=464 ------- Additional Comments From pas50 at cam.ac.uk 2003-01-09 02:11 ------- This is apparently a bug with compiling in 64 bit. David foster saw this. http://www.sunmanagers.org/pipermail/summaries/2002-October/004018.html ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hi, Solaris (tested with 2.6) needs a username in the logout record in the wtmpx file. Currently openssh (version 2.3.0p1) leaves the username (utmpx.ut_user) empty in logout records, which leads to conflicting results from the last command. Example: # last -5 siegert siegert pts/186 stikine.ucs.sfu. Mon Jan 15 14:26 still logged in siegert pts/105 stikine.ucs.sfu. Mon Jan 15

Hi, I just installed OpenSSH 4.3p1 on our Solaris 8 machines and 'last' now shows wtmpx entries for ssh logins like zierke pts/4 Thu Jan 1 01:00 still logged in zierke pts/3 Thu Jan 1 01:00 - 10:56 (13183+09: instead of e.g. zierke pts/3 rzdspc10.informa Sat Feb 4 10:54 - 10:54 (00:00) zierke pts/2

It appears to be a pervasive assumption in the Portable OpenSSH code that wtmp and wtmpx records for the end of a session do not need to include the user name or hostname. Unfortunately Solaris appears not to go along with that assumption; the Solaris "last" command shows all login sessions initiated by OpenSSH as never terminating, or sometimes terminating with the user's next

http://bugzilla.mindrot.org/show_bug.cgi?id=348 Summary: infinite loop scanning wtmpx Product: Portable OpenSSH Version: -current Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: rodney at

http://bugzilla.mindrot.org/show_bug.cgi?id=464 Summary: sshd seems to corrupt the wtmpx Product: Portable OpenSSH Version: 3.5p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: minor Priority: P4 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: pas50

Hi, I've installed openssh-2.1.0p2 on a Solaris 8 host (SPARC). The sshd corrupts utmpx/wtmpx when a client connects to this machine. Observable error: $ who who: Error --- entry has ut_type of 28265 when maximum is 9 It can be repeated and is attributable to the login done by sshd. Now, Solaris has only utmpx/wtmpx and not the old utmp/wtmp. It get's worse as more logins take place

I'm seeing a problem using OpenSSH v2.9.9p2 on solaris and the usage of the "last" command. The "last <username>" usage is displaying the sessions as still being logged on the server when it's really not. The "last" by itself shows correct information about the session. Sometimes using the "last <username>" syntax the session shows

Dear All, Apologies for sending this email to both list, but at this point I'm not sure which one could help me the most. I have 4 sets of data, 1 test and 3 different sets of controls. The measurements are binary, with a matrix of 0 and 1 I'm measuring across time (rows, ~815) the behaviour of organelles in the cell by microscopy in response to different stimuli (several measurements

Using UseLogin on a system that has to twiddle utmpx before calling login currently also twiddles wtmpx, and this causes problems on Solaris in the "last" log. Changing the source to avoid modifying wtmpx when also modifying utmpx fixes things up nicely: Index: loginrec.c --- loginrec.c 2001/05/08 20:33:06 1.33 +++ loginrec.c 2001/06/06 17:14:25 @@ -456,9 +456,10 @@ # endif # ifdef

Hi :-) i have rollout a new ssh pakage in our environment. Apr 27 12:06:03 systemx sshd[869]: [ID 847 auth.info] wtmp_write: problem writing /var/adm/wtmp: No such file or directory Solaris 8 has no /var/adm/wtmp, it use /var/adm/wtmpx In the old package there was many of this messages I compiled the new package with --disable-wtmp \ --enable-wtmpx \ but sometimes one of this message are in

Dear admin, I am working in St George Bank, Australia. I have installed Openssh 4.0p1 and 4.5p1 on our Sun Solaris 8 unix servers. We experience some bug when we launch a window on PC using ReflectionX by method Openssh to any of our Solaris 8 servers, there is no update login and logout information about users on /var/adm/wtmpx. Simply said when we using Reflection X to login a Solaris 8 server

http://bugzilla.mindrot.org/show_bug.cgi?id=122 ------- Additional Comments From tim at multitalents.net 2002-02-25 05:32 ------- I spent some time looking into this. Initially I did see that last was reporting users still logged in that had logged out of their ssh connection. I noticed logintest showed everything working as expected. Now I can not duplicate the problem. I didn't change

[Mod: I am approving this message even though it is just a rehash of known vulnerabilities of DNS. Please in future lets avoid rehashing what was alreadt discussed in probably every single mailing list that deals with UNIX security several years ago? -- alex ] ###### ## ## ###### ## ### ## ## ######