Sponsored Content
Special Forums Cybersecurity What's the difference between an SSH Client and an SSH Server? Post 53563 by norsk hedensk on Monday 19th of July 2004 03:24:58 PM
Old 07-19-2004
your question applies not only to SSH, but to every service built on the client/server model...ie almost all of them.

the server runs the service, the client connects to it.

your gonna have to search here, and on google for more info.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SSH client

How can I use ssh client with proxy support? If possible: with proxy chain support. :) (2 Replies)
Discussion started by: zylwyz
2 Replies

2. Solaris

Secure FTP Problem using Sun SSH on Client system F-Secure on Server system

I am using shell script to do secure ftp. I have done key file setup to do password less authentication. Following are the FTP Details: FTP Client has Sun SSH. FTP Server has F-Secure. I am using SCP Command to do secure copy files. When I am doing this, I am getting the foll error scp:... (2 Replies)
Discussion started by: ftpguy
2 Replies

3. UNIX for Advanced & Expert Users

difference between logging into unix through f-secure ssh client and telnet

hi, what is the difference between logging into unix through f-secure ssh client and telnet is there any more security check is involved can any one explain thanks in advance (1 Reply)
Discussion started by: trichyselva
1 Replies

4. UNIX for Dummies Questions & Answers

Is it possible for a server to be both a remote and client SSH host?

Hi, Not sure if this is possible, I have a server (SERVER1) that is currently set up as a remote SSH host. My client SSH host (SERVER2) is connecting to SERVER1 to scp a file with no password. I now have a need to set up a third server (SERVER3) as a remote SSH host and I need SERVER1 as a... (4 Replies)
Discussion started by: tatchel
4 Replies

5. Shell Programming and Scripting

Using ssh to add register key on ssh server

Hi, I want to use ssh to add a register key on remote ssh server. Since there are space characters in my register key string, it always failed. If there is no space characters in the string, it worked fine. The following is what I have tried. It seems that "ssh" command doesn't care about double... (9 Replies)
Discussion started by: leaftree
9 Replies

6. Solaris

SSH Client

Hi Gurus, I need an SSH client to connect to a Solaris server from windows and run a few scripts. I am able to put/pull files using "psftp" using below command: psftp -l <username> -pw <password> <hostname> -b <batchfile> However i am unable to find an equivalent for ssh. I tried... (3 Replies)
Discussion started by: Hari_Ganesh
3 Replies

7. Linux

What SSH Client do you Use?

Most of you probably use PuTTy, but I was wondering if there were any other good alternatives. So, what SSH client do you use? (2 Replies)
Discussion started by: erich76
2 Replies

8. IP Networking

Unable to SSH from Windows client to Ubuntu Server

I'm trying to setup a small home network environment as a pet project. These are physical machines nothing virtual. Any help or ideas is greatly appreciated. I can ping between both machines and I have Samba established and can read/write different shares. When I try to SSH from Windows 8.1... (10 Replies)
Discussion started by: lombardi4851
10 Replies

9. UNIX and Linux Applications

What is the difference between /etc/ssh/ and ~/.ssh?

Hi, I know the “/etc/ssh” directory is for the ssh daemon and the “~/.ssh” directory is for a particular user. Both directories contain private and public keys: (see the attachment) but what is the difference between those keys in both directories? I'm confused because the ones i use as a... (5 Replies)
Discussion started by: kavish11
5 Replies
nns_intro(n)						       Name service facility						      nns_intro(n)

__________________________________________________________________________________________________________________________________________________

NAME
nns_intro - Name service facility, introduction DESCRIPTION
nns (short for nano nameservice) is a facility built for the package comm, adding a simple name service to it. It is also built on top of comm, using it for the exchange of messages between the client and server parts. This name service facility has nothing to do with the Internet's Domain Name System, otherwise known as DNS. If the reader is looking for a package dealing with that please see either of the packages dns and resolv, both found in Tcllib too. Tcllib provides 2 applications and 4 packages which are working together and provide access to the facility at different levels. APPLICATIONS
The application nnsd provides a simple name server which can be run by anybody anywhere on their system, as they see fit. It is also an example on the use of the server-side package nameserv::server. Complementing this server is the nns client application. A possible, but no very sensible use would be to enter name/port bindings into a server from a shell script. Not sensible, as shell scripts normally do not provide a comm-based service. The only case for this to make some sense would be in a shell script wrapped around a Tcl script FOO which is using comm, to register the listening port used by FOO. However even there it would much more sensible to extend FOO to use the nameservice directly. And in regard on how to that nns can be used as both example and template. Beyond that it may also be useful to perform nameservice queries from shell scripts. The third application, nnslog is a stripped down form of the nns client application. It is reduced to perform a continuous search for all changes and logs all received events to stdout. Both clients use the nameserv::auto package to automatically hande the loss and restoration of the connection to the server. PACKAGES
The two main packages implementing the service are nameserv and nameserv::server, i.e. client and server. The latter has not much of an API, just enough to start, stop, and configure it. See the application nnsd on how to use it. The basic client, in package nameserv, provides the main API to manipulate and query the service. An example of its use is the application nns. The second client package, nameserv::auto is API compatible to the basic client, but provides the additional functionality that it will automatically restore data like bound names when the connection to the name service was lost and then reestablished. I.e. it automatically detects the loss of the server and re-enters the data when the server comes back. The package nameserv::common is of no interest to users. It is an internal package containing code and definitions common to the packages nameserv and nameserv::server. All packages use the uevent package for the reporting of special circumstances via events, and reserve the uevent-tag nameserv for their exclusive use. All their events will be posted to that tag. INTERNALS
The document Name service facility, client/server protocol specifies the protocol used by the packages nameserv and nameserv::server to talk to each other. It is of no interest to users of either the packages or applications. Developers wishing to modify and/or extend or to just understand the internals of the nameservice facility however are strongly advised to read it. BUGS, IDEAS, FEEDBACK This document, will undoubtedly contain bugs and other problems. Please report such in the category nameserv of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. Please also report any ideas for enhancements you may have. SEE ALSO
nameserv(n), nameserv::auto(n), nameserv::common(n), nameserv::protocol(n), nameserv::server(n), nnsd(n), nss(n) KEYWORDS
client, name service, server COPYRIGHT
Copyright (c) 2008 Andreas Kupries <andreas_kupries@users.sourceforge.net> nns 1.0 nns_intro(n)
All times are GMT -4. The time now is 04:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy