similar to: AW: X11-Forwarding for Reliant UNIX (formerly SINIX)

Hi ! I promised to report the result to the list. Here it is: Damien Miller [SMTP:djm at mindrot.org] wrote yesterday on his keyboard: > On Mon, 8 Jan 2001, Bladt Norbert wrote: [...] >> During the last week I did some investigations why the X11 forwarding >> on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box >> with OpenSSH-2.3.0p1. >> >> The

Hi ! To all: A Happy New Year ! During the last week I did some investigations why the X11 forwarding on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box with OpenSSH-2.3.0p1. The result fo my investigation is: 1. The OpenSSH sshd opens a TCP/IP-port 6000 + display number and listens to it. This is fine and works with Solaris 7, DEC-OSF 4.0D, Linux and FreeBSD-4.2 but not

Hello, it's me again ! I tried to compile / install OpenSSH on our Reliant UNIX system, OS version 5.45 (and 5.44). The following problems did appear: 1. OpenSSL-0.9.5a will not compile out of the box. The problem on RU 5.45 is, that the compiler does support "long long" but NOT "unsigned long long". The latter just provokes the error message "superfluous

Hi ! I upgraded one of our Reliant UNIX systems from 2.1.1 to 2.3.0p1. Now, I suddenly can't login any more. The error message is: Attempting authentication for illegal user ... The reason is: Password expiration Although I don't use my password to login, at all. I login via RSAAuthentication and this did work with version 2.1.1. Version 2.3.0p1, obviously, checks the password

> Andre Lucas [SMTP:andre.lucas at dial.pipex.com] wrote: > > No! The error message is because I used 'error()' instead of 'debug()'. > That's changed in the 2.1.0p1 release, I believe. (I don't have access > to it right now.) This was discussed last week for 2.1.0 - just change > error() to debug() for those two messages. Sorry, you are completely right.

Joe Warren-Meeks [SMTP:joe at hole-in-the.net] wrote: > open("/usr/local/etc/ssh_prng_cmds", O_RDONLY) = 3 open of the command file succeeded. > brk(0x000E6DB8) = 0 "malloc" in user land, i.e. sshd > brk(0x000E8DB8) = 0 "malloc" in user land, i.e. sshd > fstat64(3, 0xFFBEECD8)

> jeff at ntcor.com [SMTP:jeff at ntcor.com] wrote: > > I have a ssh enabled server and client machine (we'll call them "server" > and "client" respectively...) OK :-) > They both have proper RSA and DSA keys,using protocol version 2 works > fine between them. (so ssh itself and the network is working fine) OK. > However, I want to get something that

Hello ! I think a problem was introduced in openssh-2.3.0p1 which is still there in the latest openssh-2.5.2p1. I just noticed it before my vacation and could not send this mail earlier than today. The problem is: You can't use the Rhosts-RSA authentication based on the hosts.equiv file and the host keys. The only possible way to do rhosts-RSA authentication is to allow the usage of the

Hi ! Karsten Thygesen wrote: >>>>> "carl" == carl <carl at bl.echidna.id.au> writes: > carl> Marc, I'm seeing the same problem if I use the inbuilt entropy > carl> generator, but if I use SUNWski's /dev/random, it's fine. > carl> ssh also coredumps if I use the built in entropy generator if I > carl> run it in verbose mode.

> John Horne [SMTP:J.Horne at plymouth.ac.uk] wrote: > > Emanuel Borsboom <emanuel at heatdeath.org> wrote: >> Trying to install the portable OpenSSH on Solaris 2.6. Compiling from >> openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd >> starts fine. First connection from another system works. Child sshd is >> forked, but the parent dies

after compile (gcc 3.0.2) install and configure (SWAT) on tcpps02 the following test failed # /usr/local/samba/bin/smbclient -L TCPPS02 added interface ip=172.16.207.7 bcast=172.16.255.255 nmask=255.255.0.0 session request to TCPPS02 failed (Call timed out: server did not respond after 20000 milliseconds) session request to *SMBSERVER failed (Call timed out: server did not respond after

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I am trying to get libvirt with qemu-kvm to work on my machines running openSUSE 13.1 / Tumbleweed. My question is in regard to using qemu+ssh, which would be my preference, as I already have a working ssh-key authentication with SSH-Agent. I set the permissions of the manage-socket to 0770, added my user to the libvirt group and set

https://bugzilla.samba.org/show_bug.cgi?id=3009 Summary: build error on sinix: off64_t unknown Product: rsync Version: 2.6.5 Platform: Other OS/Version: other Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: bernhard.voelker@siemens.com

Gang, ???? I run several KVM host machines.? Due to updates, maintenance, and unexpected reboots sometime host machines are restarted.? I can easily envision a scenario where HostX needs some critical packages updated or is acting up.? I migrate guest0, guest1, guest2 etc. from HostX to HostY.? Then, in either a planned (i.e. scheduled maintenance) or unplanned (i.e. unplanned reboot) event

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27.03.2014 12:19 Johannes Kastl wrote: > Trying from another machine (say target hostname is HOSTX, > username testuser) with virsh -c qemu+ssh://testusers@HOSTX/system > always results in >>> error: failed to connect to the hypervisor error: internal >>> error: received hangup / error event on socket I just found out,

Hi Group, recently I upgraded to v 3.7.1p2 on Reliant Unix (former SINIX). With sser root everything works fine, but with a "normal" user the session terminates.. I put the logfile of the "sshd -dddd" at the end. What is wrong? regard Stephan --------------- debug2: read_server_config: filename /etc/sshd_config debug1: sshd version OpenSSH_3.7.1p2 debug1: private host key:

On 11.11.2016 19:17, Arkadiusz Mi?kiewicz wrote: > On Friday 11 of November 2016, Aki Tuomi wrote: > >> If you are interested in testing, please find patch attached that allows >> you to specify >> >> local_name *.foo.bar { >> } >> >> or >> >> local_name *.*.foo.bar { >> } >> >> so basically you can now use certificate

On Friday 11 of November 2016, Aki Tuomi wrote: > If you are interested in testing, please find patch attached that allows > you to specify > > local_name *.foo.bar { > } > > or > > local_name *.*.foo.bar { > } > > so basically you can now use certificate name matching rules for > local_name. It made most sense. Great! Seems to be working fine for my

On Friday 11 of November 2016, Aki Tuomi wrote: > On 11.11.2016 19:17, Arkadiusz Mi?kiewicz wrote: > > On Friday 11 of November 2016, Aki Tuomi wrote: > >> If you are interested in testing, please find patch attached that allows > >> you to specify > >> > >> local_name *.foo.bar { > >> } > >> > >> or > >> >

http://bugzilla.mindrot.org/show_bug.cgi?id=331 Summary: ssh w/o privilege separation does not work for non-root users Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: ssh AssignedTo: