similar to: [Bug 1602] ssh: doesn't handle IPv6 addresses with brackets

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Darren Tucker <dtucker at dtucker.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at dtucker.net --- Comment #9 from Darren Tucker <dtucker at dtucker.net> --- (In reply to Marc

To Whom It May Concern, I tried emailing the ostensible mailing list owner, at both addresses noted, and got no response. Maybe somebody here knows how to alert whomever must know about this. Observe... From home (business class cable with static IP and valid rDNS)... $ host -t mx samba.org samba.org mail is handled by 10 smtp.samba.org. samba.org mail is handled by 5

Hello, It seems there is some rights problem with https://download.gluster.org/pub/gluster/glusterfs/nfs-ganesha/rsa.pub <https://download.gluster.org/pub/gluster/glusterfs/nfs-ganesha/rsa.pub> : wget -O /dev/null https://download.gluster.org/pub/gluster/glusterfs/nfs-ganesha/rsa.pub <https://download.gluster.org/pub/gluster/glusterfs/nfs-ganesha/rsa.pub> --2017-01-23 19:28:47--

My config is this: # Global parameters [global] # bind interfaces only = Yes # if this is turned on, always perfect # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 # interfaces = lo 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 # if all interfaces

Hey! How are you? I have two interfaces (192.168.78.20 / *2001:470:1f1b:5b3:21b:21ff:fea6:ce93* and 192.168.81.20 / *2001:470:1f1b:5b5:21b:21ff:fea6:ce92*) I have interfaces disabled i mean that i bind on everything on samba ac-dc... What here is what is weird, (via bind9 DLZ i am using it and is working), but on my clients i am getting some weird ipv6 addresses: patrikx3 at bitang:~$ ping

https://bugzilla.mindrot.org/show_bug.cgi?id=2180 Bug ID: 2180 Summary: Improve the handling of the key comment field Product: Portable OpenSSH Version: 6.4p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh-keygen Assignee: unassigned-bugs

Can openssh log which public key, as listed in the authorized keys file, was used to log in? If so, how? I don't see a config option, so I'm currently using a custom command via COMMAND="....." ssh-dss AAAAB3Nza..... key1 COMMAND="....." ssh-dss AAAABFFFF..... key2 to log the key. It would be nice if there was a better way. Suggestions? Anthony. -- Anthony R

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Summary: ssh: doesn't handle IPv6 addresses with brackets Product: Portable OpenSSH Version: 5.2p1 Platform: All OS/Version: Linux Status: NEW Keywords: low-hanging-fruit Severity: normal Priority: P2 Component: ssh AssignedTo:

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.herbert+mindrot at gmail. | |com --- Comment #1

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #6 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Just did some more testing with OpenSSH_8.1p1 Apr 2020. It looks like someone did the work to implement a new ssh://[brackets] syntax except in the case where brackets are actually needed. Baffling. So these now work: ssh ssh://[host.local]:23 ssh

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #7 from Marc Herbert

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #10 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Still failing: ssh -V OpenSSH_9.6p1, OpenSSL 3.2.1 30 Jan 2024 ssh ::1 # OK ssh [::1] # Could not resolve hostname [::1] ssh ssh://[127.0.0.1] # Woks!? ssh ssh://[::1] # prints usage message Ridiculously inconsistent. PS: port

http://bugzilla.mindrot.org/show_bug.cgi?id=1194 Summary: .host is known, .00host isn't ... or is it? Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy:

https://bugzilla.mindrot.org/show_bug.cgi?id=2716 Bug ID: 2716 Summary: [PATCH] Add "permitlisten" support for -R style forward Product: Portable OpenSSH Version: 7.5p1 Hardware: amd64 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd

On Tue, 2 Jun 2020 at 06:12, Christian Weisgerber <naddy at mips.inka.de> wrote > On 2020-06-01, Ethan Rahn <ethan.rahn at gmail.com> wrote: > > > With the upcoming deprecation of ssh-rsa I was trying to see what keys my > > version of OpenSSH ( 7.8p1 ) supports. I noticed that "ssh -Q key" does not > > actually list the suggested algorithms to

I'm really, REALLY hoping someone can shed some light on this. I posted something similar about this but I got more confusing info from my LAN people. The hardware is a Soyo K-333 Dragon MB running SuSE 8.0 w/Apache2 & Samba. I have 2 NIC's, the onboard NIC and a D-Link 530TX+ card. I have two IP addresses, 155.16.78.54 & .55 on eth0 I get lots of collisions, errors, etc., and

Attached is a patch which adds a log= directive to authorized_keys. The text in the log="text" directive is appended to the log line, so you can easily tell which key is matched. For instance the line: log="hello world!",no-agent-forwarding,command="/bin/true",no-pty, no-user-rc,no-X11-forwarding,permitopen="127.0.0.1:7" ssh-rsa AAAAB3Nza....xcgaK9xXoU=

https://bugzilla.mindrot.org/show_bug.cgi?id=3627 Bug ID: 3627 Summary: openssh 9.4p1 does not see RSA keys in know_hosts file. Product: Portable OpenSSH Version: 9.4p1 Hardware: SPARC OS: Solaris Status: NEW Severity: major Priority: P5 Component: ssh

Hello, Questions, observations, and curiosities. Maybe this is something stupid or maybe I'm doing something wrong... But... In light of the Kurt Seifried paper on SSH and SSL, I was looking for the finger prints on my various servers and known hosts files to have a little crib sheet and maybe plug the list into a database on my palm pilot. I found that ssh-keygen lists out the

Hi, I have seen this come up in a couple of threads, but nothing recent. I was wondering a couple of things and was hoping someone could clarify. I have an existing working shorewall configuration (Details at end of post). >From within this config, I have a few ports redirected for use with portsentry (like the mini-howto directs forbidden port accesses to port 49999). This works