summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-1be510f9529cb082f802408b472a77d074b394c0.tar
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz
archives-1be510f9529cb082f802408b472a77d074b394c0.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html9
1 files changed, 9 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html b/zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html
new file mode 100644
index 000000000..7e4fc6a5d
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20110930/1a03e360/attachment.html
@@ -0,0 +1,9 @@
+<p>It seems we are the only distros (with Mandriva) building syslinux with system libpng.</p>
+<div class="gmail_quote">在 2011-9-30 上午2:41,&quot;Erwan Velu&quot; &lt;<a href="mailto:erwanaliasr1@gmail.com">erwanaliasr1@gmail.com</a>&gt;写道:<br type="attribution">&gt; Le 28/09/2011 22:13, D.Morgan a écrit :<br>&gt;&gt; On Wed, Sep 28, 2011 at 9:56 PM, Erwan Velu&lt;<a href="mailto:erwanaliasr1@gmail.com">erwanaliasr1@gmail.com</a>&gt; wrote:<br>
+&gt;&gt;&gt; I&#39;m currently updating Syslinux 4.04 and I&#39;m currently facing a trouble as,<br>&gt;&gt;&gt; historically speaking, we do remove the included libpng by the system one.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; The compilation process fails. I was wondering if we really consider<br>
+&gt;&gt;&gt; replacing the libpng of syslinux as a security issue.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Sec team ? What&#39;s your opinion on it ?<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Cheers,<br>&gt;&gt;&gt;<br>&gt;&gt; hi,<br>&gt;&gt;<br>
+&gt;&gt; i take my security hat on, we prefer when possible when we use the system libs.<br>&gt;&gt; i have not looked but which libpng is included ?<br>&gt; <br>&gt; It take the libpng-source to replace the current syslinux code.<br>
+&gt; <br>&gt; The point is syslinux is a bootloader that obviously don&#39;t share libs <br>&gt; with the rest of the system.<br>&gt; Considering that we can attack the bootloader via a picture means you <br>&gt; compromized the picture. If you can change the picture located at /boot, <br>
+&gt; means that you can compromize the booting parameters too.<br>&gt; <br>&gt; So if we take this road of removing bootloader&#39;s libs, shall we also <br>&gt; remove the jpeg/gz/gcc/... libs too, and maybe for other bootloaders too ?<br>
+&gt; <br>&gt; I do understand the need for the application that runs under linux... <br>&gt; but about the bootloaders...<br>&gt; <br>&gt; What&#39;s your thoughts about it ?<br>&gt; Would you agree on keep syslinux untouched regarding the png lib ?<br>
+&gt; <br></div>