Re: [babel] [Babel-users] Reworked implementation of Babel-over-DTLS
"STARK, BARBARA H" <bs7652@att.com> Fri, 15 March 2019 22:46 UTC
Return-Path: <bs7652@att.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01DF1130F04 for <babel@ietfa.amsl.com>; Fri, 15 Mar 2019 15:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 u846EC6wAa_1 for <babel@ietfa.amsl.com>; Fri, 15 Mar 2019 15:46:14 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8962128B14 for <babel@ietf.org>; Fri, 15 Mar 2019 15:46:13 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x2FMjxW4018824; Fri, 15 Mar 2019 18:46:11 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 2r8mn9gp3s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 15 Mar 2019 18:46:11 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x2FMkBgq012181; Fri, 15 Mar 2019 18:46:11 -0400
Received: from zlp30488.vci.att.com (zlp30488.vci.att.com [135.47.91.93]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x2FMk6SS012125; Fri, 15 Mar 2019 18:46:06 -0400
Received: from zlp30488.vci.att.com (zlp30488.vci.att.com [127.0.0.1]) by zlp30488.vci.att.com (Service) with ESMTP id D844B4009E77; Fri, 15 Mar 2019 22:46:06 +0000 (GMT)
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (unknown [130.8.218.154]) by zlp30488.vci.att.com (Service) with ESMTPS id C23AC4009E70; Fri, 15 Mar 2019 22:46:06 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.55]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0435.000; Fri, 15 Mar 2019 18:46:05 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Antonin Décimo' <antonin.decimo@gmail.com>, babel-users <babel-users@lists.alioth.debian.org>
CC: Babel at IETF <babel@ietf.org>
Thread-Topic: [babel] [Babel-users] Reworked implementation of Babel-over-DTLS
Thread-Index: AQHU2zbZKszEhU5Zhky/SnehaH04SaYM2pow
Date: Fri, 15 Mar 2019 22:46:05 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114E0EE094@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <CAC=54BKnmFudHr+LJRb86wzBMkKfZ1w2hQFeS4fszjN=BoYWTg@mail.gmail.com>
In-Reply-To: <CAC=54BKnmFudHr+LJRb86wzBMkKfZ1w2hQFeS4fszjN=BoYWTg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.235.237]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903150154
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/5Rb-P4tIRpIw74s5TUyhhtex-Zk>
Subject: Re: [babel] [Babel-users] Reworked implementation of Babel-over-DTLS
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2019 22:46:15 -0000
> I’ve finally managed to rework my implementation of Babel-over-DTLS > (spoiler: it seems to be working). Thanks to Juliusz for the help. Cool. This is great. <snip> > It is unclear to me how the user interface to provide certificates and private > keys should look like, and if we prefer CA certificates or self-signed. Perhaps > the draft should be more specific about that. Since no one else answered, here are my opinions... My reading of the babel-dtls draft (and DTLS references) is 2 types of certificates are mentioned: X.509 is mandatory and Raw Public Key is optional. Raw Public Key has no signature (self or CA). X.509 can be self-signed or signed by someone else (i.e., a CA). In all cases, the implementation needs (somehow) to be configured with the certificates it trusts for use with Babel. If CAs are going to be trusted to sign usable-for-my-Babel-network certs, then the implementation needs to be configured with CA X.509 certificates that are trusted by the owner of the Babel network. For a basic implementation, I would suggest having a Babel trust store for certificates that are directly trusted for use with Babel (independent of whether or how they are signed). If the certificate is in the Babel trust store, it's trusted. If you also want to support CA-signed trust of X.509 certificates (that are not yet in the Babel trust store), then you need a store of trusted Babel CA certificates. This store MUST NOT be the same trust store used for any web browsers or software updates, etc. It MAY be a trust store of CAs trusted to sign certificates for devices allowed to operate on this (local or virtually local) network. Even if you support CA-signed, you can store received certificates signed by trusted CAs in the "directly trusted" Babel store for future direct trust. As for user interface: One way to do this simply would be to allow a person to provide a file (for trusted certificates) with one or more certificates in PEM format. For the device's own certificate, you could probably get it to generate its own (self-signed certificate) and then provide a file with the certificate in PEM format (that you can then load into other devices). Since the certificate was locally generated, it will already have the private key -- so you won't need to deal with that. All certificate-generating utilities support PEM. If you're running a CA that will generate all the certificates and associated private keys, you'll need to see what file formats that CA implementation supports, for exporting certificates and private keys. Then support that. PEM will likely be supported, but you'll need to see how Certificate+Key gets done. Barbara
- [babel] [Babel-users] Reworked implementation of … Antonin Décimo
- Re: [babel] [Babel-users] Reworked implementation… STARK, BARBARA H