similar to: [Bug 3831] New: Invalid key length

Hi! I'm investigating the seccomp filter in openssh and I wanted to know whether the following system calls should be added to the filter: 1. getgroups - do_authentication2->dispatch_run_fatal->sshpkt_fatal->logdie->cleanup_exit->do_cleanup->temporarily_use_uid->getgroups 2. setgroups -

Hi comunity, i have implemented in my company a small samba server only use for sharing proposes. Mi problem is simple, in the config i set the directives "client min protocol = SMB2" and "client max protocol = SMB3_11". Acording to this 2 directives a client with Windows XP can't connect to my server, but i have 2 clientes using that OS and conncect without problems.

Hello I'm wondering if anybody has ever done anything like what I'm trying to do, and if so please help!!! This is the situation. I'm working at a university that has a classroom full of WinXP PC's. These machines conncect to a Win Server 2003 box, where they get the user policies and active direcory stuff. Now, we want to put a switch and a Linux Server between the the classroom

Hello everybody, I have systemd set up to listen on ssh socket (:::22), the connection is handled to sshd via socket activation. Usually this works perfectly fine. However the service is checked from nagios. Sometimes the host logs: systemd[1]: Started OpenSSH Per-Connection Daemon ([::1]:60865). systemd[1]: Starting OpenSSH Per-Connection Daemon ([::1]:60865)... systemd[1]: Started OpenSSH

all but one lan host (gv)can ssh connect to host 2x Included windows 10, several linux. 2x is a solaris host. That problem host (gv) can connect to all others but 2x. 2x can connect to all other encluding the problem host (gv) So gv ssh to 2x throws this error: ssh_dispatch_run_fatal: Connection to 192.168.1.42 port 22: incorrect signature. 192.168.1.42 is 2x. So incoming ssh from gv to 2x

CentOS Errata and Security Advisory 2018:3831 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:3831 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 429981c764d258970b014425dfe4a26573613bb5941d254e0deac4aa21ed0c91 firefox-60.4.0-1.el6.centos.i686.rpm x86_64:

People, For some years I have been using rsync quite happily to send / retrieve files to / from SSHDroid Pro but recently I have started having a problem when transferring large numbers of file - I am pretty sure it started after upgrading from Fedora x86_64 28 to 29 - but I am not 100% sure. Below is the tail end of the output of: rsync -avvv root at 192.168.1.100:/storage . >

https://bugzilla.mindrot.org/show_bug.cgi?id=2727 Bug ID: 2727 Summary: ssh_dispatch_run_fatal: Connection to 127.0.0.1 port 8002: message authentication code incorrect Product: Portable OpenSSH Version: 7.5p1 Hardware: ix86 OS: Linux Status: NEW Severity: major Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=3814 Bug ID: 3814 Summary: incorrect signature when ssh'ing to an AIX server (Big Endian) from amd64 (Little endian) Product: Portable OpenSSH Version: 10.0p1 Hardware: PPC64 OS: AIX Status: NEW Severity: major Priority: P5

On Sun 03 Feb 2019, Philip Rhoades via rsync wrote: > > For some years I have been using rsync quite happily to send / retrieve > files to / from SSHDroid Pro but recently I have started having a problem > when transferring large numbers of file - I am pretty sure it started after > upgrading from Fedora x86_64 28 to 29 - but I am not 100% sure. Below is [...] > Corrupted MAC

I have a cron script that polls various machines for their configs and archives any changes. When it connects to an OpenWrt router running "OpenSSH_9.1p1, OpenSSL 1.1.1s 1 Nov 2022", it sometimes gets this error: Bad packet length 1231976033. ssh_dispatch_run_fatal: Connection to 192.168.8.1 port 22: message authentication code incorrect What's odd is that the length is *always*

https://bugzilla.mindrot.org/show_bug.cgi?id=3786 Bug ID: 3786 Summary: openssh client no longer connects to dropbear server Product: Portable OpenSSH Version: 9.9p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at

https://bugzilla.mindrot.org/show_bug.cgi?id=2419 Bug ID: 2419 Summary: SECCOMP filter does not accept getpgid syscall Product: Portable OpenSSH Version: 6.8p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at

On Wed, Jun 19, 2024 at 02:10:30PM +1000, Damien Miller wrote: > On Tue, 18 Jun 2024, Joseph S. Testa II wrote: > > > In the upcoming v9.8 release notes I see "the server will now block > > client addresses that repeatedly fail authentication, repeatedly > > connect without ever completing authentication or that crash the > > server." Has this new

Hi All, I'm having an issue where SSH sessions fail if I enable the cryptodev engine for HMAC. I'd like to confirm if this is a supported configuration and if there are any known bugs. HMAC with the cryptodev engine works fine when using the openssl application directly, so I suspect that something in openssh may be the cause of the issue. I tried this initially with sshd from openssh

Hi, I'm using squid-3.3.8-12.el7_0.x86_64 on CentOS 7 I've configured squid for basic authentication, md5 password *works*, but if fails when I try to use either blowfish or sha password. Below is the cache.log when it fails: 2015/03/18 17:21:02.637 kid1| Checklist.cc(275) matchNode: 0x7f217e8baca8 matched=0 async=0 finished=0 2015/03/18 17:21:02.637 kid1| Checklist.cc(299)

I don't know anything about cryptodev-linux, but I assume it's an openssl engine? If so it's possible sshd's multiprocess model and/or file descriptor handling is confusing it. It's not a configuration we test, so you're mostly on your own to debug it. It's entirely possible there's a bug there; if so, I'd expect it to be something like a fd being closed while

https://bugzilla.mindrot.org/show_bug.cgi?id=3475 Bug ID: 3475 Summary: ED25519 signature verification nondeterministic spurious failure Product: Portable OpenSSH Version: v9.0p1 Hardware: amd64 OS: Linux Status: NEW Severity: critical Priority: P5 Component: ssh

On 02/14/2012 11:01 AM, Jun Koi wrote: > On Tue, Feb 14, 2012 at 11:47 PM, Alex Jia <ajia at redhat.com> wrote: >> Hi Jun, >> I assume you haven't changed libvirt default URI, it may be a issue, >> I want to know whether it works for you if you explicitly specify >> --connect qemu:///system with virt-install? I think a root reason >> probably is your disk

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When