similar to: sshd startup error on SCO SR6

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, building OPENSSH v4.3p2 on OSX 10.4.7, all's fine (config, nake, install, exec) out-of-the-box. so, to be clear, this is NOT a blocker, by any stretch ... that said, however ... if, instead of a don't-monkey-with-it build, prior to ./configure, i: autoreconf -i -f then, a subsequent: ./configure \ --prefix=/usr/local/openssh \

Hi, Sorry for the last mail with wrong subject. I am a LLVM newbie, I have read some tutorials of LLVM, and play with some demos. I am developing a Hadoop native runtime, it has C++ APIs and libraries, what I want to do is to compile Hive's logical query plan directly to LLVM IR or translate Hive's physical query plan to LLVM IR, then run on the Hadoop native runtime. As far as I know,

Hi Chang, > I am developing a Hadoop native runtime, it has C++ APIs and libraries, > what I want to do is to compile Hive's logical query plan directly to LLVM > IR or translate Hive's physical query plan to LLVM IR, then run on the > Hadoop native runtime. As far as I know, Google's tenzing does similar > things, and a few research papers mention this technique, but

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

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

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

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

In configure for openssh 4.3p2 is this: as_executable_p="test -f" as_executable_p, as the name suggests, is used to test whether a file is executable or not, so should use -x and not -f. Discovered after doing chmod a-x gcc so configure would not discover it, but found it anyway. -- Roger Cornelius rac at tenzing.org

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

https://bugzilla.mindrot.org/show_bug.cgi?id=2279 Bug ID: 2279 Summary: ListenAddress option does not allow IPv6 link-local addresses Product: Portable OpenSSH Version: 6.6p1 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: sshd

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.

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

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

Hello All, I have multiple OCFS2 clusters on SLES10 SP2 running Xen. We needed to increase the O2CB_HEARTBEAT_THRESHOLD from 31 up to 61 and did so successfully on 2 of our 3 clusters. However on one of the three clusters we are not able to change the value. The /etc/sysconfig/o2cb file contains 61 as the threshold after reconfiguring via /etc/init.d/o2cb configure, we reconfigure all 3 nodes at

I was wondering what everyone's thoughts were on a simpler way to exclude addresses from having listeners on them. I know a lot of people have multiple subnets, especially larger corporations. Some networks are non-route-able, and therefor unsuitable for use with SSH, aside from communication between other servers on the same subnet. Given that we may want to exclude those non-route-able

I'm not a ssh expert and I don't know if the log is good or bad, but I too am running OpenSHH under OpenServer. I find that after I connect, the return key has no effect unless I first type: stty sane <Ctrl>j If you've hit <ENTER> before that you must first press <Ctrl>j a couple of times to clean out the buffer. After I type the above command, everything

(Maybe this is a re-posting: sorry for that.) Hello, a SonicWALL appliance that protects my servers' LAN has suddenly begun to refuse OpenSSH connections with the following message: 'SSH 2.0 Overly Long Protocol Version Exchange String, SID: 3696, Priority: High - This signature detects overly long "Protocol Version Exchange" string in SSH 2.0. The maximum length of the

Good Day to You! THANKS for ALL your work on this project! We appreciate any help you can give! ----We are attempting to install OpenSSH v4.3p2 on OpenStep 4.2 for Intel -----our configure completes but when we run make we get: labnx02:136# make cc -g -O2 -Wall -Wpointer-arith -Wuninitialized -I. -I. -I/usr/local/ssl/include -I/usr/local/include -DSSHDIR=\"/usr/local/etc\"