Syslinux - Jan 2015 - PXE Error Reporting

On 01/20/2015 02:45 PM, Andreas Gruenbacher wrote:
>
> Sorry, but people with such stupid requirements just shouldn't be
> supported. The approach may look alright in a few specific scenarios at
> the cost of everyone else.
>
That is a pretty harsh statement.  That is effectively saying "my use 
case matters more than anyone else's."

	-hpa

On 01/21/2015 09:56 AM, H. Peter Anvin wrote:
> On 01/20/2015 02:45 PM, Andreas Gruenbacher wrote:
>>
>> Sorry, but people with such stupid requirements just shouldn't be
>> supported. The approach may look alright in a few specific scenarios at
>> the cost of everyone else.
>
> That is a pretty harsh statement.  That is effectively saying "my use
> case matters more than anyone else's."
Not really. As a security requirement, if this even really is anyone's 
security requirement, this is pointless -- the ErrCode is set to 0 ("Not 
defined") while the ErrMsg is still set to "Permission denied".
The
server isn't making full use of the protocol at everyone's cost.
That's
why it's a stupid idea, not because of conflicting but equally 
justifiable requirements.

Andreas

On Wed, 21 Jan 2015, Andreas Gruenbacher wrote:
> Not really. As a security requirement, if this even really is anyone's
> security requirement, this is pointless -- the ErrCode is set to 0
("Not
Still, requirements like this d?o? exist in the real world,
dismissing them is a, I quote, stupid idea. I?d suggest
to please wake up.

bye,
//mirabilos (not speaking for his employer here)
-- 
tarent solutions GmbH
Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/
Tel: +49 228 54881-393 ? Fax: +49 228 54881-235
HRB 5168 (AG Bonn) ? USt-ID (VAT): DE122264941
Gesch?ftsf?hrer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg