Tag Archives: PEM

Linux

Problem using scp to transfer a file

Leave a comment

By jyoung

I am testing the following command to transfer a file from my server (AIX 5.2) to another server. I was able to generate the keys and sent them the public key.

Code:
scp -v -P 4030 /home/lawson/.ssh/jimtest.txt someuser@some.ftpsite.net:/Inbound/jimtest.txt > jimtest_out.txt 2>&1

Based on the output from the command it looks like it is authenticating correctly, but the file is not getting sent or they tell me they are not getting it. Can you take a look at the above command and let me know if it is not correct. I am currently doing this from the command line, but will script it when I get it working. Below is output from the comman execution.

Code:
Executing: program /usr/local/bin/ssh host some.ftpsite.net, user someuser, command scp -v -t /Inbound/jimtest.txt
OpenSSH_3.8p1, SSH protocols 1.5/2.0, OpenSSL 0.9.6l 04 Nov 2003
debug1: Reading configuration data /usr/local/etc/ssh_config
debug1: Connecting to some.ftpsite.net [0.0.0.0] port 4030.
debug1: Connection established.
debug1: identity file /home/lawson/.ssh/identity type -1
debug1: identity file /home/lawson/.ssh/id_rsa type 1
debug1: identity file /home/lawson/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version Maverick_SSHD
debug1: no match: Maverick_SSHD
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'some.ftpsite.net' is known and matches the RSA host key.
debug1: Found key in /home/lawson/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
Welcome to the Gateway Interchange SSH server.
debug1: Authentications that can continue: password,publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/lawson/.ssh/identity
debug1: Offering public key: /home/lawson/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending command: scp -v -t /Inbound/jimtest.txt
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: fd 2 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status -1
lost connection

Any thoughts. I want to determine if the problem is on my side or theirs. Thank you.

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

[SOLVED] Problem using scp to transfer a file

Leave a comment

By jyoung

I am testing the following command to transfer a file from my server (AIX 5.2) to another server. I was able to generate the keys and sent them the public key.

Code:
scp -v -P 4030 /home/lawson/.ssh/jimtest.txt someuser@some.ftpsite.net:/Inbound/jimtest.txt > jimtest_out.txt 2>&1

Based on the output from the command it looks like it is authenticating correctly, but the file is not getting sent or they tell me they are not getting it. Can you take a look at the above command and let me know if it is not correct. I am currently doing this from the command line, but will script it when I get it working. Below is output from the comman execution.

Code:
Executing: program /usr/local/bin/ssh host some.ftpsite.net, user someuser, command scp -v -t /Inbound/jimtest.txt
OpenSSH_3.8p1, SSH protocols 1.5/2.0, OpenSSL 0.9.6l 04 Nov 2003
debug1: Reading configuration data /usr/local/etc/ssh_config
debug1: Connecting to some.ftpsite.net [0.0.0.0] port 4030.
debug1: Connection established.
debug1: identity file /home/lawson/.ssh/identity type -1
debug1: identity file /home/lawson/.ssh/id_rsa type 1
debug1: identity file /home/lawson/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version Maverick_SSHD
debug1: no match: Maverick_SSHD
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'some.ftpsite.net' is known and matches the RSA host key.
debug1: Found key in /home/lawson/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
Welcome to the Gateway Interchange SSH server.
debug1: Authentications that can continue: password,publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/lawson/.ssh/identity
debug1: Offering public key: /home/lawson/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending command: scp -v -t /Inbound/jimtest.txt
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: fd 2 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status -1
lost connection

Any thoughts. I want to determine if the problem is on my side or theirs. Thank you.

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Konversation 1.5-rc1 (KDE Chat Application)

Leave a comment
Thumbnail

Konversation 1.5-rc1
(KDE Chat Application)
Konversation is a user-friendly Internet Relay Chat (IRC) client built on the KDE Platform.

— What’s new —

1.5-rc1:
Konversation 1.5-rc1 is the first test release for our next major release. The 1.5 development cycle has lead to significant new features in many areas of the application, from support for SASL and client certificate authentication on the protocol side, to all-new topic management UI, overhauled authentication UI, per-tab spell-checking language settings, user-configurable nick context menu entries and mouse spring-loading in the frontend and all-new versions of major bundled scripts. Improved Ignore, Watched Nicknames and Edit Paste functionality and behavior, performance improvements in some critical codepaths and many other bug fixes and minor UI touch-ups round things out.

1.4:
The dominant theme in Konversation v1.4 is improvements and feature additions to the user interface, particularly to text views, dialogs, (context) menus and input line commands. However, nearly all areas of the application have seen some amount of improvements in this release, as is to be expected given the relatively long relase cycle: Connection behavior, IRC protocol handling, scripting support, encryption support, user documentation – new features, polish and certainly also bug fixes are to be found in all of them. In summary, we hope you will enjoy the best Konversation yet.

— Essential links —

Konversation’s website: http://konversation.kde.org/
Wiki: http://userbase.kde.org/Konversation
Report bugs and wishes at: https://bugs.kde.org/enter_bug.cgi?product=konversation
Older releases: http://konversation.kde.org/wiki/Releases

changelog:
Changes from 1.4 to 1.5-rc1:
* The user interface for the Auto Identify settings in the Identities dialog has been extended by a combo box that allows choosing the type of authentification to be performed. Depending on the chosen type, different input fields are shown below the combo box.
* The server password-based authentification supported by some networks is now configurable in the Identities dialog as well, making it more discoverable and allowing to keep Auto Identify settings generally with the Identity rather than requiring going through the Edit Server dialog.
* SASL PLAIN authentification is now supported. To use, pick SASL as the Auto Identify type in the Identities dialog and fill in your account name and password.
* Standard NickServ authentification has been further improved. The command sent to to the service, previously hard-coded to “identify”, is now configurable, and the name of the service now defaults to “nickserv” in new identities (the previous default was an empty field).
* Added support for authenticating via a SSL Client Certificate in the form of a PEM file if Konversation is built against KDE Platform v4.8.3 or higher. Choosing this type of authentication in the Identities dialog forces SSL to be enabled for a connection, overriding any server settings.
* Added the ability to set a different spell-checking language for every tab, from the context menu of the input box. The chosen language setting is preserved across application restarts.
* The Topic tab …read more
Source: FULL ARTICLE at KDE Apps