Jake,
For non technical users you can use ssh as a CA, you can create to
each user a public key inside a USB Pendrive and them configure their
ssh clients (like a portable putty, and so) with that certificate (key).
This way they can authenticate to your server.
---
Felipe Martins
Security Analyst
Skype: martins.felipe
URL: http://www.felipemartins.info/
E-mail: martins.felipe.security@xxxxxxxxx
On 19/01/2011 15:49, guy@xxxxxxxxx wrote:
Thanks for all advises.
I actually don't need a full ssh implementation. The thing a wanted was a simple password-authentification for non-technical users without support for rsa-keys, remote execution etc.
But it sounds to complicated for a side-project...
Problem solved. Not quite the solution I hoped for but anyway...
regards,
jake
On Jan 17, 2011, at 8:39 PM, Felipe Martins wrote:
When you try to connect to a SSH Server it exchanges a session key, you would have to give that to the server before authentication.
Like Salva said, it's far more complicated than that.
Best Regards
---
Felipe Martins
Security Analyst
Skype: martins.felipe
URL: http://www.felipemartins.info/
E-mail: martins.felipe.security@xxxxxxxxx
On 17/01/2011 15:43, Salvador Fandino wrote:
----- Original Message ----
From: "guy@xxxxxxxxx"<guy@xxxxxxxxx>
To: secureshell@xxxxxxxxxxxxxxxxx
Sent: Sat, January 15, 2011 9:19:15 PM
Subject: simulate connection with netcat
Hello,
my long-term intention is to write a cross-platform GUI-authpf-client
without using libssh or libssh2. Before I get into that I'd like to simulate
the ssh-connection/authentication via netcat.
I took a look at the RFCs but don't get it working.
% nc 127.0.0.1 22
SSH-2.0-OpenSSH_5.2
SSH-2.0-OpenSSH_5.2<-- entered by me
... a lot of text ...
What do I enter now to authenticate?
My attempts resulted in "Packet corrupt".
SSH uses a binary protocol. Getting authenticated is far more complex than
writting something at your keyboard by hand.
You can find pointers to the related RFCs here:
http://en.wikipedia.org/wiki/Secure_Shell
- Salva
