Displaying 20 results from an estimated 5000 matches similar to: "[Bug 303] New: conftest fails to determine mmap anon shared"
2002 Jun 28
1
[Bug 303] conftest fails to determine mmap anon shared
http://bugzilla.mindrot.org/show_bug.cgi?id=303
mouring at eviladmin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From mouring at eviladmin.org
2002 Jun 29
1
[Bug 322] Anon shared MMAP test fails wrongly under FreeBSD
http://bugzilla.mindrot.org/show_bug.cgi?id=322
gert at greenie.muc.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From gert at greenie.muc.de
2002 Jun 29
0
[Bug 322] New: Anon shared MMAP test fails wrongly under FreeBSD
http://bugzilla.mindrot.org/show_bug.cgi?id=322
Summary: Anon shared MMAP test fails wrongly under FreeBSD
Product: Portable OpenSSH
Version: -current
Platform: ix86
OS/Version: FreeBSD
Status: NEW
Severity: minor
Priority: P3
Component: Build system
AssignedTo: openssh-unix-dev at mindrot.org
2002 Jul 25
0
openssh-unix-dev digest, Vol 1 #505 - 15 msgs
subscribe openssh-unix-dev at mindrot.org
> Send openssh-unix-dev mailing list submissions to
> openssh-unix-dev at mindrot.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
> or, via email, send a message with subject or body 'help' to
> openssh-unix-dev-request at mindrot.org
>
2011 Aug 17
1
openssh-unix-dev Digest, Vol 100, Issue 3
Works on my netbsd tinkerbox.
NetBSD 5.0.2 NetBSD 5.0.2 (GENERIC)
It uses rlimit.
Privsep sandbox style: rlimit
I also get warnings during make.
fmt_scaled.c: In function 'scan_scaled':
fmt_scaled.c:84: warning: array subscript has type 'char'
fmt_scaled.c:111: warning: array subscript has type 'char'
fmt_scaled.c:155: warning: array subscript has type 'char'
2016 Mar 08
2
Need Help to Fix CVE-2008-1483, CVE-2008-5161, CVE-2015-5600 and CVE-2015-6565
Hi Gert,
Thanks for your reply.
But we can't upgrade to 7.2 version also we don't have plan to upgrade in
near future. Can I fix these vulnerabilities in the current version?
Regards
Abhishek
On Tue, Mar 8, 2016 at 6:42 PM, Gert Doering <gert at greenie.muc.de> wrote:
> Hi,
>
> On Tue, Mar 08, 2016 at 06:14:01PM +0530, abhi dhiman wrote:
> > Actually I am working
2001 Nov 12
1
Interesting problem with 3.0p1 and IPv6
Hi,
I just ran into an interesting problem with 3.0p1 on FreeBSD 4.0 and
IPv6/v4 mapped addresses.
If I do "ssh -v machine", where "machine" has an IPv4 address in the
DNS, everything works fine (machine is "hilbert.space.net"):
debug1: Connecting to hilbert [194.59.182.6] port 22.
...
Warning: This may be due to an old implementation of ssh.
debug1: Received
2024 Sep 09
1
OL8 (RHEL8), ssh-rsa turned off using update-crypto-policies, receiving an openssh error that I don't seem to be able to override in my personal .ssh/config file
using "update-crypt-policies --set DEFAULT" allows the connectivity to work
again. setting that but then setting -ssh-rsa... in /etc/ssh/ssh_config
breaks it again. setting my personal .ssh/config file to +ssh-rsa... keeps
it still broken. so I guess my personal .ssh/config file is only used when
something isn't explicitly set in system wide crypto policies or the system
2016 Feb 17
5
Using 'ForceCommand' Option
Gert,
Thank you for the feedback. Can you give any further direction on where to
get more information on what you are describing?
On Wed, Feb 17, 2016 at 3:17 PM, Gert Doering <gert at greenie.muc.de> wrote:
> Hi,
>
> On Wed, Feb 17, 2016 at 12:59:57PM -0600, Lesley Kimmel wrote:
> > I would like to implement an arbitrary script to be executed when logging
> > on via
2001 Oct 31
1
OpenSSH-3.0p1-pre-CVS: configure.ac checks for login in -lutil and -lbsd?
OpenSSH-3.0p1-pre, from CVS as of about 2001-10-30 23:45 UTC.
Any particular reason why configure is checking for login() in -lutil,
finds it, then checks for it again in -lbsd?
Here's the relevant excerpts (Red Hat Linux 6.2, , kernel-2.2.19,
glibc-2.1.3, egcs-1.1.2, autoconf-2.52):
$ CFLAGS='-O2 -mpentium -Wall'; export CFLAGS
$ ./configure
2001 Jul 16
0
No subject
openssh at openssh.com
Dear openssh team !
When I try to configure openssh version 2.9p2 on an ALPHA OSF1 V4.0
I get lots of error messages of the following type
What is missing fundamentally ?
Could this be due to not using gcc ?
How can I solve these problems ?
best regards
S. Hoefinger
2002 Jun 25
0
getnameinfo(), PrivSep, FreeBSD 4.1.1
Hi,
I spent the last couple of hours scratching my head about a problem on
FreeBSD 4.1.1 with OpenSSH 3.3p1.
Without privsep:
debug1: Trying rhosts with RSA host authentication for client user gert
debug3: Trying to reverse map address 195.30.1.100.
debug1: Rhosts RSA authentication: canonical host moebius2.space.net
debug2: auth_rhosts2: clientuser gert hostname moebius2.space.net ipaddr
2002 Mar 12
1
Disconnecting: Corrupted check bytes on input.
Hi,
just "cvs update"'d to get the latest portable version, to start
rebuilding our AIX systems to get zlib-1.1.4 and the channel-bug fix.
SSH protocol 2 seems to work nicely, ssh protocol 1 doesn't work properly.
Environment: AIX 4.3.3, openssl 0.9.6c, openssh as of today (Mar 12, 11:20
GMT).
Client/blowfish, to openssh 3.0p1 or to 2.5.1p1:
debug1: Encryption type: blowfish
2006 Nov 01
0
No subject
(yet-unknown) server key, but just checking all possible locations, not
finding the key, and giving up.
I have seen a similar effect on a system that had a /dev/tty entry that
was not world-writeable (thus the ssh client couldn't open it to ask for
a confirmation).
The effect will also happen if you have "StrictHostKeyChecking yes" in
ssh_config - set that to "ask",
2000 Dec 22
1
bug in sshd.d (destroy_sensitive_data core dumps)
Hi,
experimenting with openssh_cvs on my SCO Unix 3.2v4.2 machine, I had
sshd core dumping on me.
Tracking this, I found that if a host key is specified in the sshd_config
that does not exist (I used "./sshd -d -d -d -f sshd_config" with the
shipped sshd_config file, to work around incompatibilities with the
installed sshd.com's sshd_config, and I do not have ssh2 host keys on
2000 Dec 22
1
Makefile dependencies
Hi,
the openssh_cvs Makefile includes the following rules:
$(LIBSSH_OBJS): config.h
$(LIBOPENBSD_COMPAT_OBJS): config.h
but no equivalent for $(LIBSSHD_OBJS) - is this desired or an oversigt?
In my case, I built the sshd, tested it, reconfigured with SKEY support,
rebuilt (just running "make", no "make clean"), and tracked down the
non-working s/key for a while before I
2001 Feb 16
1
CVS and AIX
Hi,
trying "current CVS" on AIX 4.3.3, yields:
gcc -O2 -Wall -I/usr/local/include -I/gnulocal/include -I/gnu/include -I. -I./openbsd-compat -I. -DETCDIR=\"/etc\" -D_PATH_SSH_PROGRAM=\"/gnu/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/gnu/libexec/ssh-askpass\" -D_PATH_SFTP_SERVER=\"/gnu/libexec/sftp-server\" -DHAVE_CONFIG_H -c auth.c
auth.c: In
2001 Feb 20
2
openssh wish list for 2.6.*
Hi,
something that I'd like to see for the next major release is "build
OpenSSH without installing zlib and openssl".
That is, I have a source tree with the following subdirectories:
.../src/zlib-1.1.3/
/openssl-0.9.6/
/openssh_cvs/
and want "configure", run from openssh_cvs, to be able to find the zlib
and openssl trees in the directory
2001 Mar 08
0
PRNGD/TCP
Hi,
On Wed, Mar 07, 2001 at 10:05:07AM +1100, Damien Miller wrote:
> > now to patching openssh to actually *use* prngd/socket... :-)
> Was done last week - use the "--with-prngd-port=XXX" configure option.
OpenSSH + PRNGD + SCO3 seem to work nicely. Thanks!
One other thing: I'm not fully convinced that current OpenSSH does
everything right regarding utmp/wtmp on SCO3
2001 Aug 30
0
Force S/Key for all but known hosts?
Hi,
I'm not sure if what I'm thinking of is doable with current OpenSSH's,
and if yes, how.
I want to force our users to use S/Key-Authentication, but only if they
do not come from "known hosts". "known hosts" could be hosts that
are listed via IP address ("network 192.168.0.0/24") or hosts that are
listed in ssh_known_hosts - this doesn't really