Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-flor
Version : 1.1.1
Upstream Author : Andreas Dewes
* URL : https://github.com/DCSO/flor/
* License : BSD_3-clause
Programming
On Thu, Jan 24, 2019 at 08:00:12PM +, Holger Levsen wrote:
> On Thu, Jan 24, 2019 at 03:18:40PM +, Ian Jackson wrote:
> > To the Debian Perl maintainers: [...]
> > To the Debian security team: [...]
>
> I've read the whole thread and am surprised "talking to upstream" (and
> fixing the iss
Package: wnpp
Severity: wishlist
Owner: Andreas Henriksson
* Package name: mender-cli
Version : 1.1.0-1
Upstream Author : Mender
* URL : https://github.com/mendersoftware/mender-cli
* License : Apache-2.0
Programming Lang: Go
Description : A general-pur
Package: wnpp
Severity: wishlist
Owner: Hanno Stock
* Package name: displaylink
Version : 4.4
Upstream Author : DisplayLink (UK) Ltd.
* URL : https://www.displaylink.com/downloads
* License : proprietary
Programming Lang: binary
Description : Proprietar
Vincent Lefevre writes ("Re: Potentially insecure Perl scripts"):
> I fear that this is not that simple: I suppose that this will break
> scripts that modify @ARGV to make <> secure. :(
The easiest way to sanitise a string to make it safe for 2-argument
open involves:
* prepending ./ if the strin
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: salmid
Version : 0.1.23
Upstream Author : Henk den Bakker
* URL : https://github.com/hcdenbakker/SalmID
* License : MIT
Programming Lang: Python
Description : rapid Kmer based Salmone
Package: wnpp
Severity: wishlist
Owner: Felix Salfelder
* Package name: gnucap-custom
Version : 0.0.1
Upstream Author : Felix Salfelder
* URL : https://gitlab.com/gnucap/gnucap-custom
* License : GPLv3+
Programming Lang: C++
Description : A basis for G
Holger Levsen writes ("Re: Potentially insecure Perl scripts"):
> On Thu, Jan 24, 2019 at 03:18:40PM +, Ian Jackson wrote:
> > To the Debian Perl maintainers: [...]
> > To the Debian security team: [...]
>
> I've read the whole thread and am surprised "talking to upstream" (and
> fixing the is
Sorry for not reading the whole thread first, so my last mail didn't
take account of this one...
Dominic Hargreaves writes ("Re: Potentially insecure Perl scripts"):
> No, I don't think you did; thank you for putting it so succinctly.
> As is obvious from the discussion, this is clearly not someth
9 matches
Mail list logo