EXTERNAL: OSError: [Errno 48] Address already in use

Grant Edwards grant.b.edwards at gmail.com
Tue Jul 3 10:38:23 EDT 2018


On 2018-07-01, Marko Rauhamaa <marko at pacujo.net> wrote:
> Gregory Ewing <greg.ewing at canterbury.ac.nz>:
>
>> I don't see how the address-reuse timeout can be a security measure,
>> because the process trying to take over the address can easily
>> circumvent it by setting SO_REUSEADDR.
>
> [...]
>
> Nevertheless, the later socket object cannot unilaterally take over a
> socket using SO_REUSEADDR. The earlier socket object must have set the
> same option previously.

On what OS?  In my experience, that's not true on Linux or BSD Unix.

-- 
Grant Edwards               grant.b.edwards        Yow! Yes, but will I
                                  at               see the EASTER BUNNY in
                              gmail.com            skintight leather at an
                                                   IRON MAIDEN concert?



More information about the Python-list mailing list