can't open display : (on Linux rlogin to SGI) - SGI

This is a discussion on can't open display : (on Linux rlogin to SGI) - SGI ; Hello, When I try to open a GUI (using rsh) on SGI while on Linux, I am told : can't open display. I did a "xhost SGI_computer" before I went to Linux. The /etc/hosts file has an entry for the ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 24

Thread: can't open display : (on Linux rlogin to SGI)

  1. can't open display : (on Linux rlogin to SGI)

    Hello,


    When I try to open a GUI (using rsh) on SGI while on Linux, I
    am told :

    can't open display.

    I did a "xhost SGI_computer" before I went to Linux.

    The /etc/hosts file has an entry for the SGI.

    And, the .rhosts file on SGI has an entry for the Linux computer.

    What can I do to open the GUI?


    Thank you,
    Christopher Lusardi


  2. Re: can't open display : (on Linux rlogin to SGI)

    Le Thu, 28 Apr 2005 10:21:31 -0700, clusardi2k a écrit*:

    >
    > What can I do to open the GUI?


    Use "ssh -X" instead of rlogin/rsh. rlogin/rssh shouldn't be used anymore,
    never. And "ssh -X" would setup the X forwarding automatically for you.

    --
    Il y a toujours un bug de plus.
    Loi de Lubarsky.


  3. Re: can't open display : (on Linux rlogin to SGI)

    In article , Emmanuel Florac wrote:
    > Le Thu, 28 Apr 2005 10:21:31 -0700, clusardi2k a écrit*:
    >
    >>
    >> What can I do to open the GUI?

    >
    > Use "ssh -X" instead of rlogin/rsh. rlogin/rssh shouldn't be used anymore,
    > never. And "ssh -X" would setup the X forwarding automatically for you.


    Once again, there is nothing wrong with rlogin/rsh in a trusted, secure
    network... Never say never

    Kevin

    --
    Unix Guy Consulting, LLC
    Unix and Linux Automation, Shell, Perl and CGI scripting
    http://www.unix-guy.com

  4. Re: can't open display : (on Linux rlogin to SGI)

    I forgot to add that I do not want to enter a password by using ssh -X
    -l

    If you can, please, explain to me in a step by step method of how to
    use secure shell without
    entering a password. (I bet one cent that I probably woun't get it to
    work!)

    Thank you,
    Christopher Lusardi


  5. Re: can't open display : (on Linux rlogin to SGI)

    Hi,

    wrote:

    > I forgot to add that I do not want to enter a password by using ssh -X
    > -l


    You can use SSH with public key authentication and without a passphrase.

    > If you can, please, explain to me in a step by step method of how to use
    > secure shell without entering a password.


    There are a lot of ressource available on thet that subject, google
    shows things like or
    . Have a look at it.


    Regards,

    Dominik.

  6. Re: can't open display : (on Linux rlogin to SGI)

    It still asks me for a password. Here is what I did. You tell me what
    I did wrong?

    (1) On SGI and Linux type:
    ssh-keygen -t rsa
    (2) (Both accepting the defaults and entering a "paraphase" met with
    the same exact results!)
    (3) I now have 3 files on the SGI system. They are

    id_rsa
    id_rsa.pub
    known_hosts
    (4)I now have 2 files on the Linux system. They are

    id_rsa
    id_rsa.pub
    (5)I take the id_rsa.pub file on SGI and put it on Linux, but I rename
    the file to ~user/.ssh/authroized_keys.
    (6)I should be done and ready to use it, right.
    (7)I type
    ssh user@linux_box date
    (8)It tells me
    Warning: the RSA host key for 'linux_box' differs from the key for IP
    address '...'
    Offending key for IP is /usr/people/clusardi/.ssh/known_hosts:5
    Matching host key in /usr/people/clusardi/.ssh/known_hosts:8
    Are you sure you want to continue connecting (yes/no)? yes
    password ########

    (9)Note: The remote account is in directory /home/clusardi/.

    Does SGI big endian and Linux little endian have anything to do with
    it?

    Thanks,
    Christopher Lusardi


  7. Re: can't open display : (on Linux rlogin to SGI)

    It still asks me for a password. Here is what I did. You tell me what
    I did wrong?


    (1) On SGI and Linux type:
    ssh-keygen -t rsa
    (2) (Both accepting the defaults and entering a "paraphase" met with
    the same exact results!)
    (3) I now have 3 files on the SGI system. They are
    id_rsa
    id_rsa.pub
    known_hosts
    (4)I now have 2 files on the Linux system. They are
    id_rsa
    id_rsa.pub
    (5)I take the id_rsa.pub file on SGI and put it on Linux, but I rename
    the file to ~user/.ssh/authroized_keys.
    (6)I should be done and ready to use it, right.
    (7)I type
    ssh user@linux_box date
    (8)It tells me
    Warning: the RSA host key for 'linux_box' differs from the key for IP
    address '...'
    Offending key for IP is /usr/people/clusardi/.ssh/know*n_hosts:5
    Matching host key in /usr/people/clusardi/.ssh/know*n_hosts:8
    Are you sure you want to continue connecting (yes/no)? yes
    password ########

    (9)Notes: The remote account is in directory /home/clusardi/. And,
    there is no known_hosts file any where on the Linux computer.

    Does SGI big endian and Linux little endian have anything to do with
    it?

    I tried pasting and copying (via shared drive) the key over to Linux. I
    compared the files with vi and diff. In vi, I did a set list to compare
    control chararacters. The files appear to be the same.

    Thanks,
    Christopher Lusardi


  8. Re: can't open display : (on Linux rlogin to SGI)

    Hi,

    wrote:

    > (2) (Both accepting the defaults and entering a "paraphase" met with
    > the same exact results!)


    No, you don't use a passphrase. Just hit , when you are asked
    for it during key generation.

    > (3) I now have 3 files on the SGI system. They are
    > id_rsa
    > id_rsa.pub
    > known_hosts
    > (4)I now have 2 files on the Linux system. They are
    > id_rsa
    > id_rsa.pub


    You only need to create one pair of keys, if you just want to connect
    from your Linux box to the SGI.

    > (7)I type
    > ssh user@linux_box date


    So you want to connect from your SGI? If you created new machine keys,
    you might have to clean up your '~/.ssh/known_hosts'.

    > (8)It tells me
    > Warning: the RSA host key for 'linux_box' differs from the key for IP
    > address '...'
    > Offending key for IP is /usr/people/clusardi/.ssh/known_hosts:5
    > Matching host key in /usr/people/clusardi/.ssh/known_hosts:8


    .... see above.

    > Are you sure you want to continue connecting (yes/no)? yes
    > password ########


    Is that your login or your SSH passphrase? If it's the latter one, you
    need to create a new pair of keys without a passphrase.

    > (9)Notes: The remote account is in directory /home/clusardi/. And,
    > there is no known_hosts file any where on the Linux computer.


    You get one, if you login from your Linux box to another machine.

    > Does SGI big endian and Linux little endian have anything to do with
    > it?


    No.

    > I tried pasting and copying (via shared drive) the key over to Linux. I
    > compared the files with vi and diff. In vi, I did a set list to compare
    > control chararacters. The files appear to be the same.


    You can also use 'scp', as SSH is already working.


    Regards,

    Dominik.

  9. Re: can't open display : (on Linux rlogin to SGI)

    In article <1114796567.594875.168860@f14g2000cwb.googlegroups. com>,
    clusardi2k@aol.com wrote:

    : (5)I take the id rsa.pub file on SGI and put it on Linux, but I rename
    : the file to ~user/.ssh/authroized keys.

    Double-check the permissions of the .ssh folder, its contents, your home
    directory, and all directories above it. If SSH finds that the directories are
    group or world writeable it'll ignore the keys and force you to enter your
    password.

    This is so someone else can't drop their key into your authorized_keys file and
    ssh into the system as you.


    Cheers - Tony 'Nicoya' Mantler

    --
    Tony 'Nicoya' Mantler -- Master of Code-fu -- nicoya@ubb.ca
    -- http://nicoya.feline.pp.se/ -- http://www.ubb.ca/ --

  10. Re: can't open display : (on Linux rlogin to SGI)

    >From: Tony 'Nicoya' Mantler - Find messages by this
    author
    >Date: Fri, 29 Apr 2005 23:42:41 GMT
    >Local: Fri,Apr 29 2005 4:42 pm
    >Subject: Re: can't open display : (on Linux rlogin to SGI)


    >Double-check the permissions of the .ssh folder, its contents, your

    home
    >directory, and all directories above it. If SSH finds that the

    directories are
    >group or world writeable it'll ignore the keys and force you to enter

    your
    >password.


    This worked for me, many thanks.

    Christopher Lusardi

    This is so someone else can't drop their key into your authorized_keys
    file and
    ssh into the system as you.

    Cheers - Tony 'Nicoya' Mantler
    --
    Tony 'Nicoya' Mantler -- Master of Code-fu -- nic...@ubb.ca
    -- http://nicoya.feline.pp.se/ -- http://www.ubb.ca/ --


  11. Re: can't open display : (on Linux rlogin to SGI)

    clusard...@aol.com May 2, 5:36 am show options

    Newsgroups: comp.unix.questions, comp.sys.sgi.misc
    From: clusard...@aol.com - Find messages by this author
    Date: 2 May 2005 05:36:15 -0700
    Local: Mon,May 2 2005 5:36 am
    Subject: Re: can't open display : (on Linux rlogin to SGI)
    Reply | Reply to Author | Forward | Print | Individual Message | Show
    original | Remove | Report Abuse



    >From: Tony 'Nicoya' Mantler - Find messages by this

    author
    >Date: Fri, 29 Apr 2005 23:42:41 GMT
    >Local: Fri,Apr 29 2005 4:42 pm
    >Subject: Re: can't open display : (on Linux rlogin to SGI)
    >Double-check the permissions of the .ssh folder, its contents, your

    home
    >directory, and all directories above it. If SSH finds that the

    directories are
    >group or world writeable it'll ignore the keys and force you to enter

    your
    >password.


    This worked for me, only one-way.

    On Onyx it worked:

    ssh clusardi@linux_box date
    ....

    But, going the other way it didn't appear to work.

    On Linux it failed:

    ssh clusardi@onyx date
    ssh: connect to host onyx port 22 : Connection refused

    Christopher Lusardi

    >This is so someone else can't drop their key into your authorized_keys


    >file and
    >ssh into the system as you.
    >Cheers - Tony 'Nicoya' Mantler



  12. Re: can't open display : (on Linux rlogin to SGI)


    Tony 'Nicoya' Mantler wrote:
    > In article <1114796567.594875.168860@f14g2000cwb.googlegroups. com>,
    > clusardi2k@aol.com wrote:
    >
    > : (5)I take the id rsa.pub file on SGI and put it on Linux, but I

    rename
    > : the file to ~user/.ssh/authroized keys.
    >
    > Double-check the permissions of the .ssh folder, its contents, your

    home
    > directory, and all directories above it. If SSH finds that the

    directories are
    > group or world writeable it'll ignore the keys and force you to enter

    your
    > password.
    >
    > This is so someone else can't drop their key into your

    authorized_keys file and
    > ssh into the system as you.
    >
    >
    > Cheers - Tony 'Nicoya' Mantler
    >


    This worked for me, only one-way.

    On Onyx it worked:

    ssh clusardi@linux_box date
    ....

    But, going the other way it didn't appear to work.

    On Linux it failed:

    ssh clusardi@onyx date
    ssh: connect to host onyx port 22 : Connection refused

    Christopher Lusardi


  13. Re: can't open display : (on Linux rlogin to SGI)

    Hi,

    wrote:

    > This worked for me, only one-way.
    >
    > [...]
    >
    > ssh clusardi@onyx date
    > ssh: connect to host onyx port 22 : Connection refused


    That probably isn't a problem with your certificates, it looks like some
    kind of firewall, non-working portforwarding or sshd not running. You
    might want to check that ... .


    Regards,

    Dominik.

  14. Re: can't open display : (on Linux rlogin to SGI)


    Dominik Schlütter wrote:
    > Hi,
    >
    > wrote:
    >
    > > This worked for me, only one-way.
    > >
    > > [...]
    > >
    > > ssh clusardi@onyx date
    > > ssh: connect to host onyx port 22 : Connection refused

    >
    > That probably isn't a problem with your certificates, it looks like

    some
    > kind of firewall, non-working portforwarding or sshd not running. You
    > might want to check that ... .


    I used chkconfig to turn the SGI and Linux options on, but I still
    get the same error message:

    SGI before:

    fw_sshd off

    SGI after

    fw_ssh on

    -----------

    Linux before:
    ssh 0ff 1ff 2n 3n 4n 5n 6ff

    Linux after:
    ssh 0n 1n 2n 3n 4n 5n 6n

    Christopher Lusardi


  15. Re: can't open display : (on Linux rlogin to SGI)

    A little more information about my problem follows.

    ssh -v clusardi@onyx date
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for *
    debug1: Rhosts Authentication disabled, originating port will not be
    trusted
    debug1: Connecting to onyx [...] port 22
    debug1: connect to address ... port: Connection refused
    ssh: connect to host onyx port 22: Connection refused

    Note: I received a similar error with telnet.

    telnet onyx 22
    telnet: Unable to connect to remote host: Connection refused

    Christopher Lusardi


  16. Re: can't open display : (on Linux rlogin to SGI)

    In article <1115040483.094437.11340@l41g2000cwc.googlegroups.c om>,
    clusardi2k@aol.com wrote:

    : ssh: connect to host onyx port 22 : Connection refused

    sshd obviously isn't running on your Onyx. Please review the steps you used when
    installing ssh on your Onyx, you most likely missed configuring and starting the
    sshd daemon, and probably also missed generating a set of host keys.

    These steps are not automatic, sadly.


    Cheers - Tony 'Nicoya' Mantler

    --
    Tony 'Nicoya' Mantler -- Master of Code-fu -- nicoya@ubb.ca
    -- http://nicoya.feline.pp.se/ -- http://www.ubb.ca/ --

  17. Re: can't open display : (on Linux rlogin to SGI)

    Tony 'Nicoya' Mantler wrote:
    > In article <1115040483.094437.11340@l41g2000cwc.googlegroups.c om>,
    > clusardi2k@aol.com wrote:
    >
    > : ssh: connect to host onyx port 22 : Connection refused
    >
    > sshd obviously isn't running on your Onyx. Please review the steps

    you used when
    > installing ssh on your Onyx, you most likely missed configuring and

    starting the
    > sshd daemon, and probably also missed generating a set of host keys.
    >
    > These steps are not automatic, sadly.


    I've never started a daemon before. How do I start sshd on SGI,
    properly?

    Please be descriptive in your step by step directions. (As I'm about as
    novice as one can be without being ignorant! I don't want to wait
    months to get it done.)

    Thank you,
    Christopher Lusardi


  18. Re: can't open display : (on Linux rlogin to SGI)

    In comp.sys.sgi.misc clusardi2k@aol.com wrote:

    [....]
    > I've never started a daemon before. How do I start sshd on SGI,
    > properly?


    Hm, edit file /etc/config/sshd and change the 'no' in there to 'yes'? Or
    am I completely wrog. Do not forget to check the config files in
    directory /etc/openssh/ - of course you have to install the ssh package
    first, if not already done.

    Toni
    (xp&fup2cssm)
    --
    I am root. If you see me laughing you better have a backup.

  19. Re: can't open display : (on Linux rlogin to SGI)

    clusardi2k@aol.com wrote:

    > Tony 'Nicoya' Mantler wrote:
    >> In article <1115040483.094437.11340@l41g2000cwc.googlegroups.c om>,
    >> clusardi2k@aol.com wrote:
    >>
    >> : ssh: connect to host onyx port 22 : Connection refused
    >>
    >> sshd obviously isn't running on your Onyx. Please review the steps

    > you used when
    >> installing ssh on your Onyx, you most likely missed configuring and

    > starting the
    >> sshd daemon, and probably also missed generating a set of host keys.
    >>
    >> These steps are not automatic, sadly.

    >
    > I've never started a daemon before. How do I start sshd on SGI,
    > properly?
    >
    > Please be descriptive in your step by step directions. (As I'm about as
    > novice as one can be without being ignorant! I don't want to wait
    > months to get it done.)
    >
    > Thank you,
    > Christopher Lusardi


    If you don't want to/can't get sshd running on the Onyx, and you're working
    over a relatively secure network, rsh/rlogin is fine.

    Some Linux distros. have removed the ability from the X server to accept
    network connections, instead making it only listen on a UNIX domain socket
    (probably /tmp/.X11-unix/X0). Ssh can be used to tunnel X and open the UNIX
    domain socket locally, so it all works relatively seamlessly.

    To get XFree86 to listen on the network will depend on which distro you are
    using. For RH distros you need to edit the file /etc/X11/gdm/gdm.conf and
    change the line "DisallowTCP=true" to "DisallowTCP=false". Then restart X.

    However, you should realize that now your traffic (including X) will be sent
    over the network unencrypted - everything you type into a remote terminal
    shell, remote dialog box etc. can be captured. Also, your X display itself
    may be compromised, and clients can potentially hijack all events including
    keystrokes. The chance of this happening is fairly minimal, but it's
    definitely greater than zero. Whatever you do don't use a plain 'xhost +',
    even 'xhost +host' is quite dangerous as any user logged into 'host' can
    connect to your X server; use xauth instead.

    --
    Nigel Wade, System Administrator, Space Plasma Physics Group,
    University of Leicester, Leicester, LE1 7RH, UK
    E-mail : nmw@ion.le.ac.uk
    Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555

  20. Re: can't open display : (on Linux rlogin to SGI)

    Once again you are correct in your analysis of the problem, hooray!

    This is what I did:

    1) Added another /etc/passwd nobody entry

    Originally had only,
    nobody:x:6003:6001riginal nobody uid:/dev/null/:/dev/null

    Now is,
    nobody:x:6001:6001riginal nobody uid:/dev/null/:/dev/null
    nobody:x:6003:6001riginal nobody uid:/dev/null/:/dev/null

    2) Started ssh demon with

    /etc/init.d/fw_sshd start

    Thank you,
    Christopher Lusardi


+ Reply to Thread
Page 1 of 2 1 2 LastLast