similar to: [Bug 3494] New: ssh-keygen -r cannot disable SHA-1 digest

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:

https://bugzilla.mindrot.org/show_bug.cgi?id=1972 Daniel Black <daniel.black at ovee.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.black at ovee.com.au Keywords| |openbsd, patch --- Comment #2

Hi, I was sure I sent this to openssh at openssh.com, but cannot find that email now in my Sent mailbox, so I am sending it to the developers list. I took a liberty and wrote an I-D with accompanying patch (with contributions from Ondrej Caletka) to support ECDSA in the SSHFP DNS resource record. The I-D is here: https://tools.ietf.org/html/draft-os-ietf-sshfp-ecdsa-sha2 (and the source XML

hi folks: it looks like ssh-keygen -r can''t export SSHFP records for ECDSA keys: 0 dkg@pip:/tmp/cdtemp.oiRYAS$ ssh-keygen -f foobar -t ecdsa -q -P '''' 0 dkg@pip:/tmp/cdtemp.oiRYAS$ ssh-keygen -r foobar -f foobar.pub export_dns_rr: unsupported algorithm 0 dkg@pip:/tmp/cdtemp.oiRYAS$ the first number in my prompt is the return code of the last command; note that

https://bugzilla.mindrot.org/show_bug.cgi?id=3533 Bug ID: 3533 Summary: tracking bug for openssh-9.3 Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Keywords: meta Severity: enhancement Priority: P5 Component: Miscellaneous Assignee:

Any plans for using Atom with rails. I saw the "Typo" project is using MoveableType, Blogger, ... but not Atom. It seems Atom is not part of ActionWebService. Has anyone done any work with Atom and Rails ? Thanks for your answers, Gaspard

https://bugzilla.mindrot.org/show_bug.cgi?id=1972 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with release

https://bugzilla.mindrot.org/show_bug.cgi?id=3546 Bug ID: 3546 Summary: Use SHA2 in ssh-keygen key verification Product: Portable OpenSSH Version: 8.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh-keygen Assignee: unassigned-bugs at

Say your app responds to : store/show/3 and caching is enable at the store controller level. A route says : map.connect ''store/:action/:id'', :controller => ''store'' All the following urls will be processed and cached (the cache filling with ''page not found'' messages) ! store/foo/bar store/show/090934298234897342

Hello, everyone! I was wondering if somebody has some insight on this issue. [h]A little background:[/h] I work for a midsize electronic manufacturing company with 2 people in IT dept - a network admin and a developer (me). We''ve been using rails to migrate from an old dBase and VB based system to build internal company IntrAnet that does things like label printing, invetory control,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, My name is Olivier Gaspard, and I work for the CHC Belgium (IT department of differents Hospitals). So, let's me introduce the situation: for the moment, the firm works with Win NT for the users profiles, and Samba 3.0 on Unix platform for the "files sharing". Resuming : Every users having a user (NT) profile (roamming profile)

In the current implementation, ssh always uses the hostname supplied by the user directly for the SSHFP DNS record lookup. This causes problems when using the domain search path, e.g. I have "search example.com" in my resolv.conf and then do a "ssh host", I will connect to host.example.com, but ssh will query the DNS for an SSHFP record of "host.", not

Hi, To begin I'm sorry for my poor English level, that's not my first language. On CentOS 6 I've installed fail2ban 0.8.4 from EPEL repository. I've configured it with this page : http://centoshelp.org/security/fail2ban/ Then I've tried this command : chkconfig --level 23 fail2ban on && service fail2ban start but the output says it fallen, nothing more. The status

Hej, Calling newuoa (from the minqa package) makes R crash when the package rgl is loaded first. This however only on certain selected data. The data used for testing (saved to 'bugs.R'): xvals = c(1,2,4,5,7,8,9,10,11,12,14,15,16,18,19,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36) yvals =

https://bugzilla.mindrot.org/show_bug.cgi?id=3698 Bug ID: 3698 Summary: SSHFP validation fails when multiple keys of the same type are found in DNS Product: Portable OpenSSH Version: 8.7p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: ssh

https://bugzilla.mindrot.org/show_bug.cgi?id=1978 Bug #: 1978 Summary: ECDSA & SHA256 support in SSHFS DNS records Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All URL: https://tools.ietf.org/html/draft-os-ietf-sshfp-ecdsa- sha2-07 OS/Version: All

https://bugzilla.mindrot.org/show_bug.cgi?id=2223 Bug ID: 2223 Summary: Ed25519 support in SSHFP DNS resource records Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at

Hi there I''m planning to build "The Perfect Rails/Debian/Lighttpd Stack", published by Ezra Zygmuntowicz and Sean Schertell at http://brainspl.at/rails_stack.html I''m wondering what sort of constant maintanance that setup would incur. What actions have be regularly performed to keep this setup healthy and secure under normal conditions? Alder

Hi, I am working on a media conversion tool for MacOSX... I currently support encoding to Ogg Vorbis, but in order for my app to work, the user needs to install the Ogg.framework and the Vorbis.framework (as compiled directly from the CVS). I'm wondering if anybody is already distributing those two frameworks, and if not, if it's ok for me to distribute them myself from my web

Hello last week we updated three domain controllers (Sernet Samba) from 4.2 to 4.7, typical upgrade path (4.3->4.4->4.5->4.6->4.7), everything was ok. The next day we got a mail from the Sernet team informing they fixed a bug affecting the group memberships. https://bugzilla.samba.org/show_bug.cgi?id=13095 We've applied the update and few days after the update which should