From: Gonglei <arei.gonglei@huawei.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 6/6] vnc: track & limit connections
Date: Tue, 21 Oct 2014 17:10:01 +0800 [thread overview]
Message-ID: <544622E9.4020105@huawei.com> (raw)
In-Reply-To: <1413881843.14632.6.camel@nilsson.home.kraxel.org>
On 2014/10/21 16:57, Gerd Hoffmann wrote:
> On Di, 2014-10-21 at 14:06 +0800, Gonglei wrote:
>> On 2014/10/20 15:02, Gerd Hoffmann wrote:
>>
>>>
>>> Hi,
>>>
>>>> If we set the max trying times, and then
>>>> There are some concepts:
>>>> - INTERVAL_TIME: a time window that user can connnet vnc server
>>>> - REJECT_TIME: the time of reject any connection
>>>> - MAX_TRY_TIMES: the times that user can connect vnc server in INTERVAL_TIME,
>>>> if attach the MAX_TRY_TIMES, the server will lock, any user can not connect again
>>>> before REJECT_TIME attached. The old connected client will not be influenced.
>>>
>>> i.e. effectively rate-limit login attempts. Makes sense to have an
>>> option for that, although I'm not sure it is worth the trouble doing
>>> something beyond a simple "one attempt per second allowed" (i.e. stop
>>> polling the listening socket for a second after each accept).
>>>
>>
>> Hi,
>>
>> "one attempt per second allowed" is just reduce the frequency for attack,
>
> Yes. Which is common practice, to slow down dictionary attacks.
>
>> but I don't think the effect is very well. It can limit the login attempts for
>> attack problem from a flood of attack to "one attempt per second" (not
>> the same magnitude with my approach for security).
>
> Problem with rejecting is any login attempts for REJECT_TIME is that you
> also lock out the good guys.
>
Yes. But I think it is not a big problem, when the REJECT_TIME is over,
the good guys can connect vnc successfully immediately.
Or maybe we just lock those guys with "the same Source IP address" ?
Best regards,
-Gonglei
next prev parent reply other threads:[~2014-10-21 9:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 12:19 [Qemu-devel] [PATCH 0/6] vnc: add support for multiple vnc server instances Gerd Hoffmann
2014-10-15 12:19 ` [Qemu-devel] [PATCH 1/6] vnc: remove vnc_display global Gerd Hoffmann
2014-10-15 12:19 ` [Qemu-devel] [PATCH 2/6] vnc: remove unused DisplayState parameter, add id instead Gerd Hoffmann
2014-10-15 12:19 ` [Qemu-devel] [PATCH 3/6] vnc: switch to QemuOpts, allow multiple servers Gerd Hoffmann
2014-10-15 12:19 ` [Qemu-devel] [PATCH 4/6] vnc: allow binding servers to qemu consoles Gerd Hoffmann
2014-10-15 12:19 ` [Qemu-devel] [PATCH 5/6] vnc: update docs/multiseat.txt Gerd Hoffmann
2014-10-15 12:19 ` [Qemu-devel] [PATCH 6/6] vnc: track & limit connections Gerd Hoffmann
2014-10-15 12:31 ` Daniel P. Berrange
2014-10-15 14:19 ` Gerd Hoffmann
2014-10-15 14:39 ` Daniel P. Berrange
2014-10-16 10:46 ` Gerd Hoffmann
2014-10-17 6:34 ` Gonglei
2014-10-17 6:38 ` Daniel P. Berrange
2014-10-17 6:54 ` Gonglei
2014-10-20 7:02 ` Gerd Hoffmann
2014-10-21 6:06 ` Gonglei
2014-10-21 8:57 ` Gerd Hoffmann
2014-10-21 9:10 ` Gonglei [this message]
2014-10-21 9:35 ` Gerd Hoffmann
2014-10-21 10:32 ` Gonglei
2014-10-15 14:51 ` Eric Blake
2014-10-15 12:32 ` [Qemu-devel] [PATCH 0/6] vnc: add support for multiple vnc server instances Daniel P. Berrange
2014-10-15 14:29 ` Gerd Hoffmann
2014-10-15 14:41 ` Daniel P. Berrange
2014-10-15 12:51 ` Daniel P. Berrange
2014-10-15 14:30 ` Gerd Hoffmann
2014-10-15 14:48 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544622E9.4020105@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=aliguori@amazon.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=weidong.huang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.