From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=phoenix.com (client-ip=216.205.24.170; helo=us-smtp-delivery-170.mimecast.com; envelope-from=neil_bradley@phoenix.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=phoenix.com Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=phoenix.com header.i=@phoenix.com header.a=rsa-sha256 header.s=mimecast20170203 header.b=e+agJObI; dkim=pass (1024-bit key) header.d=phoenix.com header.i=@phoenix.com header.a=rsa-sha256 header.s=mimecast20170203 header.b=e+agJObI; dkim-atps=neutral Received: from us-smtp-delivery-170.mimecast.com (us-smtp-delivery-170.mimecast.com [216.205.24.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Bmx9s3DzMzDqZD for ; Thu, 10 Sep 2020 08:13:34 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=phoenix.com; s=mimecast20170203; t=1599689609; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=Omfc0D4Fcta+s2vCe5mIzHxihAIdJxuDtsY98z4wL5A=; b=e+agJObIvEfcx1sjDX3OsTXbEL5fIAkH6wqXvbpmUHR+cH7/0WB4hnjA54OPPELTpw7WFH BlY9ACYwyYaGYNw4oF4lrUCdXHhr++Y0Tv87r2OazEVk3OYYLj2l9nL3gnRcDvSa9eCAey SyOPnuhmh22MszPDL6bHw4efa9J11l0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=phoenix.com; s=mimecast20170203; t=1599689609; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=Omfc0D4Fcta+s2vCe5mIzHxihAIdJxuDtsY98z4wL5A=; b=e+agJObIvEfcx1sjDX3OsTXbEL5fIAkH6wqXvbpmUHR+cH7/0WB4hnjA54OPPELTpw7WFH BlY9ACYwyYaGYNw4oF4lrUCdXHhr++Y0Tv87r2OazEVk3OYYLj2l9nL3gnRcDvSa9eCAey SyOPnuhmh22MszPDL6bHw4efa9J11l0= Received: from SCL-EXCHMB-13.phoenix.com (67.51.239.50 [67.51.239.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-257-szWkuymjMVOEygyEkU-9Fw-1; Wed, 09 Sep 2020 18:13:25 -0400 X-MC-Unique: szWkuymjMVOEygyEkU-9Fw-1 X-CrossPremisesHeadersFilteredBySendConnector: SCL-EXCHMB-13.phoenix.com Received: from SCL-EXCHMB-13.phoenix.com (10.122.68.16) by SCL-EXCHMB-13.phoenix.com (10.122.68.16) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Wed, 9 Sep 2020 15:13:22 -0700 Received: from SCL-EXCHMB-13.phoenix.com ([fe80::fd2e:a8f8:f740:cb3b]) by SCL-EXCHMB-13.phoenix.com ([fe80::fd2e:a8f8:f740:cb3b%12]) with mapi id 15.00.1156.000; Wed, 9 Sep 2020 15:13:22 -0700 From: Neil Bradley To: OpenBMC Maillist Subject: bmcweb 30 second lockout Thread-Topic: bmcweb 30 second lockout Thread-Index: AdaG9iozMxnfwn4/QwqseainYVjCAA== Date: Wed, 9 Sep 2020 22:13:21 +0000 Message-ID: <1f5b34f7029a48f39a5dfdbf9aad9e93@SCL-EXCHMB-13.phoenix.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [50.43.115.202] MIME-Version: 1.0 X-OrganizationHeadersPreserved: SCL-EXCHMB-13.phoenix.com Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA70A150 smtp.mailfrom=neil_bradley@phoenix.com X-Mimecast-Spam-Score: 0.0 X-Mimecast-Originator: phoenix.com Content-Type: multipart/alternative; boundary="_000_1f5b34f7029a48f39a5dfdbf9aad9e93SCLEXCHMB13phoenixcom_" Content-Language: en-US X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2020 22:13:39 -0000 --_000_1f5b34f7029a48f39a5dfdbf9aad9e93SCLEXCHMB13phoenixcom_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable I had recently read somewhere on the OpenBMC mailing list (forgive me, as I= can't find it anywhere now) recently indicating that there'd be a 30 secon= d lockout for a given user if there were 3 consecutive failed login attempt= s. My question is firstly, is this the case, and secondly, is it tied to th= e user globally regardless of connection or is it per user and connection? = The reason I ask is that the former would still allow for a denial of servi= ce attack and want to make sure that's not actually the case. Thanks! -->Neil --_000_1f5b34f7029a48f39a5dfdbf9aad9e93SCLEXCHMB13phoenixcom_ Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable

I had recently read somewhere on the OpenBMC mailing= list (forgive me, as I can’t find it anywhere now) recently indicati= ng that there’d be a 30 second lockout for a given user if there were= 3 consecutive failed login attempts. My question is firstly, is this the case, and secondly, is it tied to the user globall= y regardless of connection or is it per user and connection? The reason I a= sk is that the former would still allow for a denial of service attack and = want to make sure that’s not actually the case.

 

Thanks!

 

àNeil

--_000_1f5b34f7029a48f39a5dfdbf9aad9e93SCLEXCHMB13phoenixcom_--