Hello community,

here is the log from the commit of package patchinfo.15256 for 
openSUSE:Leap:15.2:Update checked in at 2020-12-09 00:25:37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Leap:15.2:Update/patchinfo.15256 (Old)
 and      /work/SRC/openSUSE:Leap:15.2:Update/.patchinfo.15256.new.5913 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "patchinfo.15256"

Wed Dec  9 00:25:37 2020 rev:1 rq:853332 version:unknown

Changes:
--------
New Changes file:

NO CHANGES FILE!!!

New:
----
  _patchinfo

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ _patchinfo ++++++
<patchinfo incident="15256">
  <packager>computersalat</packager>
  <rating>moderate</rating>
  <category>recommended</category>
  <summary>Recommended update for proftpd</summary>
  <description>This update for proftpd fixes the following issues:

proftpd was updated to 1.3.6d:

* Issue 857 - Fixed regression in the handling of `%{env:...}` configuration
  variables when the environment variable is not present. 
* Issue 940 - Second LIST of the same symlink shows different results.
* Issue 959 - FTPS uploads using TLSv1.3 are likely to fail unexpectedly.
* Issue 980 - mod_sftp sends broken response when CREATETIME attribute is
  requested.
* Bug 4398 - Handle zero-length SFTP WRITE requests without error.
* Issue 1018 - PidFile should not be world-writable.
* Issue 1014 - TLSv1.3 handshake fails due to missing session ticket key on
  some systems.
* Issue 1023 - Lowercased FTP commands not properly identified.

This update was imported from the openSUSE:Leap:15.1:Update update 
project.</description>
</patchinfo>
_______________________________________________
openSUSE Commits mailing list -- [email protected]
To unsubscribe, email [email protected]
List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette
List Archives: 
https://lists.opensuse.org/archives/list/[email protected]

Reply via email to