11-21-2011
Apologies for late reply, I was away from work for a week.
I have trashed the user and recreated it on the RH box. Same result though.
@vgersh99, I have modified permissions as well.
I did it step by step as you did it, Scott. I'm going to keep playing around with this, I need to get it right.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I'm wondering if anyone has a step-by-step instruction set for setting up ssh keys? I've gone through many of the manuals online (most seem to be from the same source) and it's a little bit unclear when the documentation is talking about the server versus the client machine. I'm missing... (1 Reply)
Discussion started by: sysera
1 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone,
i wanted to generate ssh keys so that i can include the public key in the remote sever, so that for subsequent logins, i can do away with the keying in of the password. I consulted the man ssh-keygen man pages. "..Normally each user wishing to use SSH with RSA or DSA... (1 Reply)
Discussion started by: new2ss
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have ssh keys (id_rsa and id_rsa.pub). However, every once in a while, someone deletes these keys.
here's what i want to do :
1. on my server, it will ssh user@password into the target machine(where ssh keys are located).
2. check the date/filesize of id_rsa, id_rsa.pub).
3.... (0 Replies)
Discussion started by: tungaw2004
0 Replies
4. Shell Programming and Scripting
Hi All,
I am having knowledge on some basics of ssh and wanted to know what are the public keys and how can we create and implement it in connecting server.
Please provide the information for the above, it would be helpful for me.
Thanks,
Ravindra (1 Reply)
Discussion started by: ravi3cha
1 Replies
5. Red Hat
Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured
server:
/etc/hosts.allow:
all : all
all :all@all
setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies
6. Solaris
Hello,
I could use some help with my ssh keys and agent.
This is the issue. I have 2 different UNIX systems at work. One is the normal Solaris servers with my uid being the same throughout all the servers. I now have a different system for my desktop. A contractor came in and installed some SUN... (0 Replies)
Discussion started by: bitlord
0 Replies
7. Shell Programming and Scripting
Hi,
I am trying to complete my bash script in order to find which SSH servers on LAN are still active with the ssh keys, but i am frozen at this step:
#!/bin/bash
# LAN SSH KEYS DISCOVERY SCRIPT
</etc/passwd \
grep /bin/bash |
cut -d: -f6 |
sudo xargs -i -- sh -c '
&& cat... (11 Replies)
Discussion started by: syrius
11 Replies
LEARN ABOUT DEBIAN
sasl_server_step
sasl_server_step(3) SASL man pages sasl_server_step(3)
NAME
sasl_server_step - Perform a step in the authentication negotiation
SYNOPSIS
#include <sasl/sasl.h>
int sasl_server_step(sasl_conn_t *conn,
const char *clientin,
unsigned clientinlen,
const char ** serverout,
unsigned * serveroutlen);
DESCRIPTION
sasl_server_step() performs a step in the authentication negotiation. It returns SASL_OK if the whole negotiation is successful and
SASL_CONTINUE if this step is ok but at least one more step is needed.
conn is the SASL connection context
clientin is the data given by the client (decoded if the protocol encodes requests sent over the wire) clientinlen is the length of cli-
entin
serverout and serveroutlen are set by the library and should be sent to the client.
RETURN VALUE
sasl_server_step returns an integer which corresponds to one of the SASL error codes. SASL_CONTINUE indicates success and that there are
more steps needed in the authentication. SASL_OK indicates that the authentication is complete. All other return codes indicate errors and
should either be handled or the authentication session should be quit.
CONFORMING TO
RFC 4422
SEE ALSO
sasl(3), sasl_errors(3), sasl_server_init(3), sasl_server_new(3), sasl_server_start(3)
SASL
10 July 2001 sasl_server_step(3)