Displaying 20 results from an estimated 11000 matches similar to: "[Bug 84] last command provides incorrect information on Solaris 8"
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
2002 Mar 11
7
[Bug 158] ssh-add trips up due to missing key types
http://bugzilla.mindrot.org/show_bug.cgi?id=158
------- Additional Comments From wknox at mitre.org 2002-03-12 06:43 -------
Created an attachment (id=38)
Patch to fix described problem
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2004 May 27
1
Problem with VFS audit and recycle
Is there anyone running Samba 3.0.X on Solaris 8 that has VFS working? I
am dying to know if this is a problem with my setup or if there is
something else going on. If you do have it working, please let me know
which module. Thanks.
Bill Knox
Lead Operating Systems Programmer/Analyst
The MITRE Corporation
---------- Forwarded message ----------
Date: Tue, 25 May 2004 13:54:26 -0400
2006 May 15
11
[Bug 1189] Stacked PAM modules hang root logout
http://bugzilla.mindrot.org/show_bug.cgi?id=1189
Summary: Stacked PAM modules hang root logout
Product: Portable OpenSSH
Version: 4.3p2
Platform: UltraSparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: PAM support
AssignedTo: bitbucket at mindrot.org
ReportedBy:
2006 May 22
5
[Bug 1189] PAM module hangs root logout
http://bugzilla.mindrot.org/show_bug.cgi?id=1189
wknox at mitre.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Stacked PAM modules hang |PAM module hangs root logout
|root logout |
------- Comment #12 from wknox at mitre.org 2006-05-22
2002 Feb 13
3
[Bug 87] Last logon that gets reported upon login is the current login time
http://bugzilla.mindrot.org/show_bug.cgi?id=87
------- Additional Comments From djm at mindrot.org 2002-02-13 23:14 -------
so a PAM session module is setting the last login time before we retrieve it?
Why not just disable the module in the PAM config?
BTW you should attach your patch using the "create a new attachment" link (under
the keywords entry). Pasting them into the
2003 Jan 14
3
[Bug 468] 3.5p1 authentication error on Solaris 8
http://bugzilla.mindrot.org/show_bug.cgi?id=468
------- Additional Comments From wknox at mitre.org 2003-01-15 07:36 -------
I'm not seeing this behavior on my Solaris 8 systems - latest patch cluster
(1/8/03), including patch 109007-08.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2004 Nov 18
3
Domain authentication failing after a period of time
I am having an unusual bit of behavior with a recently upgraded 3.0.8
installation (from 3.0.2a). I upgraded the server and retained the
secrets.tdb file. The server itself is using security = domain, and it had
been joined to the domain prior to the upgrade. Now, once I started the
new version, I couldn't log on, and would get the error "There are no
logon servers available to service
2002 Jan 30
0
[Bug 87] New: Last logon that gets reported upon login is the current login time
http://bugzilla.mindrot.org/show_bug.cgi?id=87
Summary: Last logon that gets reported upon login is the current
login time
Product: Portable OpenSSH
Version: 3.0.2p1
Platform: UltraSparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo:
2007 Apr 06
2
mbox sync/lock issue, rc28 and later
Help!
I just noticed this error this morning, we have been getting a
lot of these in rc28 and rc29, not in rc27 or before:
Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file /var/mail/j/jaearick was modified while we were syncing, check your locking settings
Pine coughed up an internal error, no core dump, and dovecot
basically doubled the size of my mailbox by
2002 Nov 05
3
Nothing work : Win2k Nethwork path not found
HI all,
ok. I read all the entries of this mailinglist with the subject nethwork path. I try everything but
nothing happens. I have no more ideas what i can do. Pleaaaaaaasssseeee heeeeellllllppppp.
(I also tried to walk throught document.txt)
The problem:
-Client Win2k
-Server Suse Linux 8.0 with Samba
-I completely installed and configured Samba. I walk throught the document of Samba. I tried
2002 May 17
16
[Bug 245] SSH can not log out under Solaris 2.6
http://bugzilla.mindrot.org/show_bug.cgi?id=245
------- Additional Comments From wknox at mitre.org 2002-05-18 00:58 -------
Same issue with Solaris 8 built with gcc 2.95.2 with the following configure
options:
--without-rsh --with-tcp-wrappers --with-pam --disable-suid-ssh
--with-prngd-socket
--with-default-path=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
Running a ssh -v
2000 Feb 02
1
Samba disappearing from WINS
We are running samba 2.0.4b to provide corporate print services.
Everything with regards to printing is working like a charm. However,
twice in the past two weeks, some of our Samba servers have disappeared
from the WINS servers. The WINS servers are NT servers running 4.0SP5.
The strangest part was that in one occurrence, it was the lone samba
server at one location, but in the other
2002 Oct 16
0
[Bug 84] last command provides incorrect information on Solaris 8
http://bugzilla.mindrot.org/show_bug.cgi?id=84
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |misiek at pld.org.pl
------- Additional Comments From djm at mindrot.org 2002-10-16 13:08 -------
*** Bug 301 has been marked as a
2005 Dec 26
1
[Bug 1116] Solaris 10: mucho remote terminal problems
http://bugzilla.mindrot.org/show_bug.cgi?id=1116
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Comment #2 from djm at mindrot.org 2005-12-27 10:36
2002 Apr 05
2
[Bug 87] Last logon that gets reported upon login is the current login time
http://bugzilla.mindrot.org/show_bug.cgi?id=87
stevesk at pobox.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |openssh-unix-dev at mindrot.org
AssignedTo|openssh-unix-dev at mindrot.org|stevesk at pobox.com
------- Additional Comments From
2007 Feb 02
2
1.0.rc20 released
http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz
http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig
So, rc19 was somewhat broken. How about this version?
+ dovecot: Added --log-error command line option to log an error, so
the error log is easily found.
+ Added mail_log_max_lines_per_sec setting. Change it to avoid log
throttling with mail_log plugin.
- Changing message flags
2007 Feb 02
2
1.0.rc20 released
http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz
http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig
So, rc19 was somewhat broken. How about this version?
+ dovecot: Added --log-error command line option to log an error, so
the error log is easily found.
+ Added mail_log_max_lines_per_sec setting. Change it to avoid log
throttling with mail_log plugin.
- Changing message flags
2008 Jul 14
5
EOL in stderr of ssh - Linux
Hello everyone,
recently I've found something I consider a bug.
Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A.
Imagine my surprise when I saw that all messages that are being output
on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are
terminated with 0x0D, 0x0A.
Maybe that's standard behaviour of all stderr messages in all Linux