Displaying 5 results from an estimated 5 matches for "sirle".
Did you mean:
simle
1999 Dec 30
3
ANNOUNCE: openssh-1.2.1pre24
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
openssh-1.2.1pre24 is being uploaded to:
http://violet.ibs.com.au/openssh/files/
This release fixes the silly bugs (almost all autoconf related) that
crept into yesterday's release.
19991231
- Fix password support on systems with a mixture of shadowed and
non-shadowed passwords (e.g. NIS). Report and fix from
HARUYAMA Seigo
1999 Dec 30
3
ANNOUNCE: openssh-1.2.1pre24
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
openssh-1.2.1pre24 is being uploaded to:
http://violet.ibs.com.au/openssh/files/
This release fixes the silly bugs (almost all autoconf related) that
crept into yesterday's release.
19991231
- Fix password support on systems with a mixture of shadowed and
non-shadowed passwords (e.g. NIS). Report and fix from
HARUYAMA Seigo
2006 Aug 10
6
3.0.20 -> 3.0.23 SID/group error?? Won't connect.
Gerry, all:
HELP! On mandriva, I compiled samba from source and got it running, but
I cannot connect from windows. (see my post from earlier "[Samba] Compiling
and Configuring Samba for Mandrival")
I think this relates to the group/SID changes discussed in the release
notes. However, I'm not smart enough to figure it out. The tarball compiled
and installed fine. It
2023 May 16
2
[Bug 3573] New: sshd service crashes with "error 1067: Service terminated unexpectedly" when I try to start it in Windows 11
...Windows 11
Product: Portable OpenSSH
Version: 8.6p1
Hardware: Other
OS: Windows 11
Status: NEW
Severity: minor
Priority: P5
Component: sshd
Assignee: unassigned-bugs at mindrot.org
Reporter: sirleeofstanford at gmail.com
I cannot seem to start the openssh server service in Windows 11 (sshd).
I've tried to start the service from PowerShell and through Windows 11
Services App. When I try to start the service in the Services App, it
tries to start the service but crashes and gives me err...
1999 Aug 19
1
dptr_create: returned 9: Error - all new dirptrs in use ?
Hi,
I get this error message in the log for a Win98 client which is regularly
scanning a directory on the share. When this happens the client no longer
can access any data in the shares (security=share), only the toplevel
directory structure of a share is still accessible. This seems to be a new
problem in 2.0.5/6pre (not sure if it already happened for 2.0.4). Any hints?
Franz.
Platform: