Displaying 20 results from an estimated 300 matches similar to: "Solaris 8: RSA_padding_check_PKCS1_type_1:block type is not 01"
2013 Jan 17
1
Fwd: Re: Inconsisten declaration of ssh_aes_ctr_iv()
Oops, I meant to CC the list on this.
--
Iain
----- Forwarded message from Iain Morgan <Iain.Morgan at nasa.gov> -----
Date: Thu, 17 Jan 2013 14:51:01 -0800
From: Iain Morgan <Iain.Morgan at nasa.gov>
To: Damien Miller <djm at mindrot.org>
Subject: Re: Inconsisten declaration of ssh_aes_ctr_iv()
On Wed, Jan 16, 2013 at 21:26:39 -0600, Damien Miller wrote:
> On Mon, 14 Jan
2007 Apr 12
3
zaptel/ssh interaction
I hope I don't get flamed the first time I post to a new list. I have
spent a couple of hours poking around without seeing anything like this.
The problem is, as soon as I load the Zaptel drivers (with a TDM-31B
card), ssh into or out of the server is broken. Trying to ssh in, I get:
RSA_public_decrypt failed: error:0407006A:rsa
routines:RSA_padding_check_PKCS1_type_1:block type is not 01
2001 Mar 26
2
Openssh-2.5.1p1 and Solaris 2.6 problem with ssh_rsa_verify
We recently upgraded from an older version of SSH to OpenSSH
2.5.1p1 (OpenSSH_2.5.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f)
and are having problems on just a few hosts in our environment. The
other 200 systems are working fine. Every once in a blue-moon it will
connect with version 2.
When I try to connect to or from one of these hosts using SSH2 I
get the following error (I have sshd -d
2001 Apr 27
0
key_verify failed for server_host_key from Solaris 2.7 to non-Solaris hosts
Hi,
I am using OpenSSH 2.5.2p2 on Solaris 2.7 (Ultra 10) with 64bit support and
have the following problem when connecting with the ssh2 protocol to
non-solaris OS:
On the client side, I do:
/local/work/lysis/bin/slogin -v -2 -p 2222 rs30
On the server side (AIX 4.3), the sshd runs as follows:
aix/sbin/sshd -p 2222 -d
Full output follows at the end of this mail.
The server is compiled with
2002 Apr 24
0
need help in ssh client: key exchange
Hello,
I have a problem with ssh client.
I have:
SSH-2.0-OpenSSH_2.3.1p1
When I try to connect to a sshd server (USING V2):
Remote protocol version 1.99, remote software version
OpenSSH_2.5.2p2
or
Remote protocol version 2.0, remote software version
OpenSSH_3.0.1p1
I get error (looking at codebase):
In sshconnect2.c:
ssh_dhgex_client(kex, host, hostaddr,
client_kexinit,
2007 Nov 12
0
inability to connect with netware OpenSSH 3.7.1 to FreeBSD 4.5p1
(I'm sorry - the securityfocus mailing list is dead
and there are no other SSH resources on the net)
Hello,
Client is (some netware installation) running:
Local version string SSH-2.0-OpenSSH_3.7.1p2
Server is plain old FreeBSD 6.2-RELEASE running:
OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1
When I attempt to connect from client (netware) to
server (freebsd) I see:
ssh
2003 Apr 18
0
openssh 3.5p1 problem with openssl 0.9.6i
you wrote:
> I am using openssh 3.5p1 and I am having problems using the protocol 2
> of ssh with openssl 0.9.6i
> It was working fine with openssl 0.9.6g.
> I am using binary packages downloaded fron SunFreeware and I did not
> changed any config file.
> Both the machines are running Solaris 8.
>
> <test1> /usr/local/bin> ssh -2 -v -v -v test2
> ...
> ...
2013 Jan 18
0
Inconsisten declaration of ssh_aes_ctr_iv() (fwd)
---------- Forwarded message ----------
Date: Fri, 18 Jan 2013 10:19:35 +1100 (EST)
From: Damien Miller <djm at mindrot.org>
To: Iain Morgan <Iain.Morgan at nasa.gov>
Subject: Re: Inconsisten declaration of ssh_aes_ctr_iv()
On Thu, 17 Jan 2013, Iain Morgan wrote:
> > Could you tell me the declaration of the function pointer do_cipher in
> > OpenSSL's evp.h on your
2002 Mar 27
2
Problem with ssh-keygen
Dear Developer,
I'm having problem running ssh_keygen on my solaris 7 box. Can you
please tell me as to why I'm getting this error as described below? I
don't have that problem with solaris 8 that runs SMCossh 3.0.2p1
Thanks in advance.
Louie
# /usr/local/bin/ssh-keygen
ld.so.1: /usr/local/bin/ssh-keygen: fatal: libcrypto.so.0.9.6: open
failed: No such file or directory
Killed
#
2002 Jun 26
0
Problem with interaction between commercial and openssh
Hello all,
Earlier this week we disabled protocol 1 upon our machines while
installing commercial ssh 3.2.0. Suddenly I discovered that the AIX
systems running Openssh were not able to connect. I upgraded to the newly
minted 3.4p1 and discovered the same problem.
My limited poking around has shown the following:
<16:59:38>atb at ursus:>ssh -vv atb at host
<snip>
debug1: bits
2008 Jul 08
1
SSH_RSA_MINIMUM_MODULUS_SIZE
Hi,
is there any chance to make SSH_RSA_MINIMUM_MODULUS_SIZE configurable?
I keep receiving these messages:
ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits
key_verify failed for server_host_key
And it's quite a hassle to recompile each time I need to use it (there
are still devices where you can't fix it easily).
Thanks
Michal
2013 Sep 24
9
[PATCH] curve25519-sha256@libssh.org key exchange proposal
Dear OpenSSH developers,
I've worked this week on an alternative key exchange mechanism, in
reaction to the whole NSA leaks and claims over cryptographic backdoors
and/or cracking advances. The key exchange is in my opinion the most
critical defense against passive eavesdropping attacks.
I believe Curve25519 from DJB can give users a secure alternative to
classical Diffie-Hellman (with fixed
2002 Sep 11
0
[Bug 394] New: SSH 2 MAC Error Caused By OpenSSH?
http://bugzilla.mindrot.org/show_bug.cgi?id=394
Summary: SSH 2 MAC Error Caused By OpenSSH?
Product: Portable OpenSSH
Version: -current
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P3
Component: ssh
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy:
2010 Sep 23
0
RSA_public_decrypt failed: error:8106A072:lib(129):func(106):reason(114)
Dear Group,
I'm having a problem connecting Solaris 10 Server to a Redhat Enterprise
Linux 5.4 and meanwhile pretty clueless on that issue. Hopefully I get
at least a hint, from your group, where to look at.
key-length is 2048, permissions are correct on .ssh-directory and the
files itself, keygen is done manually. On the Linuxserver we're using
openssh-4.3p2-36.el5, on Solaris the
2014 Apr 18
2
[Bug 2232] New: curve25519-sha256@libssh.org Signature Failures When 'ssh' Used with Dropbear, libssh Servers
https://bugzilla.mindrot.org/show_bug.cgi?id=2232
Bug ID: 2232
Summary: curve25519-sha256 at libssh.org Signature Failures When
'ssh' Used with Dropbear, libssh Servers
Product: Portable OpenSSH
Version: 6.6p1
Hardware: All
OS: All
Status: NEW
Severity: major
2008 Jan 16
4
x509 patch for SSH
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi guys,
been trying the x509 patch for ssh from Roumen, it works great.
However, I can't figure out couple of things, and been trying to solve
it for couple of days already.
I'am using OpenSSH_4.7p1-hpn12v19, OpenSSL 0.9.8g
with 6.1 version of your patch.
The serverside hostkey is configured correctly, to present x509v3-sign-rsa
dynowork
2014 Oct 18
10
[Bug 2297] New: EDD25519 Signature verification failed on Solaris
https://bugzilla.mindrot.org/show_bug.cgi?id=2297
Bug ID: 2297
Summary: EDD25519 Signature verification failed on Solaris
Product: Portable OpenSSH
Version: 6.7p1
Hardware: amd64
OS: Solaris
Status: NEW
Severity: major
Priority: P5
Component: sshd
Assignee: unassigned-bugs at
2019 Feb 14
2
Migrating to Samba 4.9.4 AD, kinit administrator -> kinit: Cannot contact any KDC for realm...
On 2019/02/14 22:19, Rowland Penny via samba wrote:
> On Thu, 14 Feb 2019 21:43:43 +0200
> Ashley via samba <samba at lists.samba.org> wrote:
>
>> On 2019/02/14 21:12, Rowland Penny via samba wrote:
>>> On Thu, 14 Feb 2019 19:14:19 +0200
>>> Ashley via samba <samba at lists.samba.org> wrote:
>>>
>>>> Hi there
>>>>
2019 Feb 14
0
Migrating to Samba 4.9.4 AD, kinit administrator -> kinit: Cannot contact any KDC for realm...
On Thu, 14 Feb 2019 19:14:19 +0200
Ashley via samba <samba at lists.samba.org> wrote:
> Hi there
>
> I have migrated from an older version of Samba DC to Samba 4.9.4 AD.
> Running Centos 7. One server with everything on... (AD and file
> server) Bind 9.9.4
>
> Built from source.
> Followed directions in the wiki.
> All seems to go fine, but when I startup
2019 Feb 14
0
Migrating to Samba 4.9.4 AD, kinit administrator -> kinit: Cannot contact any KDC for realm...
On Thu, 14 Feb 2019 21:43:43 +0200
Ashley via samba <samba at lists.samba.org> wrote:
>
> On 2019/02/14 21:12, Rowland Penny via samba wrote:
> > On Thu, 14 Feb 2019 19:14:19 +0200
> > Ashley via samba <samba at lists.samba.org> wrote:
> >
> >> Hi there
> >>
> >> I have migrated from an older version of Samba DC to Samba 4.9.4
>