Displaying 20 results from an estimated 6000 matches similar to: "FreeBSD 3.5-STABLE"
2001 Jun 29
1
wtmpx problem on Solaris 8 sparcv9 (64bit) environment
Hello
When I was using OpenSSH-2.9p2 in Solaris 8 sparcv9 (64bit)
environment, I found some trouble that wtmpx has broken.
The size of utmpx structure object becomes larger than 32 bit environment
in sparcv9 environment.Therefore, instead of using utmpx structure object,
using futmpx structure object is better.
In sparcv9 environment, futmpx structure object is used instead of utmpx
structure
2000 Jun 14
1
OpenSSH 2.1.1p1 on SCO Unixware 7.1.0
Yo All!
I was just trying out OpenSSH 2.1.1p1 on SCO Unixware 7.1.0.
The "configure" dies. See below.
This seems to be the problem:
if test -d "$f" -o -e "$f" ; then
conf_lastlog_location=$f
fi
test is expecting a "shell option" after the "-o".
If I run "/bin/sh ./configure" it fails.
If I run "/bin/bash ./configure it
2011 Sep 02
1
problems building openssh-5.8p1 on qnx
I am having trouble figuring out how to build openssh-5.8p1 for QNX 6.5. I am trying to build on linux, cross-compiling for armv7.
If I configure like this:
configure CC=ntoarmv7-gcc --host=i686-pc-linux-gnu --target=arm-unknown-nto-qnx6.5.0
then I get these errors:
sshconnect.o: In function `timeout_connect':
sshconnect.c:(.text+0x778): undefined reference to
2001 Apr 10
2
Compiling openssh 2.5.p1 on unixware 7.0.1
Hi.
I'm tryng to compile openssh 2.5.p1 (latest)
on sco unixware 7.0.1 and I'm getting
this error in make:
cc -o sshd sshd.o auth.o auth1.o auth2.o auth-chall.o auth2-chall.o
auth-rhosts.o auth-options.o auth-krb4.o auth-pam.o auth2-pam.o
auth-passwd.o auth-rsa.o auth-rh-rsa.o auth-sia.o dh.o sshpty.o log-server.o
sshlogin.o loginrec.o servconf.o serverloop.o md5crypt.o session.o
2000 Jul 01
0
Problem with cleaning utmp entry
Hello
I have problem with OpenSSH 2.1.1p1 on libc5 system (Slackware 4). I'm not
sure if I had those problems with 1.2.x version of OpenSSH (on the same
system), but I don't think so.
When someone ends ssh session (logout, or something) utmp entry for that
user doesn't get erased from UTMP file. In 'finger' I can see a lot of
multiplicied users that are not actually logged
2001 May 15
0
openssh 2.9p1 on Solaris 2.6 with AFS
hello,
I'm attempting to compile 2.9p1 on Solaris 2.6 with AFS support.
I am not using Kerberos aside from AFS. The installation notes state
that Kerberos IV is required by AFS. Since the Kerberos libraries and
header files do not appear to be distributed with AFS, I downloaded and
installed ftp://ftp.pdc.kth.se/pub/krb/src/krb4-1.0.8.tar.gz
./configure --sysconfdir=/etc/ssh
2001 Jul 11
0
Solaris 2.6: Undefined symbol seed_rng
Hi,
I hope I'm not asking some FAQ, but I can't compile openssh-2.9p2 on
maas34:openssh-2.9p2 {173} uname -a
SunOS maas34 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-5_10
using:
maas34:openssh-2.9p2 {174} gcc -v
Reading specs from /opt/local/gcc-2.95.2/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specs
gcc version 2.95.2 19991024 (release)
I get:
maas34:openssh-2.9p2 {172}
2002 Dec 29
0
[Bug 460] New: ut_addr_v6 not used
http://bugzilla.mindrot.org/show_bug.cgi?id=460
Summary: ut_addr_v6 not used
Product: Portable OpenSSH
Version: 3.5p1
Platform: All
URL: http://bugs.debian.org/167867
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at
2000 Jul 08
1
sshd Pam problem for Redhat 6.2
Hi,
There was another message about this from Darren Evans. I am hoping that
the logs from below might shed additional light on this problem (kernel
version 2.2.14). I'm running Redhat 6.2, openssh-2.1.1p2.tar.gz,
openssl-0.9.5a.tar.gz.
I haven't tried to recompile with /usr/src/linux pointing to 2.2.12 per
Darren's solution - that's my next thing to do, or perhaps compile
2000 Aug 26
0
New chroot patch, for 2.1.1p4
Hi there, everybody;
As promised, here's the new version for my chroot patch.
It applies cleanly over OpenSSH 2.1.1p4, and I'm attaching 2 versions:
- openssh-2.1.1p4-chroot.patch-wc, is the chroot patch plus
a "--with-chroot" patch for the "configure" script.
- openssh-2.1.1p4-chroot.patch, is the same without the
"--with-chroot" part.
Have fun,
2000 Jul 02
0
patch for NetBSD utmp (ut_name instead of ut_host)
here are patches to compile portable openssh 2.1.1p2 on netbsd,
and some other platforms I suppose.
itojun
-------------- next part --------------
$NetBSD: patch-aa,v 1.8 2000/07/02 22:07:56 itojun Exp $
--- configure.in.orig Sat Jul 1 15:52:55 2000
+++ configure.in Mon Jul 3 06:49:00 2000
@@ -647,2 +647,6 @@
+OSSH_CHECK_HEADER_FOR_FIELD(ut_name, utmp.h, HAVE_NAME_IN_UTMP)
2000 Oct 04
0
2.2.0p1 chroot patch
Hi there, everyone;
Attached to this mail is the 2.2.0p1 version of my chroot patch.
For those of you interested, my usual warning: This is NOT plug&pray.
You'll have to build a whole binaries/libs/conf files tree within the new
root. (it's just like the "classic" anonymous ftp behaviour)
Configure with "configure --with-chroot" to use.
Regards;
RC
--
2006 Feb 06
1
Compile warning report of openssh 4.3p1 on Intel Macs
Hi.
I was compiling openssh 4.3p1 on Apple's iMac Core Duo computer and
came across following warnings.
configure: WARNING: net/if.h: present but cannot be compiled
configure: WARNING: net/if.h: check for missing prerequisite
headers?
configure: WARNING: net/if.h: see the Autoconf documentation
configure: WARNING: net/if.h: section "Present But Cannot Be
Compiled"
2009 Dec 25
2
[openssh-portable] utmpx and ut_name
Hello OpenSSH hackers,
The last couple of weeks I've been figuring out how hard it is to
replace FreeBSD's <utmp.h> with <utmpx.h>. I don't think utmpx is
perfect, but at least it's better than what we have now and at least it
has gone through some form of standardisation. I noticed POSIX says the
following [1]:
| The <utmpx.h> header shall define the utmpx
2006 Apr 23
0
Configuration Warnings OpenSSH 4.3p2
I don't know enough about this to know if these warnings mean that
I can't build it or not.
Also, since I'm e-mailing anyway, how can I tell what options were
compiled into my exiting ssh:
My system is freeBSD 4.11.
PC% ssh -V
OpenSSH_3.5p1 FreeBSD-20030924, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
PC%
so that I can do the same thing with the newer version. I don't
want to
2001 Oct 26
2
problems building on solaris 2.6
Using the latest cvs sources, the compilation of ssh.c fails.
The 'struct rlimit rlim;' line is being expanded by cpp into
'struct rlimit64 rlim;' and there is no struct rlimit64 defined.
In order to get the struct rlimit64 to be included when the
#include <sys/resource.h>
is used, it appears to need the _LARGEFILE64_SOURCE symbol defined OR
it needs the '#if
2000 Jul 04
0
AW: FreeBSD 3.5-STABLE
At 08:15 04/07/00 +0200, Bladt Norbert wrote:
>> Darren Evans [SMTP:darren at horseplay.demon.co.uk] wrote:
>>
>> gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\"
>-DSSH_PROGRAM=\"/usr/local/bin/ssh\" -
>> DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\"
>-DHAVE_CONFIG_H -c loginrec.c
>> loginrec.c:
2000 Jan 18
1
Error when compiling for Solaris7
I cannot make openssh on Solaris.
The 'make' fails on the first file.
Here are the commands and the output.
Essentially, I pre-built EGD, SSL, and ran:
configure
make
make errors are listed at the bottom.
Can anyone help me get this compiled on Solaris7?
Steve
sdn at sprintlabs.com
./configure --prefix=/common --sysconfdir=/etc/ssh
--with-egd-pool=/common/bin/egd.pl
loading cache
2003 Jun 24
20
[Bug 601] configure script doesen't setup preprocessor flags properly
http://bugzilla.mindrot.org/show_bug.cgi?id=601
Summary: configure script doesen't setup preprocessor flags
properly
Product: Portable OpenSSH
Version: 3.6.1p2
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: major
Priority: P2
Component: Build system
AssignedTo:
2000 Jan 27
1
Long awaited round 1 of NeXT patches.
This is about 90% of the core work. I omited a few files from the patch
set since they are basicly small blocks of #ifndef HAVE_NEXT/#endif to
get it to compile.
Daimen, feel free to let me know what you applied and what your
rejecting and why.. so I can work on cleaning things up.
Andre, Only thing of note you may want to look into is NeXT does not
use "ut_user" in it's lastlog.