similar to: WinSCP 5.7.5 will support the RFC 4419 revision to Diffie-Hellman group exchange

Displaying 10 results from an estimated 10 matches similar to: "WinSCP 5.7.5 will support the RFC 4419 revision to Diffie-Hellman group exchange"

2015 Aug 06
5
[Bug 2441] New: compat listing for WinSCP
https://bugzilla.mindrot.org/show_bug.cgi?id=2441 Bug ID: 2441 Summary: compat listing for WinSCP Product: Portable OpenSSH Version: -current Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org
2017 Jul 24
8
[Bug 2748] New: Bug compatibility masks incorrectly match WinSCP 5.10.x
https://bugzilla.mindrot.org/show_bug.cgi?id=2748 Bug ID: 2748 Summary: Bug compatibility masks incorrectly match WinSCP 5.10.x Product: Portable OpenSSH Version: 7.5p1 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: sshd
2004 May 04
2
[Bug 861] Swapped parameters of SSH_FXP_SYMLINK packet of SFTP protocol
http://bugzilla.mindrot.org/show_bug.cgi?id=861 Summary: Swapped parameters of SSH_FXP_SYMLINK packet of SFTP protocol Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sftp-server AssignedTo:
2013 Oct 17
0
ANNOUNCE: CVE-2013-4419: insecure temporary directory handling for guestfish's network socket
This issue has been assigned CVE-2013-4419. https://bugzilla.redhat.com/show_bug.cgi?id=1016960 (Note this bug is private, but will be made public shortly) ---------------------------------------------------------------------- When using the guestfish --remote or guestfish --listen options, guestfish would create a socket in a known location (/tmp/.guestfish-$UID/socket-$PID). The location has
2013 Jan 08
0
[LLVMdev] [cfe-dev] LTO "bug" and Clang warnings
On 1/8/2013 1:11 PM, Renato Golin wrote: > > Still, doesn't explicitly say it's undefined. I agree this gives the > freedom of implementers to extend naturally, but it's at least arguable. > I have the 2011 draft and couldn't find anything, nor in the current > open issues. It does, actually: C++ 2003 [5.7.5] When an expression that has integral type is added to
2013 Jan 08
4
[LLVMdev] [cfe-dev] LTO "bug" and Clang warnings
On 8 January 2013 18:40, Matthieu Monrocq <matthieu.monrocq at gmail.com>wrote: > I do believe it's undefined. > > §5.2.1 Subscripting [expr.sub] > ... > §5.7 Additive operators [expr.add] > ... > Still, doesn't explicitly say it's undefined. I agree this gives the freedom of implementers to extend naturally, but it's at least arguable. I have the 2011
2016 Nov 01
1
[Bug 98525] New: nouveau graphics freeze when using KDE Plasma 5 with "fifo: PBDMA0: 00200000 subc 0 mthd 000c data 00000000"
https://bugs.freedesktop.org/show_bug.cgi?id=98525 Bug ID: 98525 Summary: nouveau graphics freeze when using KDE Plasma 5 with "fifo: PBDMA0: 00200000 subc 0 mthd 000c data 00000000" Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status:
2015 Sep 18
0
RFC: virtio-peer shared memory based peer communication device
Hello, this is a first RFC for virtio-peer 0.1, which is still very much a work in progress: https://github.com/hw-claudio/virtio-peer/wiki It is also available as PDF there, but the text is reproduced here for commenting: Peer shared memory communication device (virtio-peer) General Overview (I recommend looking at the PDF for some clarifying pictures) The Virtio Peer shared memory
2015 Sep 09
3
[opnfv-tech-discuss] rfc: vhost user enhancements for vm2vm communication
On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages
2015 Sep 09
3
[opnfv-tech-discuss] rfc: vhost user enhancements for vm2vm communication
On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages