(OLD) (ARCHIVED) Puppy Linux Discussion Forum

drj · Joined: 26 Jun 2005 Posts: 41

an openssh deamon I made for myself, in case someone on the same boat as I was, here comes the package

notes:
1. includes openssh deamon and its configuration file
2. add user sshd
3. modify hosts.allow and hosts.deny
4. menu entries for all three WMs
5. registers to pupget manager
6. need either set password for root or a new user with password to remotely connect.

rarsa · Posted: Sat 09 Jul 2005, 21:46 Post subject:

Woow, you beat me to the finish line.

Actually you beat me to the start line.

That was going to be my next .pup after I finish the vncserver script and acompanying DotPup (I am translating the perl script into a simple bash script, I'm 90% there already)

Well, one less thing to worry about.

Thanks

flamesage · Joined: 01 Jul 2005 Posts: 214

How do I set this up again?
Theres no execution file, nor can I access it from console.

rarsa · Posted: Mon 18 Jul 2005, 13:10 Post subject:

Here is what I did:

- Install the DotPup Package by clicking on the downloaded file from Rox
- If you are booting from CD, you need to create a /var/empty folder everytime

Flash · Posted: Mon 18 Jul 2005, 15:51 Post subject:

Thank you, rarsa, that was excellent. One question: if you put nothing after "passwd," will it work (without entering a password?)

rarsa · Posted: Mon 18 Jul 2005, 21:06 Post subject:

dvw86 · Joined: 04 May 2005 Posts: 636 Location: Washington State

Great program, but I have a question. While I can connect to Puppy from other Puppy machines and my iBook, I can not get X11 to forward application windows. I get the error "Can't open display". I tried editing the file sshd_config and changed the line "#X11Forwarding no" to "#X11Forwarding yes" I then went to edit the ssh_config file but could not find it. Any ideas?

drj · Joined: 26 Jun 2005 Posts: 41

you might be trying to use X appl and DISPLAY has not be set. try following

1. before you connect, disable X auth
$ xhost +

2. $ ssh -Y remotehost

dvw86 · Joined: 04 May 2005 Posts: 636 Location: Washington State

What is the -Y flag? I do not see it listed in the help, and when I type "ssh -Y root@myip" I get "illegal option --Y" and then a list of all the options.

CapeCodCDog · Joined: 19 Nov 2005 Posts: 3 Location: Cape Cod, MA

I want to be able to "tunnel" x applications through ssh. I am having trouble getting the DISPLAY variable to be set automatically when I log in through ssh to the openssh (sshd). I do have the
X11Forwarding yes
in the sshd_config file.
The DISPLAY variable is not set at all (doesn't exist).
Here's a verbose log of my session:
OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.6.1p2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'xxx.xxx.xxx.xxx' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
root@xxx.xxx.xxx.xxx's password:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: channel 0: request pty-req
debug1: No xauth program.
Warning: No xauth data; using fake authentication data for X11 forwarding.
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: channel 0: request x11-req
debug1: channel 0: request shell
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug1: Remote: No xauth program; cannot forward with spoofing.

Is this problem do to XAUTHORITY?
from the openssh.org FAQ
NOTE: For users of Linux Mandrake 7.2, Mandrake modifies the XAUTHORITY environment variable in /etc/skel/.bashrc, and thus any bash user's home directory. This variable is set by OpenSSH and for either of the above options to work, you need to comment out the line:
# export XAUTHORITY=$HOME/.Xauthority

Thanks in advance,

CapeCodCDog

rarsa · Posted: Wed 07 Dec 2005, 00:12 Post subject:

The Xvesa video driver in Puppy cannot forward X.

You can forward X from a client into the puppy X server, but not the other way around.

If you want to do that you will need to use the xserver dotpup provided by MU. Search the forum.

CapeCodCDog · Joined: 19 Nov 2005 Posts: 3 Location: Cape Cod, MA

Thanks ...

I am able on a local network to manually set DISPLAY, i.e.:
export DISPLAY=192.168.0.12
and then start X apps. But this won't work if I'm coming in from outside through a router that is port forwarding, etc.

I was able to ssh in from the "outside" into a system running SuSE and the DISPLAY variable was set. I suppose I can try installing the other xserver (it will be on a "live-CD boot machine" so if I have too many problems it will be easy to start from scratch. Thanks again!

ostkaka · Joined: 21 Feb 2007 Posts: 3

When i try to run the sshd deamon I get this:
OpenSSL version mismatch. Built against 90704f, you have 90802f

what can I do to solve this?

rarsa · Posted: Thu 22 Feb 2007, 18:38 Post subject: Re: OpenSSL version mismatch

llevet · Joined: 02 Mar 2007 Posts: 3 Location: Paris, France

Hi rarsa,

I have the same issu.
So, could you compile sshd for puppy 2.14 (libssl 90802f), and post it on the forum ?
It will be cool !

Thank's !
Laughing

Ludo.