jnq...@gmail.com wrote:
>
>>From within command mode of the running copy of grub-legacy I have tried
>setting 'terminal graphics', which did nothing, and I have tried
>'testvbe 0x143' (since 800x600x32 mode worked perfectly for me with a
>grub2 based image in the same VM), which just results in a l
Updated 1.0.67 based patch attached.
I am not currently particularly familiar with the debootstrap codebase,
however this certainly seems like a condition that should result in an
error to me.
commit 8e084dc9b0c6d6ee02668e3581e55bbe3047a4d1
Author: jnqnfe
Date: Thu Jan 15 18:05:20 2015 +
Package: debootstrap
Tags: security patch
Patch attached to output warning if falling back to sha1.
commit 0911f1a8ba757a013e4c97e017634eb0ab746997
Author: jnqnfe
Date: Thu Jan 15 19:22:17 2015 +
Issue warning if having to fall back to sha1
diff --git a/debootstrap b/debootstrap
index
Package: debootstrap
Tags: security patch
I am not comfortable with allowing a SHA_SIZE environmental variable,
defined at some point prior to running debootstrap, to dictate the
security of checksum verification performed by debootstrap. I would much
prefer to see the default overridden only by a
Ok, if that's the general feeling on grub legacy now (I'm relatively new
to the Linux world), and recognising your status in the Debian community
(thus respecting highly your opinion on this matter), I will ignore
supporting it further and push for removal from live-build. Thanks.
On 15/01/2015 12
Package: debootstrap
Severity: important
Tags: security patch
In the event of a GPG keyring not being found, debootstrap may fallback
to the alternative security of an https mirror.
Users lacking the requisite GPG keyring file (or perhaps just making a
typo in their parameters) may not necessaril
Additional patch attached to update the manpages with regard to the new
param introduced in the previously supplied patch.
commit 30a65d578daecbc58fe8159572d7c0da9af2ecee
Author: jnqnfe
Date: Fri Jan 16 04:49:43 2015 +
Update manpage with new --sha-size parameter
diff --git a/debootstr
Additional patch attached to update the manpages with regard to the new
param introduced in the previously supplied patch.
I believe I may have misread the code slightly when composing the
initial bug report. I believe now that the matter only arises when the
dist script tries to set the keyring f
Package: debootstrap
Tags: patch
Patch attached to cause a helpful error to be issued to the user in the
event that they should specify a keyring file via the --keyring
parameter, but should the specified keyring file not be found (for
example should the user have made a typo). From a reading of t
9 matches
Mail list logo