On 2014-05-28 01:10, Edgar E. Iglesias wrote:
> On Wed, May 14, 2014 at 01:22:25AM +, Edgar E. Iglesias wrote:
>> On Wed, May 14, 2014 at 03:13:09AM +0200, Samuel Thibault wrote:
>>> Do not special-case addresses with zero host part, as we do not
>>> necessarily know how big it is, and the gues
On Wed, May 14, 2014 at 03:13:09AM +0200, Samuel Thibault wrote:
> Do not special-case addresses with zero host part, as we do not
> necessarily know how big it is, and the guest can fake them anyway.
> Silently avoid having 0.0.0.0 as a destination, however.
>
> Signed-off-by: Samuel Thibault
I
On Wed, May 14, 2014 at 01:22:25AM +, Edgar E. Iglesias wrote:
> On Wed, May 14, 2014 at 03:13:09AM +0200, Samuel Thibault wrote:
> > Do not special-case addresses with zero host part, as we do not
> > necessarily know how big it is, and the guest can fake them anyway.
> > Silently avoid having
On Wed, May 14, 2014 at 03:13:09AM +0200, Samuel Thibault wrote:
> Do not special-case addresses with zero host part, as we do not
> necessarily know how big it is, and the guest can fake them anyway.
> Silently avoid having 0.0.0.0 as a destination, however.
>
> Signed-off-by: Samuel Thibault
R
Do not special-case addresses with zero host part, as we do not
necessarily know how big it is, and the guest can fake them anyway.
Silently avoid having 0.0.0.0 as a destination, however.
Signed-off-by: Samuel Thibault
---
This is particularly bad actually, one can for instance simply do this
i