similar to: [PATCH] Remove unused since ssh1 protocol removal crc32.[ch]

See attached: (1) patch against 7.9p1, tested with openssl 1.1.0j and openssl 1.1.1a on linux/i386; passes regression test and connects to unpatched sshd without problems; I hacked a bit regress/unittests/kex, and benchmarked do_kex_with_key("curve25519-sha256 at libssh.org", KEY_ED25519, 256); Before: 0.3295s per call After: 0.2183s per call That is, 50% speedup; assuming

On some cpu's optimized chacha implementation in openssl (1.1.0+) is notably faster (and on others it is just faster) than generic C implementation in openssh. Sadly, openssl's chacha20-poly1305 (EVP_chacha20_poly1305) uses different scheme (with padding/etc - see rfc8439) and it looks it is not possible to use in openssh. OpenSSL 1.1.1+ also exports "raw" poly1305 primitive,

On Fri, 2019-07-12 at 15:54 +1000, Damien Miller wrote: > On Thu, 17 Jan 2019, Yuriy M. Kaminskiy wrote: > > > On some cpu's optimized chacha implementation in openssl (1.1.0+) > > is > > notably faster (and on others it is just faster) than generic C > > implementation in openssh. > > > > Sadly, openssl's chacha20-poly1305

On Solaris 8, I have ssh 3.1.0 and on other box Sol 7 I have 1.2.26 (min version for comtable with ssh 3), I checked also /etc/ssh2/sshd2_config file ## SSH1 compatibility # Ssh1Compatibility <set by configure by default> # Sshd1Path <set by configure by default 2) generate key for ssh3 # ssh-keygen2 -P /etc/ssh2/hostkey

https://bugs.freedesktop.org/show_bug.cgi?id=34429 Summary: Failure during resume on NV50: INIT_AUXCH: rd auxch fail -121 Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau

CORE SDI http://www.core-sdi.com SSH1 CRC-32 compensation attack detector vulnerability Date Published: 2001-02-08 Advisory ID: CORE-20010207 Bugtraq ID: 2347 CVE CAN: CAN-2001-0144 Title: SSH1 CRC-32 compensation attack detector vulnerability Class: Boundary Error Condition Remotely Exploitable: Yes Locally Exploitable: Yes Release Mode:

Hi Samba I noticed that the crc32 function in lib/crc32.c is somewhat inefficient. This little patch will reduce the inner loop from 10 instructions to 8 instructions on x86 with gcc. gcc can't figure out this simple optimization by itself on x86. Further optimization is possible by using the impl. in the linux 2.5 kernel, but I don't know if it is worth it. Is crc32 common in samba?

Dear R-develers, Antoine Lucas suggested extending my small digest package (which provides md5 and sha-1 digests of R objects, which it are serialized if needed) with a crc32 function, and provided a fairly complete patch. We are now wondering if we should play it safe and bundle crc32.c (plus utils) in the digest sources (as I do with md5 and sha1), or if we can assume that crc32 is present on

OCFS Experts, Sorry if the questions below are naive, or were answered before, but here it goes. I have a potential client who at the moment having problems installing 10g RAC on RHEL 3.0 (2.4.21-20). They using (rather planning to use) OCFS for everything, including CRS files (OCR, voting). Questions: 1) They use custom kernel (modified by their security people). Do we support OCFS on the

What about multiple errors detection with crc32? Is it work? Thanks.

OpenSSH defines a function crc32(), and so does the zlib library. This is at best confusing (since they are different functions with different prototypes), and at worst a source of crashes. I found this problem getting OpenSSH up and running on Darwin, which turned out to be calling the wrong function. My bandaid was to include ``-Dcrc32=crcsum32'' in CFLAGS. The proper fix would be

Good day, some time ago we discussed that it would be very helpful to store epoch in inode on mds. the perfect solution could be to store epoch in old inode body, but there is no much space for this in the body and with DMU we''ll have this problem again. given the minimal inode size we use on MDS is 512 bytes, we can store upto 13 stripes in the body. larger EAs go to a dedicated block.

https://bugs.freedesktop.org/show_bug.cgi?id=34680 Summary: Enable dithering by default for eDP panels Product: xorg Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

There's a world of difference between changing defaults and killing functionality. SSH in general and OpenSSH in particular is part of what we'll eventually get around to identifying as (I know everyone hates this word) critical infrastructure. That means it doesn't break, particularly not intentionally, and even more particularly not without time, warning, and probably public input.

Generically, yes, the hardware is supported. On Mon, Sep 18, 2017 at 11:42 PM, <ygrishin-lists at mail2.ca> wrote: > I will update the thread as soon as I get the hardware back. It was > something serious like artifacts or no video in X so that I had to resort to > proprietary drivers. > So the question is whether this hardware is supported or not. > > > On 2017-09-18

ah yes.. that are the "limitation", but know limitations ( for us ) Rowland, this is something to add on the wiki. (here : https://wiki.samba.org/index.php/DNS_Administration ) ;-) Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens Yuriy Tabolin >Verzonden: woensdag 19 augustus 2015 11:35 >Aan: samba at

https://bugzilla.mindrot.org/show_bug.cgi?id=2583 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Blocks| |2647 CC| |djm

FYI, The CRC64 intrinsics were renamed to CRC32 since there is no such thing. See below for details. Chad On May 26, 2011, at 4:13 PM, Chad Rosier wrote: > Author: mcrosier > Date: Thu May 26 18:13:19 2011 > New Revision: 132163 > > URL: http://llvm.org/viewvc/llvm-project?rev=132163&view=rev > Log: > Renamed llvm.x86.sse42.crc32 intrinsics; crc64 doesn't exist.

I see that commercial SSH version it is possible to run sshd in SSH1 using DES (i.e, accepting SSH-DES clients). I understand from Damien Miller that Cisco routers also run in only SSH1 DES mode. Is it possible in openSSH to configure sshd (compile-time/runtime) to run sshd in SSH1 or SSH2 mode and accept SSH1 or SSH2 DES clients ? [I would like to be able to run sshd in SSH1/DES mode ] Is

Hi, the OpenSSH installation script for Cygwin still creates a SSH1 host key by default. My question is, wouldn't it make more sense to drop all auto-generation of SSH1 keys from the default installation procedure? I mean, nobody should use SSH1 anymore, right? Or should the script stick to it for some reason? Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat