similar to: openssh 4.3p2 configure problem

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

3.8p1 added the following to main() in sshd.c: #ifndef HAVE_CYGWIN /* Clear environment */ environ[0] = NULL; #endif This breaks the getenv("TZ") in session.c and causes logins to occur in GMT time. It also causes any sshd syslog messages to be written in GMT time. I'm on SCO Openserver 5.0.7, but this looks like it should affect all platforms. Am I missing something? I

openssh 4.7p1 SCO OSR6 Password authentication is non-functional. This seems dependent on USE_LIBIAF which further depends on HAVE_LIBIAF (in defines.h), but there is no longer any code in configure to define the latter. Building with HAVE_LIBIAF defined enables password authentication, but only for non-long (<9 char) passwords, even though UNIXWARE_LONG_PASSWORDS seems to be defined. I

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()

I read the exchange regarding > 8 char passwords on Unixware from the end of June. Is anything being done to add support for >8 character passwords on SCO OSR6 (in udk mode)? I have it working by calling osr5bigcrypt(), instead of bigcrypt(), in openbsd-compat/xcrypt.c and linking with -lcrypt. libcrypt has bigcrypt(), but for whatever reason, openssh built with it fails to authenticate

Openssh 4.4p1 and 4.5p1 SCO Openserver 6 w/mp1, mp2 While installing v4.5p1, I noticed this sshd syslog error which began appearing when I upgraded from v4.3p2 to v4.4p1: Sep 1 17:54:41 tenzing sshd[12837]: error: Bind to port 22 on :: failed: \ Network is unreachable. sshd -d reports: debug1: Bind to port 22 on ::. Bind to port 22 on :: failed: Network is unreachable. debug1: Bind

Build of 5.1p1 fails on SCO OSR6 with the error: UX:acomp: ERROR: "addrmatch.c", line 100: undefined struct/union member: sin6_scope_id configure checks for presence of struct sockaddr_in6 and uses the system declaration if found (via #define HAVE_STRUCT_SOCKADDR_IN6 in config.h) If not found, the struct is declared in openbsd-compat/fake-rfc2553.h. OSR6 has struct sockaddr_in6 but it

3.0.20 documentation bug: The smbclient's printmode command (which didn't actually do anything) has been removed in samba 3.0.20 but is still documented in the smbclient man page. -- Roger Cornelius rac@tenzing.org

Openssh 5.5p1 and 5.6p1 SCO OpenServer 5.0.7 I've built various versions of openssh on SCO OSR5.0.7 over the years without much of a problem. Beginning with 5.5p1 however, I have been unable to get a working install. I'm building with gcc 2.95.3. The build completes normally, but 'make tests' fails on several tests: sftp-cmds.sh failures (get command fails on both): - get

If SCO OpenServer is configured for large passwords, i.e. u_pwseg is greater than 1 in /etc/auth/system/default, then user authentication in auth-passwd.c will fail for users whose passwords are longer than 8 characters. The "traditional" level of security installs with u_pwseg#1, so most users would never encounter this problem. This has been an issue in openssh since I started using

Is anyone still using OpenSSH on SCO Open Server 3? My clients no longer run Open Server 3. The entropy gathering code changes have broken the Open Server 3 build. If there is still interest I'll work on it. If not, I have no need for it. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net

No "ssh -X hostname" doesn't work. But when you "export DISPLAY=..." it works!? I set the the Display Hack so that I can see my IP with "env" or "echo SSH_CLIENT" when I'm connect via VPN-Tunnel and I don't know my IP in the Net I'm connected through. Andreas Kerl ----------------------------------------- DTS Medien GmbH Heidestrasse 38

Okay, here's what you need to do. You have to configure apache. This won't be too hard. You will need to edit the httpd.conf located in /etc/httpd/conf directory. Look through the httpd.conf file until you find this line: #Servername localhost It may or may not have the # in front of it. You need to edit this line and make it say: Servername yourservernamegoeshere For example,

Hello List, I tried to set up openvpn with the shorewall on my openwrt box but failed! I am not able to access the "loc"al Network from my vpn. I followed the roadwarrior setup. I define a vpn zone, that should be able to access the firewall and the local network: vpn fw ACCEPT info fw loc ACCEPT info vpn

Howdy, Not sure, but it appears that OpenSSH_4.3p1 on solaris creates bad wtmpx entries during login? mgoebel pts/5 Wed Dec 31 19:00 still logged in It is creating entries for Dec 31st 1969. Thanks, Matt -- Matthew Goebel : goebel at emunix.emich.edu : Unix Jockey @ EMU : Hail Eris Neo-Student, Net Lurker, Donut consumer, and procrastinating Furry Fan.

Hi, > 1) Knowing when to perform specialization. If the call was not inlined > the function is probably big. Getting this wrong will generate *a lot* > of code for very small (if not negative) speed gain. Could you elaborate why just having (lots of) more code in the final executable will incur a performance _penalty_? I was thinking of something similiar, but for type-specializations of

Hello, Unfortunately, the dovecot instance doesn't belong to me and I have no way to get the configuration. However, if that can help I've been able to reproduce this behavior on every dovecot installations I've tried. 2016-04-25 8:32 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > > > On 24.04.2016 04:44, Cornelius Charlie wrote: > > Hello, > > > >

Hi, with ldap-backend, i can't set permission for shares groupwise. This is my smb.conf for a share: [cad] ? ? ? ? comment = STT CAD ? ? ? ? path = /home/data/cad ? ? ? ? readonly = yes ? ? ? ? browseable = yes ? ? ? ? valid users = @cad ? ? ? ? write list = @cad ? ? ? ? force group = cad ? ? ? ? create mask = 0664 ? ? ? ? directory mask = 0775 But this isn't working. no user of the

I'm just learning how yo use Samba, the version I downloaded is Samba 2.0.7. Needless to say this is my first time and I'm lost. I'm sure Samba is loaded to the system. Oh I using Linux RedHat 7.0. I'm now lost on how to get the swat working, if anyone could shed any light on this subject it would be greatly appreciated. Sean Cornelius -------------- next part -------------- HTML

Hello, i have a red hat 7.2 system and set the environment variable CC='kgcc'. I have git the standard kernel: [root@linux-test source]# rpm -qf /usr/include/asm/statfs.h kernel-headers-2.4.7-10 But when compiling the tng-source i get the following error: Using FLAGS -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -I./lib -DLOGFILEBASE="/ usr/local/samba/var"