similar to: How to enable SHA1 passwords after migration from OpenSUSE?

https://bugzilla.mindrot.org/show_bug.cgi?id=3208 Bug ID: 3208 Summary: ssh-keygen man page: sha1 fingerprint with "-E sha1" is supported Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component:

I just updated my ruby from 1.8.2 to the Windows Installer 184-16 RC1, and now when I try to start Webrick I get the following: c:/program files/dev/ruby/lib/ruby/site_ruby/1.8/rubygems/security.rb:18: uninitialized constant OpenSSL::Digest::SHA1 (NameError) from c:/program files/dev/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:397 from c:/program

When I try to push my app to Heroku I get this error: OCA@OCA-PC /c/rails/oca (master) $ git push heroku master Enter passphrase for key ''/c/Users/OCA/.ssh/id_rsa'': Counting objects: 913, done. Delta compression using up to 2 threads. Compressing objects: 100% (797/797), done. Read from remote host heroku.com: Connection reset by peer fatal: sha1 file

https://bugzilla.mindrot.org/show_bug.cgi?id=1314 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #1 from Damien Miller <djm at

https://bugzilla.mindrot.org/show_bug.cgi?id=2291 Bug ID: 2291 Summary: ssh -Q kex lists diffie-hellman-group1-sha1 twice Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component: sftp-server Assignee:

Got a problem with one workstation. What I'm seeing, from a yum update (saw it with make whatis first): <snip> Running rpm_check_debug error: rpmdbNextIterator: skipping h# 1211 hdr SHA1: BAD, not hex <repeated many times> <snip> ERROR with rpm_check_debug vs depsolve: libicui18n.so.36 is needed by boost-1.33.1-10.el5_7.3.i386 libicuuc.so.36 is needed by

Hi everyone, I have a php script that put all the people from a ldap(Openldap) base to Samba4 so I need to use the same password. I'm using userpassword in samba to store the passwords sha1 but I don't understand what is happening. My user is not logging on the system. Do I need to enable anything in samba4 ? My script: public function gerarSenhaPadraoTextoPlano($strSenha) { $senha

On 2020-03-17 00:03:03 [+0100], Dimitrios Apostolou via rsync wrote: > On Thursday, February 20, 2020 10:34:53 PM CET, Sebastian Andrzej Siewior > via rsync wrote: > > > > I'm still not sure if rsync requires a cryptographic hash _or_ if a > > strong hash like xxHash64 would be just fine for the job. > > I'm fairly sure the hash should *not* be easy to

In http://www.aidanf.net/rails_user_authentication_tutorial there is a string called require ''digest/sha1'' in the model. What does it do? Everything else is well explained besides that. -- Posted via http://www.ruby-forum.com/.

On 2020-02-20 20:06:39 [+0100], Markus Ueberall wrote: > On 2020-02-09 23:19, Sebastian Andrzej Siewior wrote: > > [...] > > My primar motivation to use SHA1 for checksumming (by default) instead > > of MD5 is not the additional security bits but performance. On a decent > > x86 box the SHA1 performance is almost the same as MD5's but with > > acceleration it

https://bugzilla.mindrot.org/show_bug.cgi?id=3753 Bug ID: 3753 Summary: ssh-keygen and ssh-keyscan prints SHA1 SSHFP digest by default Product: Portable OpenSSH Version: 9.9p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

That doesn't seem to be the case. See https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r4.pdf (5.6.1 Comparable Algorithm Strengths) On Fri, Feb 15, 2019 at 8:28 AM Darren Tucker <dtucker at dtucker.net> wrote: > > On Fri, 15 Feb 2019 at 16:00, Yegor Ievlev <koops1997 at gmail.com> wrote: > > I don't think there is any point to generate so

Hello, I have problem with authentication. I'm using SHA1 passwords stored in MySQL. >From debug: Info: auth-worker(default): sql(test at mail, IP): query: SELECT password FROM vmail WHERE mail = 'test at mail' Info: auth-worker(default): sql(test at mail ,IP): Password mismatch Info: auth-worker(default): sql(test at mail ,IP): SHA1(dupadupa) !=

Can we disable diffie-hellman-group14-sha1 too? On Thu, Feb 14, 2019 at 10:23 PM Mark D. Baushke <mdb at juniper.net> wrote: > > Hi John, > > The short answer is YES. > > Jon DeVree <nuxi at vault24.org> writes: > > > I ask because the removal of diffie-hellman-group-exchange-sha1 happened > > accidently in 7.8 due to a mistake in a change to

Hello, I have a problem. When I do 'make' it gives the following error: gcc -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecot-auth auth-cache.o au th-client-connection.o auth-master-connection.o auth-module.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o

I'll give those a look and make change accordingly. On 9/11/2018 9:26 PM, Aki Tuomi wrote: > You know we have rpm packages for 2.3.2.1 available at > https://repo.dovecot.org if you are in a hurry? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch at whitehorsetc.com> > Date: 12/09/2018 00:35

I ask because the removal of diffie-hellman-group-exchange-sha1 happened accidently in 7.8 due to a mistake in a change to readconf.c. I noticed this and filed a bug about it along with a patch to fix readconf.c to use KEX_CLIENT_* like it used to: https://github.com/openssh/openssh-portable/commit/1b9dd4aa https://bugzilla.mindrot.org/show_bug.cgi?id=2967 Its clear the removal was unintentional

Hi. I'm having a problem with hashing passwords for use in the menu. If I specify plain passwords in my config it works file: Example: MENU MASTER PASSWD 1234567890 MENU PASSWD test123 However if I hash a password using the sha1pass script the resulting hashes don't work. MENU MASTER PASSWD $4$9qj4qv8g$HQ6Jl6TVrpign78XeofX2OLmfJo$ MENU PASSWD test123

e.g. can we make it throw warnings etc. rsa-sha2-256 and rsa-sha2-512 are fine, they use PSS. On Sun, Jan 20, 2019 at 1:55 AM Yegor Ievlev <koops1997 at gmail.com> wrote: > > Also can we do anything with ssh-rsa? It uses both SHA-1 and > deprecated PKCS#1 padding. If it's used to sign certificates, there's > no additional protection of SHA-2 hashing before SHA-1

On Wed, 5 Apr 2017, Jakub Jelen wrote: > Disabling SHA-1 for signatures sounds like a good idea these days (and was the > main reason why the extension created if I read it right [1]). > This leaves me confused if the use case without SHA1 was missed from the draft > or it was left as an implementation detail, that was not implemented in > OpenSSH. The reasons we didn't