similar to: inconsistent ut_id values in the utmp(x) file

Displaying 20 results from an estimated 4000 matches similar to: "inconsistent ut_id values in the utmp(x) file"

2001 Sep 06
0
line_abbrevname patch
Once upon a time there were two places in the loginrec code that were ifdef'd sgi and which stripped the "tty" off the line along with the "dev" when recording utmp. (Specifically it was being done in line_stripname and line_abbrevname.) Doing that in line_stripname was wrong, because it broke things like wall that expected the ut_line to have the "tty" present.
2002 Apr 12
0
[Bug 214] New: IRIX utmp problem loginrec.c: line_abbrevname() goes wrong
http://bugzilla.mindrot.org/show_bug.cgi?id=214 Summary: IRIX utmp problem loginrec.c: line_abbrevname() goes wrong Product: Portable OpenSSH Version: 3.1p1 Platform: MIPS URL: http://groups.google.de/groups?hl=de&selm=3B979A7D.10809 06%40nowhere.org&rnum=4 OS/Version: IRIX
2002 Dec 29
0
[Bug 460] New: ut_addr_v6 not used
http://bugzilla.mindrot.org/show_bug.cgi?id=460 Summary: ut_addr_v6 not used Product: Portable OpenSSH Version: 3.5p1 Platform: All URL: http://bugs.debian.org/167867 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at
2003 Sep 05
2
3.6p1 bug on SCO OpenServer
SCO OpenServer 5.0.x Openssh 3.6p1 loginrec.c writes incorrect data into the ut_id field of the utmp file. This has been an issue since at least openssh 3.0.2 but I never bothered to report it. For Openssh 3.6p1, defining WITH_ABBREV_NO_TTY corrects the problem. Below is a brief patch to configure which does this. You can observe the errant results in the "Line" column from the
2002 Dec 08
1
Password expiry related clarification in OpenSSH3.5p1
fyi (i'm behind in following the passord expire efforts). ----- Forwarded message from Logu <logsnaath at gmx.net> ----- Date: Sat, 7 Dec 2002 02:42:52 +0530 From: "Logu" <logsnaath at gmx.net> To: <stevesk at cvs.openbsd.org> Cc: <kumaresh_ind at gmx.net> Subject: Password expiry related clarification in OpenSSH3.5p1 Hello Stevesk, We are using
2005 May 03
1
which PID should be written to utmp/wtmp file
Hi, For each user connection when privilege separation is enabled, 3 processes are of interest for this topic. 1. sshd:[priv] - privileged user process. 2. sshd:user at pts/0 - user process. 3. shell - shell process. Openssh code writes the #2. sshd:user at pts/0 - user process to the utmp/wtmp file. Is this the correct behaviour.? Or should it write the #3. shell
2001 Nov 20
0
PATCH: Fixing last/utmpx for Solaris
In case it is any help, here is the patch against openssh-3.0.1p1 that corrects the problem with last reporting on Solaris that I sent to the list a week or so ago against 3.0p1. There was no conversation about this aside from Rip Loomis' comment about including it to support BSM auditing - does this present a problem for other OSes to include the ut_name field in the utmpx entry? Should this
2002 Jan 29
0
[Bug 84] New: last command provides incorrect information on Solaris 8
http://bugzilla.mindrot.org/show_bug.cgi?id=84 Summary: last command provides incorrect information on Solaris 8 Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org
2001 Nov 15
1
Patch for "last" providing incorrect information on Solaris 8
I have put together a simple set of diffs that corrects the problem described by Steven Fishback <sfishback at interpath.net> on 10-30 on this list regarding incorrect information reported by last on Solaris. The patches merely pass along the username in the utmpx record for a logout. Is there any reason why this would be a problem with other OSes? If not, maybe this could be rolled into the
2000 Mar 20
2
samba-2.0.7pre2 compilation on SunOS 4.1.4 with --with-utmp
samba-2.0.7pre2 (out of the box) compiles and works well on my test file server; however after ./configure --with-utmp the compilation fails... Andrew ... smbd/connection.c: In function `utmp_fill': smbd/connection.c:328: structure has no member named `ut_user' smbd/connection.c:329: structure has no member named `ut_id' smbd/connection.c:332: structure has no member named
2002 Apr 23
1
[Bug 214] IRIX utmp problem loginrec.c: line_abbrevname() goes wrong
http://bugzilla.mindrot.org/show_bug.cgi?id=214 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From djm at mindrot.org 2002-04-23 23:08 ------- Similar patch applied - please test tommorow's
2005 Apr 23
7
OpenSSH is not asking for passwords.
I am trying to use shfs to mount a remote root filesystem for a diskless workstation. The system downloads its kernel and initrd from a server. I have tried repeatedly to get a working installation of ssh on the initrd with no success. I finally got ssh to connect to the server. Normally when I use ssh the session goes as follows [arrummzen at localhost LFS-BOOK-6.0-HTML]$ ssh 192.168.11.10 -l
1999 Dec 28
1
ANNOUNCE: openssh-1.2.1pre22
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks
1999 Dec 28
1
ANNOUNCE: openssh-1.2.1pre22
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks
2001 Jun 29
1
wtmpx problem on Solaris 8 sparcv9 (64bit) environment
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
2009 Feb 08
2
how to make this qq plot in lattice and/or ggplot2
Hi Group, Here is some data. p <- runif(1000) # sample data groups <- rep(c(1,2),each=500) #conditioning variable mydata <- cbind(p,groups) n <- length(p) u <- (1:n)/(n + 1) # uniform distribution reference for qqplot logp <- -log(p,base=10) logu <- -log(u,base=10) qqplot(logp,logu) How can I make the above qqplot in lattice and/or ggplot2. The sample is uniform, and I take
2007 Oct 31
1
Simple Umacs example help..
Hello all... I am just starting to teach myself Bayesian methods, and am interested in learning how to use UMacs. I've read the documentation, but the single example is a bit over my head at the level I am at right now. I was wondering if anyone has any simple examples they'd like to share. I've successfully done a couple of simple gibbs examples, but have had a hard time
2000 Jul 03
0
FreeBSD 3.5-STABLE
gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\" -DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" -DHAVE_CONFIG_H -c loginrec.c loginrec.c: In function `construct_utmp': loginrec.c:619: structure has no member named `ut_user' loginrec.c:619: structure has no member named `ut_user'
2000 Jul 01
0
Problem with cleaning utmp entry
Hello I have problem with OpenSSH 2.1.1p1 on libc5 system (Slackware 4). I'm not sure if I had those problems with 1.2.x version of OpenSSH (on the same system), but I don't think so. When someone ends ssh session (logout, or something) utmp entry for that user doesn't get erased from UTMP file. In 'finger' I can see a lot of multiplicied users that are not actually logged
2004 Apr 28
1
[Bug 855] doesn't properly log logout event in utmp entry when pts bigger than 999
http://bugzilla.mindrot.org/show_bug.cgi?id=855 Summary: doesn't properly log logout event in utmp entry when pts bigger than 999 Product: Portable OpenSSH Version: 3.8p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: