Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias
* Package name: collectd-graph-panel
Version : 1
Upstream Author : Pim van den Berg
* URL : http://pommi.nethuis.nl/category/cgp/
* License : GPL3
Programming Lang: PHP
Description : web-based grap
Hello bebyx,
could you please take this bug to a Debian support channel [1] (I
suggest IRC!) and find out, what package this needs to be reassigned
to? And maybe collect more info along the way?
Thanks,
*t
[1] https://www.debian.org/support
Package: wnpp
Severity: wishlist
Owner: Joao Eriberto Mota Filho
* Package name: ulcc
Version : 1.0.1
Upstream Author : DanSoft
* URL : https://bitbucket.org/admsasha/ulcc/src/master/
* License : GPL-3+
Programming Lang: C++
Description : Teaching chil
On 2020-08-05 20:30:59 +0100 (+0100), Nikolaus Rath wrote:
> On Aug 04 2020, Jeremy Stanley wrote:
> > Okay, so for systems to which a malicious party may gain physical
> > access (or remote console access) there's sort of a third risk this
> > addresses. A special case of the second risk really.
On Aug 04 2020, Jeremy Stanley wrote:
> Okay, so for systems to which a malicious party may gain physical
> access (or remote console access) there's sort of a third risk this
> addresses. A special case of the second risk really. *If* you're
> also encrypting the filesystem on which that signing
Package: wnpp
Severity: wishlist
Owner: Fabio Augusto De Muzio Tobich
X-Debbugs-Cc: debian-devel@lists.debian.org, ftob...@gmail.com
* Package name: ipqalc
Version : 1.5.3
Upstream Author : Alexander Danilov
* URL : https://bitbucket.org/admsasha/ipqalc
* License
Hi,
On Tue, 4 Aug 2020 12:31:04 +
Jeremy Stanley wrote:
> Okay, so for systems to which a malicious party may gain physical
> access (or remote console access) there's sort of a third risk this
> addresses. A special case of the second risk really. *If* you're
> also encrypting the filesyste
Hey,
Jeremy Stanley:
> Okay, so for systems to which a malicious party may gain physical
> access (or remote console access) there's sort of a third risk this
> addresses. A special case of the second risk really. *If* you're
> also encrypting the filesystem on which that signing key resides
> (vi
8 matches
Mail list logo