Displaying 20 results from an estimated 2000 matches similar to: "hmac-ripemd160 not in PROTOCOL"
2016 Feb 03
1
Python hashlib and ripemd160
okay it appears there are no suspect patent issues with ripemd160 so
either they just didn't include it for some other reason or the issue is
elsewhere.
On 02/03/2016 03:00 AM, Eero Volotinen wrote:
> well, how about compiling instance to another directory like
> /opt/python-alternative?
>
> usually works like ./configure --prefix=/opt/python-alternative and then
> other
2016 Feb 03
2
Python hashlib and ripemd160
Hi - I think the patent monster has struck again.
rmd = hashlib.new('ripemd160',binascii.unhexlify(someString)).hexdigest()
That fails - ValueError: unsupported hash type
From some googling, it appears that the supported hash types are from
OpenSSL and that means the OpenSSL in CentOS doesn't support ripemd160.
I've worked around other stuff missing from CentOS OpenSSL by
2016 Feb 03
0
Python hashlib and ripemd160
well, how about compiling instance to another directory like
/opt/python-alternative?
usually works like ./configure --prefix=/opt/python-alternative and then
other normal stuff..
--
Eero
2016-02-03 12:52 GMT+02:00 Alice Wonder <alice at domblogger.net>:
> Hi - I think the patent monster has struck again.
>
> rmd =
2005 Oct 26
2
openssh 4.2p1 zlib compression broken for old clients
Hello OpenSSH developers,
openssh 4.2p1 breaks old openssh clients up to 3.4p1 when they try to use compression:
# ssh-3.4p1 -C remote-host-with-4.2p1 pwd
no matching comp found: client zlib server none,zlib at openssh.com
option "-vv" shows
...
debug2: kex_parse_kexinit: zlib
...
debug2: kex_parse_kexinit: none,zlib at openssh.com
...
debug2: mac_init: found hmac-md5
no
2020 Feb 06
3
Call for testing: OpenSSH 8.2
On 2020-02-05 at 20:39 -0500, Phil Pennock wrote:
> On 2020-02-06 at 10:29 +1100, Damien Miller wrote:
> > OpenSSH 8.2p1 is almost ready for release, so we would appreciate testing
> > on as many platforms and systems as possible. This is a feature release.
>
> > * The RFC8332 RSA SHA-2 signature algorithms rsa-sha2-256/512. These
> This actually affects me:
2009 Mar 04
4
Again: Next libvorbis release?
Hi there,
I maintain the libvorbis, libogg and vorbis-tool package for Fink <http://finkproject.org/
>. Recently I had time to wonder about those again. In particular,
since I was informed libsndfile self-tests fails with 1.2.0, but not
with a version dubbed 1.2.1rc1 somebody sent me. Also trunk seems to
contain security fixes.
In https://trac.xiph.org/browser/trunk/vorbis/CHANGES
2012 Jul 25
2
libogg 1.3.0 ?
Hi,
today I learned that libogg 1.3.0 had been released in August 2011. Curiously, there seems to have been no announcement mail here, and it is not being mentioned on <http://www.xiph.org/press/> either. Is that on purpose? Is there some other channel I could subscribe to in order to learn about updates? Freecode.com doesn't have up-to-date info either (though I just submitted a 1.3.0
2015 Apr 22
2
non-openssl build fixes
The attached patches fixes and cleans up the build when configured
with --without-openssl.
Summary:
* Fix KEX_SERVER_ENCRYPT macro in myproposal.h
* Fix unresolved symbols in ssh-keygen.c
* Isolate openssl code and extend WITH_OPENSSL wrappers around it
* Make ed25519 default key type in ssh-keygen when configured --without-openssl
-------------- next part --------------
A non-text attachment was
2016 Jan 19
2
[Bug 2527] New: default algorithms mismatch between man pages and myproposal.h
https://bugzilla.mindrot.org/show_bug.cgi?id=2527
Bug ID: 2527
Summary: default algorithms mismatch between man pages and
myproposal.h
Product: Portable OpenSSH
Version: 7.1p1
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5
Component: Documentation
2017 Jan 20
2
^C doesnt work on ssh session
Thanks Darren, will check on your response.
I am attaching sshd, ssh logs with debug flags. Please see if it gives any
hint:
when I press ^C in ssh session, no log gets printed in both server/client
side.
Best Regards,
On Wed, Jan 18, 2017 at 3:09 AM, Darren Tucker <dtucker at zip.com.au> wrote:
> On Wed, Jan 18, 2017 at 5:10 AM, Sudarshan Soma <sudarshan12s at gmail.com>
2015 Sep 14
15
[Bug 2466] New: Cipher defines from opensslconf.h
https://bugzilla.mindrot.org/show_bug.cgi?id=2466
Bug ID: 2466
Summary: Cipher defines from opensslconf.h
Product: Portable OpenSSH
Version: 7.1p1
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Miscellaneous
Assignee: unassigned-bugs at mindrot.org
2013 Dec 11
4
OpenSSH 6.3p1 Smartcard-Support
Hi there,
has anybody managed to get the eToken Pro Anywhere work with SSH? I'm using the latest SafeNetAuthentication drivers available for Ubuntu 64bit (8.3) and everything is working just fine except for ssh. I can use the eToken for logging in, openvpn, rdestkop, etc. but it seems ssh does not recognize the device properly. The command "ssh -I /usr/lib/libeToken.so.8 user at
2016 Oct 24
2
SSH fail to login due to hang over after authenticated.
Hi OpenSSH,
I encountered that SSH will hang over after I input the password.
Could you help show me how to resolve this problem? Thanks for your
help.
Please find the ssh debug info and my ssh version as below.
$ ssh -vvv user1 at remote_host
OpenSSH_6.9p1, LibreSSL 2.1.8
debug1: Reading configuration data /Users/user1/.ssh/config
debug1: /Users/user1/.ssh/config line 36: Applying options for
2014 Jan 17
3
New git repository
Hi,
When the Subversion mirror of portable OpenSSH fell into disrepair, I
promised to replace it with a git mirror. Well, I finally got around to
it - you can clone git://anongit.mindrot.org/openssh.git and browse at
https://anongit.mindrot.org/openssh.git/
The repository is also mirrored to github at
https://github.com/openssh/openssh-portable
These are very new and it's entirely possible
2017 Jul 05
2
Administrivia: new list server
Hi,
I've migrated the list, bugzilla and anongit servers. With one exception
(below), you shouldn't see any difference. If you do then I've messed up
and I'd appreciate your letting me know.
The list server now runs on different MTA that turned out to be
subtly incompatible with the TMDA mail filtering software that
provides the ability for non-list members to post to
2016 Nov 08
4
one host only: ssh_dispatch_run_fatal
Darren Tucker <dtucker at zip.com.au> writes:
> On Tue, Nov 8, 2016 at 1:02 PM, Harry Putnam <reader at newsguy.com> wrote:
> [...]
>> gv harry> ssh -vv 2x
>>
>> OpenSSH_7.3p1-hpn14v11, OpenSSL 1.0.2j 26 Sep 2016
>
> this is a third-party modified version of OpenSSH. Can you reproduce
> the problem with a stock OpenSSH from the source from
2003 Jun 10
2
SecurID authentication for 3.6.1p2 with privsep
Hello all,
I have made SecurID authentication for OpenSSH 3.6.1p2.
This patch was totaly rewritten, so please test it before use.
Kbd-int authentication is now integrated into challenge response
auth.
Privsep is now fully suported.
PS: What do you think of selective access to the individual
authentications, similar to AllowGroups/DenyGroups or maybe
AllowUsers/DenyUsers ?
Vaclav Tomec
2013 Jul 20
7
Failure to Launch (was override -q option)
Attached is the very verbose ssh output. Just to be perverse, this time two
nodes lost connectivity. The only thing I see is lines saying that the two
connections are lost, although being honest I have no idea what everything
else means. For reference, 8 ssh cinnections were being made at the same
time for a 8x8mpi task.
N.B., since the OS I am using does not have rsh, I am currently using the
2017 Jan 27
4
Notes on openssh configuration
Hello list,
To my astonishment the openssh versions on both C6 and C7 will by
default negotiate an MD5 HMAC.
C6 client, C7 server:
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
C7 client & server:
debug2: mac_setup: setup hmac-md5-etm at openssh.com
debug1:
2023 Feb 24
1
[PATCH 0/1] ZSTD compression support for OpenSSH
I added ZSTD support to OpenSSH roughly three years ago and I've been
playing with it ever since.
The nice part is that ZSTD achieves reasonable compression (like zlib)
but consumes little CPU so it is unlikely that compression becomes the
bottle neck of a transfer. The compression overhead (CPU) is negligible
even when uncompressed data is tunneled over the SSH connection (SOCKS
proxy, port