From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-September/008533.html | 81 +++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/008533.html (limited to 'zarb-ml/mageia-dev/2011-September/008533.html') diff --git a/zarb-ml/mageia-dev/2011-September/008533.html b/zarb-ml/mageia-dev/2011-September/008533.html new file mode 100644 index 000000000..ada1375f6 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/008533.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] About syslinux & libpng + + + + + + + + + +

[Mageia-dev] About syslinux & libpng

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Sep 30 14:00:20 CEST 2011 +

+
+ +
On 29 September 2011 20:41, Erwan Velu <erwanaliasr1 at gmail.com> wrote:
+> The point is syslinux is a bootloader that obviously don't share libs with
+> the rest of the system.
+> Considering that we can attack the bootloader via a picture means you
+> compromized the picture. If you can change the picture located at /boot,
+> means that you can compromize the booting parameters too.
+>
+> So if we take this road of removing bootloader's libs, shall we also remove
+> the jpeg/gz/gcc/... libs too, and maybe for other bootloaders too ?
+>
+> I do understand the need for the application that runs under linux... but
+> about the bootloaders...
+>
+> What's your thoughts about it ?
+
+Indeed you got a point...
+
+> Would you agree on keep syslinux untouched regarding the png lib ?
+
+I would revert my vote and go that way.
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1