Sounds like an RBAC problem - create a non-root user that can login over network with the necessary permissions to run disk maintenance (backup, etc)? Add ssh keys for the user. Put your local ssh keys in the .ssh directory over there.
Create a script in the user's directory to do what you need.
PS: you can use tar over the network to create local tarballs from your remote disk.
Hello there, just a quick question.....Can someone please explain the concept that enables you to establish a connection using the same userId
Thanx (1 Reply)
Hi,
I am facing problem while setting up ISAKMP between two hosts.
I can see only the Initiator messages but no responder messages in tcpdump. Does anyone know the cause of this behaviour?
FYI, here is the extracted information from tcpdump :
14:47:08.699113 IP 10.118.231.143.isakmp >... (0 Replies)
Hi everybody i need your help on this I have LAN which run Sun microsystem with solaris 7 OS on each of the servers. The LAN was working fine before an interruption of power supply which makes servers to operating as standalone servers. i.e none of the servers have access to one another. How do i... (2 Replies)
Hi All,
I need an automation script to check the connectivity between 2 UNIX servers.
Could anybody please help in this regards?
regards,
janardhan (1 Reply)
Hi, I am trying to use nomachine nx server and client. But somehow it doen't work. What happens is the following:
1.- Client starts up
2.- Client authenticates with Server
3.- The NoMachine window appears for 2-4 seconds
4.- The NoMachine window exists
Somehow a "closeEvent" is sent.... (3 Replies)
We have two servers A and B (both running Solaris 10) out of which one is application server and the other is database server. The two servers faced certain network issues and the two servers were temporarily disconnected.this happened around 5AM GMT monday.Can anyone suggest some log files or... (2 Replies)
HI I have made a connection with external server which is also UNIX. I was tryign connectivity with this by telnet which fails and ping i sshowing socket is alive and traceroute tells the asterisk astersik:traceroute to 153.88.182.28 (153.88.182.28), 30 hops max, 8080 byte packets
1 * * *
2 *... (1 Reply)
Hi All
I am having issues using ftp between a solaris 10 server to a HP-UX 11.31 server, but from the solaris server to the hp-ux I am able to ping. This is what I have done so far:
in the solaris server:
root@MPCRS01 # svcs -a | grep ftp
online Jul_26 svc:/network/ftp:default... (12 Replies)
ello,
i am new to the networking side.
I have a requirement to check the tcp network connectivity between server it's running on and the list of host's and ports combination.
please help me where i am going wrong.
my code:
#!/bin/bash
#read the file line by line
cd "$1"
cat... (17 Replies)
Discussion started by: sknovice
17 Replies
LEARN ABOUT XFREE86
ssh-keysign
ssh-keysign(1M)ssh-keysign(1M)NAME
ssh-keysign - ssh helper program for host-based authentication
SYNOPSIS
ssh-keysign
ssh-keysign is used by ssh(1) to access the local host keys and generate the digital signature required during host-based authentication
with SSH protocol version 2. This signature is of data that includes, among other items, the name of the client host and the name of the
client user.
ssh-keysign is disabled by default and can be enabled only in the global client configuration file /etc/ssh/ssh_config by setting Host-
basedAuthentication to yes.
ssh-keysign is not intended to be invoked by the user, but from ssh. See ssh(1) and sshd(1M) for more information about host-based authen-
tication.
/etc/ssh/ssh_config
Controls whether ssh-keysign is enabled.
/etc/ssh/ssh_host_dsa_key
/etc/ssh/ssh_host_rsa_key
These files contain the private parts of the host keys used to generate the digital signature. They should be owned by root, readable
only by root, and not accessible to others. Because they are readable only by root, ssh-keysign must be set-uid root if host-based
authentication is used.
ssh-keysign will not sign host-based authentication data under the following conditions:
o If the HostbasedAuthentication client configuration parameter is not set to yes in /etc/ssh/ssh_config. This setting cannot be overri-
den in users' ~/.ssh/ssh_config files.
o If the client hostname and username in /etc/ssh/ssh_config do not match the canonical hostname of the client where ssh-keysign is
invoked and the name of the user invoking ssh-keysign.
In spite of ssh-keysign's restrictions on the contents of the host-based authentication data, there remains the ability of users to use it
as an avenue for obtaining the client's private host keys. For this reason host-based authentication is turned off by default.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsshu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
ssh(1), sshd(1M), ssh_config(4), attributes(5)AUTHORS
Markus Friedl, markus@openbsd.org
HISTORY
ssh-keysign first appeared in Ox 3.2.
9 Jun 2004 ssh-keysign(1M)