Sponsored Content
Operating Systems Linux Red Hat Remote access computer system as a whole not just desktop with GUI Post 303030821 by ASGR on Saturday 16th of February 2019 01:11:51 PM
Old 02-16-2019
Thanks Bakunin.


I think ssh is definitely the way to go.


I would have liked to access my devices remotely with a GUI and
discovered that openssh-server does exactly this. Problem solved.



Also, I believe you can use RSA style crypto key pairs as a means
to log into the server. This setup is ideal. Thanks for help.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Need help to access/mount so to access folder/files on a Remote System using Linux OS

Hi I need to access files from a specific folder of a Linux system from an another Linux System Remotely. I know how to, Export a folder on One SCO System & can access the same by using Import via., NFS in the Sco Unix SVR4 System using the scoadmin utility. Also, I know to use mount -t ... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies

2. UNIX for Advanced & Expert Users

Starting GUI Desktop

I have installed Oracle 9 client on 32-bit machine for Linux Enterprise 2.4. After complete installation and testing the oracle client. After rebooting the system I was presented with a login prompt but the GUI desktop does not come. I tried startx but that did not work. What command would I use... (0 Replies)
Discussion started by: aliraza123
0 Replies

3. UNIX for Dummies Questions & Answers

how to access cd's etc from a non GUI Unix system

i need to know how i would go about accessing my floppy disks, cd's and flash drives on my command prompt unix system (1 Reply)
Discussion started by: carlvernon
1 Replies

4. UNIX for Dummies Questions & Answers

ssh to see remote desktop gui

Hey, how do I access the desktop gui for a remote fedora box? $ ssh user@ip $ xinit Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Thanks (1 Reply)
Discussion started by: JustinT
1 Replies

5. Shell Programming and Scripting

Access a remote computer using perl

Dear all, Where can i find documentation on how to access a remote computer using a perl script? I search to the internet but i can not find something straightforward to this issue. Which is the easiest way to do that? What i would like to do is to access a remote computer access a directory... (5 Replies)
Discussion started by: chriss_58
5 Replies

6. Solaris

Remote Access using GUI from one Solaris to another one

hi gyus, i'm trying to login trough GUI (using login screen, instead to login to locahost I login to remote host) from on Solaris 10 to another one. You know, I see the remote host in the host list, but It's not possible to login since the screen keeps black and after that get back to the former... (3 Replies)
Discussion started by: daninx
3 Replies

7. Debian

Launch remote gui apps in remote hosts

Hi, I've been looking for a way to execute a console program (is in windows but by now I accept the linux way) from a linux machine, but this program has to be opened in the remote side. Linux machine acts only as a "signaling" host. My program has to open the camera in the remote side, but only... (7 Replies)
Discussion started by: zauberberg
7 Replies

8. Shell Programming and Scripting

Triggering remote UNIX shell script from Remote desktop

I m trying to run a batch script in remote desktop which executes unix commands on the unix server...the problem is i wnt the output in HTML format.so in my batch script i m giving the cmd like ssh hostname path ksh HC_Report.ksh>out.html ...but it generates the HTML file in remote desktop .i... (2 Replies)
Discussion started by: navsan
2 Replies

9. Hardware

Which desktop computer is the better deal?

I wasn't sure where to post this. Please move this as is fitting. My 10yr old laptop's (Dell, Latitude E5530, 4G ram, 2.5Ghz x 2 CPU) spin drive has died (currently running TinyCore Linux on USB in ram). I would be running Linux, compiling the kernel, and programming in C++. I do not do... (0 Replies)
Discussion started by: bedtime
0 Replies

10. Hardware

Desktop computer is only turning on for a few seconds

My desktop computer is only turning on for a few seconds after that it turns off. I assumed it was the power supply so I bought another one. Last night I installed the power supply. It took awhile with me reseating everything and taking out the cmos battery to get the computer running. After that I... (4 Replies)
Discussion started by: cokedude
4 Replies
SSH-KEYCONVER(1)					    BSD General Commands Manual 					  SSH-KEYCONVER(1)

NAME
ssh-keyconvert -- convert ssh v1 keys and authorization files SYNOPSIS
ssh-keyconvert [-k] [-o output_file] identity_file ... ssh-keyconvert [-a] [-o output_file] authorization_file ... DESCRIPTION
ssh-keyconvert converts RSA public and private keys used for public key based user authentication with protocol version 1 to the format used with protocol version 2. When using RSA user authentication with SSH protocol version 1, the client uses the private key from $HOME/.ssh/identity to provide its iden- tity to the server. The server grants or denies access based on whether the public part of this key is listed in $HOME/.ssh/authorized_keys. SSH protocol version 2 supports both DSA and RSA keys, but the way RSA keys are stored are differently. On the client, the default file name is .ssh/id_rsa rather than .ssh/identity, and the file's format is different as well. On the server, the public porting of the key can still be stored in .ssh/authorized_keys, but the key notation has changed as well. Therefore, when switching from protocol version 1 to version 2, you either have to create a new identity key using ssh-keygen(1) and add that key to the server's authorized_keys file, or you need to con- vert your keys using ssh-keyconvert. By default, ssh-keyconvert will try to guess the type of file that is to be converted. If it fails to guess correctly, you can tell if what type of conversion to perform by specifying the -k option to convert the private key, or the -a option to convert an authorisation file. When converting your private keys stored in .ssh/identity, ssh-keyconvert will read the private key, prompting you for the pass phrase if the key is protected by a pass phrase. If the -o option is given, it will write the private key to the specified file, using version 2 syntax. If the key was protected by a pass phrase, it will use the same pass phrase to protect the new file. It will also write the public portion of the key to a second file, using the specified file name with ``.pub'' appended. If the -o option was not given, private and public key will be written to id_rsa and id_rsa.pub, respectively, relative to the directory of the input key file. If the destination file already exists, ssh-keyconvert will prompt the user for confirmation before overwriting the file, unless the -f option is given. When converting your authorized_keys file, ssh-keyconvert will ignore any keys in SSH version 2 format. Any public keys in version 1 format will be converted and appended to the output file using the new syntax. If the -o option is given, keys are appended to the specified file. If it is not given, ssh-keyconvert will append all keys to the input file. Note that ssh-keyconvert does not check for duplicate keys, so if you run it on .ssh/authorized_keys more several times, the converted keys will show up several times. OPTIONS
-k Convert private key file(s). The default is to guess the type of file that should be converted. -a Convert authorized_keys file(s). The default is to guess the type of file that should be converted. -o outfile Specify the name of the output file. When converting an authorization file, all public keys will be appended to this file. For pri- vate key conversion, the private and public components of the key will be stored in outfile and outfile.pub, respectively. Note that since every key must be stored in a separate file, you cannot use this option when you specify several input files. -f When converting a key file, and the output file already exists, ssh-keyconvert will ask the user whether to overwrite the file. Using this option forces overwriting. AUTHORS
OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, Theo de Raadt and Dug Song removed many bugs, re-added newer features and created OpenSSH. ssh-keyconvert was contributed by Olaf Kirch. SEE ALSO
ssh(1), ssh-add(1), ssh-agent(1), sshd(8) J. Galbraith and R. Thayer, SECSH Public Key File Format, draft-ietf-secsh-publickeyfile-01.txt, March 2001, work in progress material. BSD
February 2, 2002 BSD
All times are GMT -4. The time now is 02:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy