similar to: Upgrade to 5.8 broke sshd on IPv4

Hello all, I just found a bug a nice bug that can be turned into a real feature on systems (usually Linux) that are built with --with-ipv4-default. If you enable IPv6 in kernel, and enable both listenaddress 0.0.0.0 and ::, sshd will error out 'address family not supported'. However, you can work around this error by starting sshd with 'sshd -4 -6'. As far as man page is

If all ListenAddress lines in the sshd_config file specify a port, then the -p option to sshd is silently ignored: # cat test_sshd_config2 ListenAddress 0.0.0.0:22 ListenAddress 0.0.0.0:2222 # `pwd`/sshd -D -d -p 4411 -f test_sshd_config2 debug1: sshd version OpenSSH_4.2p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1

Hello, with CentOS 6.2 - is it possible to configure OpenSSH daemon to listen on different IPs _and_ ports? I have received a 2nd IP address for my server and have successfully configured by adding the new "/etc/sysconfig/network-scripts/ifcfg-eth0:1" file. I'd like SSHd to keep listening at the_old_ip:22 but also at the_new_ip:443. The 443 on the_old_ip is already taken by

https://bugzilla.mindrot.org/show_bug.cgi?id=2037 Priority: P5 Bug ID: 2037 Assignee: unassigned-bugs at mindrot.org Summary: sshd Causing DNS Queries on ListenAddress when binding to IPV4 and IPV6 addresses on AIX Severity: normal Classification: Unclassified OS: AIX Reporter: caleblloyd at

Greetings everyone! I would like to know if adding support for Unix socket to sshd would be a feature that would be consider to be added upstream? (ListenAddress). One of the main reason for this question to you all is that tor now has Unix socket support for hidden services that is traffic of a hidden service can be forwarded to a Unix socket (see HiddenServicePort in tor.1). The rationale

I use debian buster on my old notebook, an asus f3ja and I have not grub throuble. I try a virtual mschine with testing and unstable, and both boot regularly Il dom 2 ago 2020, 00:42 Mike McCarthy, W1NR <sysop at w1nr.net> ha scritto: > It appears that it is affecting multiple distributions including Debian > and Ubuntu so it looks like the grub2 team messed up. See > > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am having a problem getting sshd to run after changing it's default port. I edit sshd_config and set the desired port, open it with firewall-cmd and then issue a systemctl start sshd. No error gets reported on the console but the following is logged in /var/messages sshd.service: main process exited, code=exited, status=255/n/a Not a very

Hello, I am having a some problems getting SSHD to run on the Ipv6 interface. Interface/Ipv6 Address: ipv6.open-systems.org [kevin at satan kevin/xp-0.0.15] 536 $ping6 ipv6.open-systems.org PING6(56=40+8+8 bytes) 3ffe:1200:3028:ff01::cab --> 3ffe:1200:3028:ff01::caa 16 bytes from 3ffe:1200:3028:ff01::caa, icmp_seq=0 hlim=64 time=73.96 ms sshd_config: ListenAddress

Hi list, I have a dedicated server managed through ssh and this morning I have upgraded my system from 7.2 to 7.3. After yum finished his work, and rebooted my server. After reboot I tried to log in with ssh and got "Connection refused". I've noticed that all public services were online. So I've contacted my provider to get access to the server and I've noticed that ssh

> Am 01.08.2020 um 23:52 schrieb Leon Fauster via CentOS <centos at centos.org>: > > ?Am 01.08.20 um 23:41 schrieb Kay Schenk: >> Well misery loves company but still...just truly unfathomable! >> Time for a change. > > > I can only express my incomprehension for such statements! > > Stay and help. Instead running away or should I say out of the >

I was wondering what everyone's thoughts were on a simpler way to exclude addresses from having listeners on them. I know a lot of people have multiple subnets, especially larger corporations. Some networks are non-route-able, and therefor unsuitable for use with SSH, aside from communication between other servers on the same subnet. Given that we may want to exclude those non-route-able

Mike McCarthy, W1NR <sysop at w1nr.net> ? 2020?11?3? ?? ??7:56??? > > > Can you reproduce the problem with this document? > > > > And, when the crash happened, could you still ping the computer from > > another device in the network? > > > > Crashing hard so that only a reset helps is usually only possible with a > > kernel bug or hardware issue,

OpenSSH developers, I have removed the fixed, arbitrary limit on the number of ListenAddress allowed by using realloc to dynamically expand listen_socks as needed. This completely removes MAX_LISTEN_SOCKS from the source. I made this change on the version of OpenSSH shipped with CentOS 5.2, version 4.3p2. Please see the attached .c file and .diff file. Please add these changes to OpenSSH

Hello, For some reason ssh has stopped working. Its been a good while since I tried to login remotely so I figure an upgrade is probably to blame as it was working some time ago. This is the only error I see when sshd is started: Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. What does

On 28 January 2017 at 13:44, Mike McCarthy, W1NR <sysop at w1nr.net> wrote: > firewalld isn't the only thing that will prevent services from accessing > the internet. I found that I needed to do a relabel before postfix could > access DNS and I have seen other issues as well. Have you tried > disabling the firewall to see if you can get connections to work? Then > try to

https://bugzilla.mindrot.org/show_bug.cgi?id=2512 Bug ID: 2512 Summary: Use IP_FREEBIND if available for sshd listening socket Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement Priority: P5 Component: sshd

https://bugzilla.mindrot.org/show_bug.cgi?id=2512 Bug ID: 2512 Summary: Use IP_FREEBIND if available for sshd listening socket Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement Priority: P5 Component: sshd

On 04 Feb (10:46:55), Daniel Kahn Gillmor wrote: > On Thu 2016-02-04 07:40:39 -0500, David Goulet wrote: > > > I would like to know if adding support for Unix socket to sshd would be a > > feature that would be consider to be added upstream? (ListenAddress). > > fwiw, i think this is a good idea, but i wouldn't implement it as an > explicit ListenAddress option:

Wonder if you guys could help me out...have a security problem with sshd wich enables a user to do a password login tough the sshd_config states PasswordAuthentication no My config works fine in both gentoo and openbsd 3.3 but users are able to login with tunneled clear text passwords in both 4.9 and 5.1 Im lost.tried everything I can think of. Here is the config:

It seems that the Webalizer WEB statistics reporting package is no longer available in CentOS 7. Rather than building from Sourceforge and writing custom configuration files for it, is there an alternative? Use the Fedora package? Another WEB analyzer? Thanks, Mike