[Secauth] Can we also be protected against such attacks?
Hosnieh Rafiee <hosnieh.rafiee@huawei.com> Wed, 26 November 2014 16:01 UTC
Return-Path: <hosnieh.rafiee@huawei.com>
X-Original-To: secauth@ietfa.amsl.com
Delivered-To: secauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78F601A026E for <secauth@ietfa.amsl.com>; Wed, 26 Nov 2014 08:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9R3Hm6IRizHs for <secauth@ietfa.amsl.com>; Wed, 26 Nov 2014 08:01:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF2771A026A for <secauth@ietf.org>; Wed, 26 Nov 2014 08:01:05 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPG42164; Wed, 26 Nov 2014 16:01:03 +0000 (GMT)
Received: from LHREML513-MBB.china.huawei.com ([fe80::b810:863:a57e:3ff]) by lhreml406-hub.china.huawei.com ([10.201.5.243]) with mapi id 14.03.0158.001; Wed, 26 Nov 2014 16:00:57 +0000
From: Hosnieh Rafiee <hosnieh.rafiee@huawei.com>
To: "secauth@ietf.org" <secauth@ietf.org>
Thread-Topic: Can we also be protected against such attacks?
Thread-Index: AdAJkimCrxm7yXjaSqSrT77Yg3foNg==
Date: Wed, 26 Nov 2014 16:00:56 +0000
Message-ID: <814D0BFB77D95844A01CA29B44CBF8A7A78C6B@lhreml513-mbb.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.82.91]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/x3VHae1CFAPGtjMkswPksZv9T-4
Subject: [Secauth] Can we also be protected against such attacks?
X-BeenThere: secauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Omni-purpose Network-layer based Secure Authentication and Authorization non-working group discussion list <secauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secauth>, <mailto:secauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secauth/>
List-Post: <mailto:secauth@ietf.org>
List-Help: <mailto:secauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secauth>, <mailto:secauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Nov 2014 16:01:11 -0000
Hi Folks, Before start reading the old threads and answering them, I came across this article and found it interesting to share. <http://www.wired.com/2014/11/mysteries-of-the-malware-regin/> When we want to think of open authentication domains, does it involve more risk with such scenarios (in this article)?? Best, Hosnieh
- [Secauth] Can we also be protected against such a… Hosnieh Rafiee
- Re: [Secauth] Can we also be protected against su… Alexandru Petrescu
- Re: [Secauth] Can we also be protected against su… Hosnieh Rafiee