search for: physik3

Displaying 10 results from an estimated 10 matches for "physik3".

Did you mean: physik
2002 Jun 26
2
MAP_ANON replacement?
...mfd = -1; if(mmfd < 0) mmfd = open("/dev/zero", O_RDWR); address = mmap(NULL, size, PROT_WRITE|PROT_READ, MAP_SHARED, mmfd, 0); } Sorry, I have *not* tested it since I am running 3.1p1 and waiting for 3.4p1 announced for next week! Hans Werner Strube strube at physik3.gwdg.de Drittes Physikalisches Institut, Univ. Goettingen Buergerstr. 42-44, 37073 Goettingen, Germany
2001 Sep 28
2
openssh-2.9p2, auth2.c
Even with option "HostbasedUsesNameFromPacketOnly yes", the trailing dot in chost should be stripped before auth_rhosts2() is called from hostbased_key_allowed(). Hans Werner Strube strube at physik3.gwdg.de Drittes Physikalisches Institut, Univ. Goettingen Buergerstr. 42-44, D-37073 Goettingen, Germany Suggested change: *** auth2.c.ORI Wed Apr 25 14:44:15 2001 --- auth2.c Fri Sep 28 10:27:34 2001 *************** *** 801,815 **** debug2("userauth_hostbased: chost %s resolvedname...
2001 Sep 28
3
openssh-2.9p2, short hostnames
...n order to strip the domain name from the remote client name (if it matches the server's DefaultDomain) for use in auth_rhost2, since netgroups usually contain short names in this case. These applies especially to Solaris with NIS hosts and netgroup maps. Hans Werner Strube strube at physik3.gwdg.de Drittes Physikalisches Institut, Univ. Goettingen Buergerstr. 42-44, D-37073 Goettingen, Germany
2006 Dec 06
1
Pre-rev1 compatibility
What about adding some compatibility for pre-rev1 IMAP4 clients which are still around (e.g., CDE dtmail, even in Solaris 10)? Especially, the understanding of command FETCH message (... RFC822.HEADER.LINES (parameters)) instead of FETCH message (... BODY.PEEK[HEADER.FIELDS (parameters)]) (with correspondingly changed replies) would be desirable and shouldn't be too difficult to implement.
2001 Oct 04
0
PAM on Solaris
When openssh-2.9.9p2 is configured with PAM on Solaris 7 (using the system's default /etc/pam.conf) the passwd authentication works: debug1: PAM Password authentication accepted for user "strube" ... debug1: PAM setting tty to "/dev/pts/1" debug1: PAM establishing creds but on logout a message is seen: debug1: Cannot delete credentials[7]: Permission denied Why does
2002 Oct 09
0
Again: Cannot delete credentials
As has often been mentioned, Solaris (at least 7 and 8) gives a debug1 message on logout: Cannot delete credentials. This occurs when in auth-pam.c, function do_pam_cleanup_proc(), pam_setcred(__pamh, PAM_DELETE_CRED) is called under UID 0. I suggested a patch for this on Nov 22, 2001, based on openssh 2.9.9p2 through 3.0.1p1. [The attempt in my patch to reset to UID 0 by "if (!flag)
2003 Sep 29
0
Man Pages
OpenSSH 3.7.1p2, Solaris: The man pages are converted by the awk script mdoc2man.awk. But some commands are not recognized and remain as such, but without the leading dot: .Bk -words .Ek .CM (is .Cm intended?) The script should be enhanced or these commands avoided. I also tried the perl script mdoc2man.pl from OpenSSH 3.5p1, which gives exactly the same results.
2003 Sep 30
2
auth-pam.c, USE_POSIX_THREADS
OpenSSH 3.7.1p2 contains an #ifdef USE_POSIX_THREADS and simulates threads by processes if this is not defined. However, configure and config.h do not provide any means to define this. Is this already included for future releases but does not function properly if defined? Or could it be set manually in config.h and would work in Solaris?
2001 Nov 09
2
openssh-3.0p1, auth2.c
openssh-3.0p1 still contains the bug which I already reported on Sept. 28 2001 for 2.9p2, namely, the trailing dot in chost should be stripped before calling auth_rhosts2() even with option "HostbasedUsesNameFromPacketOnly yes". Otherwise, the host names in /etc/hosts.equiv and .rhosts would have to be dot-terminated. Fix: Move lines 776-779 of auth2.c upwards to after line 767. (These
2001 Oct 24
3
Inconsistent server/client configuration
It appears somewhat inconsistent to me that parameter HostKey is configurable on the server side but fixed on the client side. On the client, always _PATH_HOST_KEY_FILE, _PATH_HOST_DSA_KEY_FILE, _PATH_HOST_RSA_KEY_FILE are used (in this order), whereas on the server, the paths can be specified by up to three HostKey options as arbitrary names in arbitrary sequence. Similarly, option