Sponsored Content
Full Discussion: SSH connect problem
Top Forums UNIX for Advanced & Expert Users SSH connect problem Post 302566855 by Powerponken on Friday 21st of October 2011 10:01:53 AM
Old 10-21-2011
SSH connect problem

Hi,

I know that I'm a little off the right forum but it seems like there is more experience and knowledge among Unix/Linux users than among Windows users in this case. I have seen many similar explanations on how to set up the public keys in Unix but nothing that I've tried of the Windows tips have worked - maybe there is some problem in my environment. Maybe there is someone here that is expert on both Unix and Windows in this case.

I have some problems regarding the use of SSH(and also being a newbie in the SSH world). I have an application that uses SSH but when I want to use public key authentication. The server is a Win2003 server with F-Secure SSH server 5.3. I'm logged in as administrator and the administrator have started the F-secure server.

When trying to log in on the server I get "no more authentication methods available" and that is quite easy to understand why I get - I have created a keypair in the application but I have no idea where to put the public key on the server. As I understand it is to be put in .ssh-folder but where is that supposed to be?
I have found many similar descriptions on how to put the .pub file on a Unix/Linux computer but when it comes to Windows there isn't much to find.

When checking the F-secure server configuration it says that user key directory is %D\.ssh but I don't know what %D is supposed to be. The authorization file is called authorization but I haven't found any such file in the computer. I have tried to create and put the created key inside it and moving it around to different locations but without success.

Can anyone tell me where to put my public key and hopefully get it to work?

Regards,
Kalle
 

10 More Discussions You Might Find Interesting

1. AIX

Connect from Windows Using SSH

Hi Everybody, I have 2 Servers (AIX 4.3), recently I installed SSH in both servers successfuly. I can connect from one server to another using SSH. My problem is when I tried to connect from Windows workstation to one of these servers the connection timed out. I'm using PUTTY to connect to the... (12 Replies)
Discussion started by: aldowsary
12 Replies

2. UNIX for Dummies Questions & Answers

connect to server using ssh

hi, i have script that connects to a unix server. however, i want to add condition that if it cannot connects in 10 attemps, it will send email to me. while -a ${COUNT} -lt 10] ./connect to server. if status <> 0 then email to me. fi Thanks a lot. (0 Replies)
Discussion started by: tungaw2004
0 Replies

3. Shell Programming and Scripting

SSH not able to connect - Need help

Hi, I am trying to connect to server using SSH command - ssh -l <username>@<server> 22 But it just hangs there.. Any suggestions to connect via SSH will be of great help! (2 Replies)
Discussion started by: Sathy153
2 Replies

4. AIX

cannot connect with ssh

Hi, I have created a new user as below: useradd -g staff -s /usr/bin/ksh test2 passwd test2 <type in new password> <type in new password> and I could not login via ssh with this username while I can do it with another username. Can anyone tell anything missing? Thanks! Victor (4 Replies)
Discussion started by: victorcheung
4 Replies

5. UNIX for Dummies Questions & Answers

Connect using ssh

Dear users I have a question about connecting to remote servers using terminal I can connect to one server by ssh username@domain_of_first_server.com and after logging into the above i have to connect to one more server ssh name_of_second_server bascically to be able to connect to the... (5 Replies)
Discussion started by: kevincobain2000
5 Replies

6. HP-UX

Unable to connect SSH from HP-UX

Hi, I'm trying to connect from an HP-UX with SSH2 client(ssh2 3.1.2 on hppa1.1-hp-hpux11.00) to an SSH2 server on a VxWorks system. The SSH connection is failing with the below connection logs: > /usr/local/bin/ssh2 -v -l testuser 10.10.10.10 debug: Ssh2/ssh2.c:1391: Using file... (4 Replies)
Discussion started by: ysafi
4 Replies

7. Solaris

ssh problem - hangs and then wont connect

Got a Solaris 10 server with two interfaces - 10.0.110.233 and 10.0.111.233. I can ssh to 10.0.110.233 with no problems. But after a certain amount of time it just hangs. Nothing. Then if I try to ssh to 10.0.110.233 again - times out. But I can still ssh to 10.0.111.233. And I can still ping... (1 Reply)
Discussion started by: psychocandy
1 Replies

8. HP-UX

SSH slow at connect

Hi experts, We are getting slow ssh session connections at HP-UX 11.31 servers. We have set the parameters that maybe will affect , and commented at other theads at config file sshd_config : UseDNS no X11Forwarding yes X11DisplayOffset 10 X11UseLocalhost no GSSAPIAuthentication no. ... (7 Replies)
Discussion started by: SapBasisSystem
7 Replies

9. Shell Programming and Scripting

How to connect DB2 using SSH?

How to connect db2 IBM on AIX using SSH - SecureCRT ? Please help me. (3 Replies)
Discussion started by: meomeo87
3 Replies

10. Shell Programming and Scripting

SSH HELP how to connect auto?

hi, i have some servers on my network. i need to connect to them auto from my work station sith SSH. i need to write a script thet connects to the server with USERNAME and PASSWORD automticly. and on each server to kill process. in my sciprt i want to put all list the IP of my... (1 Reply)
Discussion started by: zigizag
1 Replies
SMBPASSWD(5)						   File Formats and Conventions 					      SMBPASSWD(5)

NAME
smbpasswd - The Samba encrypted password file SYNOPSIS
smbpasswd DESCRIPTION
This tool is part of the samba(7) suite. smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several different formats in the past. FILE FORMAT
The format of the smbpasswd file used by Samba 2.2 is very similar to the familiar Unix passwd(5) file. It is an ASCII file containing one line for each user. Each field within each line is separated from the next by a colon. Any entry beginning with '#' is ignored. The smbpasswd file contains the following information for each user: name This is the user name. It must be a name that already exists in the standard UNIX passwd file. uid This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user. Lanman Password Hash This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as disabled and the user will not be able to log onto the Samba server. WARNING !! Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access. NT Password Hash This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it. This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access. Account Flags This section contains flags that describe the attributes of the users account. This field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters: o U - This means this is a "User" account, i.e. an ordinary user. o N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the null passwords parameter is set in the smb.conf(5) config file. o D - This means the account is disabled and no SMB/CIFS logins will be allowed for this user. o X - This means the password does not expire. o W - This means this account is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC. Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. For further information regarding the flags that are supported please refer to the man page for the pdbedit command. Last Change Time This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made. All other colon separated fields are ignored at this time. VERSION
This man page is correct for version 3 of the Samba suite. SEE ALSO
smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm. AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. Samba 4.0 06/17/2014 SMBPASSWD(5)
All times are GMT -4. The time now is 03:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy