02-22-2016
and following the same logic...
how did you generate key?
as in specifically what command?
10 More Discussions You Might Find Interesting
1. Solaris
I am currently setting up rdiff-backup to use ssh to connect and remotely backup and retrieve data. I am doing so by creating rsa keys for each server and copying the relevant key to the /.ssh folder on the relevant server.
All seems to work well when severs running solaris 8 with ssh 3.6.1 are... (6 Replies)
Discussion started by: falklandtim
6 Replies
2. Solaris
Hi,
I am running a script from a client machine X which does "SSH" to around 100 other machines in a farm and invokes a local script on each of those machines. Local script localscript.sh on each of those 100 target machines, does some machine specific function like fetch the specific machine's... (1 Reply)
Discussion started by: waavman
1 Replies
3. Solaris
Hi,
I m new to Sun Solaris.
I've only changed the PermitRootLogin from no to yes, so that I can login as root from Window vista by using Putty.exe. Then I can create new users and change password.
Except the above configuration, i have do nothing to my SSH server.
Am I need to generate... (5 Replies)
Discussion started by: stacychiam
5 Replies
4. Shell Programming and Scripting
Hi folks,
What I want to do is to check if there is an instance of running vlc on a remote server, then kill it, and start it again. The code I came up with is:
#!/bin/bash
expectFcn() {
expect -c "
set timeout -1
spawn ssh \"$1@$2\" \"$4\"
match_max 100000
expect {
-re... (2 Replies)
Discussion started by: dukevn
2 Replies
5. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
6. UNIX and Linux Applications
I have a UniVerse database running on a Red Hat EL3 server. If I am on the server console my software can call xpdf giving the name of a target file and it displays very nicely on the console. I have not been able to figure out how to get the display to happen on any of the Windows XP workstations.... (5 Replies)
Discussion started by: dale kelley
5 Replies
7. Solaris
Hi, It's a Solaris 10 zone. I can ssh to other systems without problems, but can not ssh to it (output attached). I don't think there is a firewall here. /etc/ipf/ipf.conf contains nothing.
What could be the problem cause? Please help. Thank you in advance!
sshclient$ ssh -v thiserver... (1 Reply)
Discussion started by: aixlover
1 Replies
8. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
9. Shell Programming and Scripting
Hi All,
I want to copy /.ssh/OM.pub file from source to destination.
Here source IP address, username and password is always fixed.
Whereas destination server IP address, password always gets changed.
From destination server :-
I am trying to write a script in which it should log in to... (3 Replies)
Discussion started by: madhur.baharani
3 Replies
10. Shell Programming and Scripting
hi Gurus,
Have been struggling with this for a while
I have 2 servers , lets say local A and remote B, I need to use both as a part of a pipeline. The folder structure is shared between the two, so I can access the same files and folders from both A and B.
When I try to ssh into B from A,... (15 Replies)
Discussion started by: senhia83
15 Replies
LEARN ABOUT REDHAT
rndc.conf
RNDC.CONF(5) RNDC.CONF(5)
NAME
rndc.conf - rndc configuration file
SYNOPSIS
rndc.conf
DESCRIPTION
rndc.conf is the configuration file for rndc, the BIND 9 name server control utility. This file has a similar structure and syntax to
named.conf. Statements are enclosed in braces and terminated with a semi-colon. Clauses in the statements are also semi-colon terminated.
The usual comment styles are supported:
C style: /* */
C++ style: // to end of line
Unix style: # to end of line
rndc.conf is much simpler than named.conf. The file uses three statements: an options statement, a server statement and a key statement.
The options statement contains three clauses. The default-server clause is followed by the name or address of a name server. This host
will be used when no name server is given as an argument to rndc. The default-key clause is followed by the name of a key which is identi-
fied by a key statement. If no keyid is provided on the rndc command line, and no key clause is found in a matching server statement, this
default key will be used to authenticate the server's commands and responses. The default-port clause is followed by the port to connect to
on the remote name server. If no port option is provided on the rndc command line, and no port clause is found in a matching server state-
ment, this default port will be used to connect.
After the server keyword, the server statement includes a string which is the hostname or address for a name server. The statement has two
possible clauses: key and port. The key name must match the name of a key statement in the file. The port number specifies the port to con-
nect to.
The key statement begins with an identifying string, the name of the key. The statement has two clauses. algorithm identifies the encryp-
tion algorithm for rndc to use; currently only HMAC-MD5 is supported. This is followed by a secret clause which contains the base-64 encod-
ing of the algorithm's encryption key. The base-64 string is enclosed in double quotes.
There are two common ways to generate the base-64 string for the secret. The BIND 9 program rndc-confgen can be used to generate a random
key, or the mmencode program, also known as mimencode, can be used to generate a base-64 string from known input. mmencode does not ship
with BIND 9 but is available on many systems. See the EXAMPLE section for sample command lines for each.
EXAMPLE
options {
default-server localhost;
default-key samplekey;
};
server localhost {
key samplekey;
};
key samplekey {
algorithm hmac-md5;
secret "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};
In the above example, rndc will by default use the server at localhost (127.0.0.1) and the key called samplekey. Commands to the localhost
server will use the samplekey key, which must also be defined in the server's configuration file with the same name and secret. The key
statement indicates that samplekey uses the HMAC-MD5 algorithm and its secret clause contains the base-64 encoding of the HMAC-MD5 secret
enclosed in double quotes.
To generate a random secret with rndc-confgen:
rndc-confgen
A complete rndc.conf file, including the randomly generated key, will be written to the standard output. Commented out key and controls
statements for named.conf are also printed.
To generate a base-64 secret with mmencode:
echo "known plaintext for a secret" | mmencode
NAME SERVER CONFIGURATION
The name server must be configured to accept rndc connections and to recognize the key specified in the rndc.conf file, using the controls
statement in named.conf. See the sections on the controls statement in the BIND 9 Administrator Reference Manual for details.
SEE ALSO
rndc(8), rndc-confgen(8), mmencode(1), BIND 9 Administrator Reference Manual.
AUTHOR
Internet Software Consortium
BIND9 June 30, 2000 RNDC.CONF(5)