lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 4 Jan 2017 11:27:10 +0100
From:   Guan Xin <guanx.bac@...il.com>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: ping: What's the purpose of rate limit?

On Wed, Jan 4, 2017 at 7:45 AM, Cong Wang <xiyou.wangcong@...il.com> wrote:
> Hi,
>
> On Sat, Dec 31, 2016 at 4:04 AM, Guan Xin <guanx.bac@...il.com> wrote:
>> Hello,
>>
>> Excuse me, I searched but didn't find an answer --
>>
>> What's the purpose of setting a limit to the "-i" and "-l" parameters
>> of ping for non-root users?
>>
>> It seems that this is only intended to prevent accidental misuse
>> because these restrictions can be easily worked around by starting
>> multiple instances or wrapping the program in a loop, e.g.,
>> while true; do ping -l3 -c3 192.168.0.1; done
>>
>
> I think the purpose of "-i" is not for rate limit, but for either hear beating
> or monitoring latency periodically.
>

Thanks for the reply! Probably I didn't make myself clear --
I meant the limit of 0.2s of the argument to -i for non-root users.

(Please Cc to me because I'm not subscribed to this list. Thanks!)

Regards,
Guan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ