
From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Tue Aug 11 21:33:01 2015
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 514BE1ACCF3 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue, 11 Aug 2015 21:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.305
X-Spam-Level:
X-Spam-Status: No, score=0.305 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 F45NOn0_aQUV for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue, 11 Aug 2015 21:33:00 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) (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 376B51AC438 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Tue, 11 Aug 2015 21:32:57 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 80DD614A207; Wed, 12 Aug 2015 04:32:53 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: by mail.netbsd.org (Postfix, from userid 1347) id 25F1914A202; Wed, 12 Aug 2015 04:32:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 0812814A14F for <ietf-ssh@netbsd.org>; Tue, 11 Aug 2015 10:23:53 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 0U7alI54tjCj for <ietf-ssh@netbsd.org>; Tue, 11 Aug 2015 10:23:52 +0000 (UTC)
Received: from mail-qg0-f43.google.com (mail-qg0-f43.google.com [209.85.192.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 6CECD14A137 for <ietf-ssh@netbsd.org>; Tue, 11 Aug 2015 10:23:52 +0000 (UTC)
Received: by qged69 with SMTP id d69so135722849qge.0 for <ietf-ssh@netbsd.org>; Tue, 11 Aug 2015 03:23:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=glHMyIcaKfv7Ye7jSOTiqkp/rVFWsqnuC+V+Tzh+JLI=; b=Q2ADvwiNh+Y3+a5YJd0DRRdok2W5P1aKoZGLw7VDlqHM85ii32DD0vji8iViC3pfI6 k3Nd3DNFmirJ0C7+s9dPuTIEQhTSl4mRYa4Pj5CV3Ccok4zbJ8waCH1X6+d3SMfJpAnj wwVh5Pxli8fKm+JuuxyjD8/0C/74xMNw85sVK8uKp66mwg9TV2WW/hixTmjhtq9tUq23 jrzo4rO9sUoDvQwKkASv2dGWA/ORlKfAQ7T6X7XSTZ5mS8314Kgm1+BJeAwHbMPz04V2 TuPuJPMn1e8Oy9W3cqHfsUN6h0bPp5m2osLMl6EFrpIvF4RwtwJuIl90ISPRJ0tBQVu1 pz4g==
X-Gm-Message-State: ALoCoQnzWOoakjY9Fpshkp5WyUm6Hn1XvApx3eROlQgoG8Tvkli05watkjlnAPfihIaij0JeMHYx
MIME-Version: 1.0
X-Received: by 10.140.22.135 with SMTP id 7mr45471003qgn.98.1439274477779; Mon, 10 Aug 2015 23:27:57 -0700 (PDT)
Received: by 10.96.158.9 with HTTP; Mon, 10 Aug 2015 23:27:57 -0700 (PDT)
Date: Tue, 11 Aug 2015 07:27:57 +0100
Message-ID: <CAPofZaHxdFUwi5yw6NxUniakwz35KAKh=hRPz53Q0ZiCtY8RSg@mail.gmail.com>
Subject: Is this list still in use?
From: Phil Lello <phil@dunlop-lello.uk>
To: ietf-ssh@netbsd.org
Content-Type: multipart/alternative; boundary=001a11c12b16fb9f9a051d033344
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

--001a11c12b16fb9f9a051d033344
Content-Type: text/plain; charset=UTF-8

Hi all,

Is this list still in use? I am working on an extension to SSH
authentication, and would like to create an RFC to standardise the
mechanism.

Best wishes,

Phil Lello

--001a11c12b16fb9f9a051d033344
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><div><div><div>Hi all,<br><br></div>Is this list still in use? I am working on an extension to SSH authentication, and would like to create an RFC to standardise the mechanism.<br><br></div>Best wishes,<br><br></div>Phil Lello<br></div>

--001a11c12b16fb9f9a051d033344--

From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Wed Aug 12 02:42:02 2015
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24AD71A0060 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Wed, 12 Aug 2015 02:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 4IKXe5hknR_w for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Wed, 12 Aug 2015 02:41:54 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) (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 E6AFC1A0053 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Wed, 12 Aug 2015 02:41:54 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id DFABA14A1D5; Wed, 12 Aug 2015 09:41:51 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id CD83E14A1D1 for <ietf-ssh@netbsd.org>; Wed, 12 Aug 2015 09:41:47 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id e4uOKRRELLd2 for <ietf-ssh@netbsd.org>; Wed, 12 Aug 2015 09:41:47 +0000 (UTC)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0709.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::709]) by mail.netbsd.org (Postfix) with ESMTP id 7578F14A1D4 for <ietf-ssh@netbsd.org>; Wed, 12 Aug 2015 09:41:44 +0000 (UTC)
Received: from DBXPR07MB062.eurprd07.prod.outlook.com (10.242.147.20) by DBXPR07MB032.eurprd07.prod.outlook.com (10.242.147.25) with Microsoft SMTP Server (TLS) id 15.1.225.19; Wed, 12 Aug 2015 09:41:41 +0000
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com; 
Received: from pc6 (81.151.167.91) by DBXPR07MB062.eurprd07.prod.outlook.com (10.242.147.20) with Microsoft SMTP Server (TLS) id 15.1.225.19; Wed, 12 Aug 2015 09:41:40 +0000
Message-ID: <002901d0d4e3$37a57780$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Phil Lello <phil@dunlop-lello.uk>, <ietf-ssh@netbsd.org>
References: <CAPofZaHxdFUwi5yw6NxUniakwz35KAKh=hRPz53Q0ZiCtY8RSg@mail.gmail.com>
Subject: Re: Is this list still in use?
Date: Wed, 12 Aug 2015 10:42:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.151.167.91]
X-ClientProxiedBy: DB3PR08CA0033.eurprd08.prod.outlook.com (25.161.51.171) To DBXPR07MB062.eurprd07.prod.outlook.com (10.242.147.20)
X-Microsoft-Exchange-Diagnostics: 1;DBXPR07MB062;2:EjGbtbbZYSgydy1EVgyyODw3PqCmp5QT57638WHXNk1aL+1o5/ATmB7SGuadkPu1mP0bCjxhVpogQ8ggq1zua69NA+Z5pXCnlQG236K3LjfqMXXcdI9LrkNAzYJA94ZZUKb6gumcK+0DuyRyXmN/T5JTqlTKjqlMGtnjtqnzYKs=;3:jHccFutcoEbwIG2RNiGlydGmnfrZp+IEzL+luGNmGZZj/BNL2nO03YwYL0uoZ02Y32voSQtWU4riHy025/28vcnG1HkDz2BVtXPS17zeEzNghJ8+9replIFKrxKdAy4YH7yVztay4FxVHflTDYMr3g==;25:EQFXOCcPASqo3x0Jxu1U680Cxg7cjuBFwBrEhhivCkCbNhgTvwleXBzRzfQMuf2bskP6SfRC1NsYIoHfnUrKRzHNEj9UIKaDezne2ZPQ/PJ2vTvO3fvvcLnlrOdr0hx/nw1elgf6yHDiTHN+4AnhOEdVB10M6AOQ9MENnfY0lGYWR5II/D6rduWRJ9hUZIuJrEyoOfMdDrnsGIPde6qKlxDbToXXwjQP1cuOFbttu+JtQEsR304QTJfK7tGSCvbFmawafAAF3+hYd6/Xgq0PDA==;4:aTLhnz8hu/lQ4GBO8MEzdftAujRE/6186FNHFRnQooP2tzuyCHsNgmyrX2/jD1kTuPwESSokiD0lGTembtRDEXmsZBi6Wy/eyvA531iiV0v95JvL4J+Vqp924QoDqs0b6nopada/dr5QgOw1hGHz1pz+k5DUp/7G9DBC2rspUBSLhawWS3qRdqK21MWtZndxaIiPPlffuxxbrH8JuH0mh7AP8mKd4MgB/Vr1hZ7XwgApYk8/qliacndL0jfK26vHVRVY+fIR5aNge39+wr1JzyJP5gA20HtbmomokDT/Hs4=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB062;UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB032;
X-Microsoft-Antispam-PRVS: <DBXPR07MB06296C84C72C71259364B13A07E0@DBXPR07MB062.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5005006)(3002001);SRVR:DBXPR07MB062;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB062;
X-Forefront-PRVS: 0666E15D35
X-Forefront-Antispam-Report: SFV:NSPM;SFS:(10019020)(6009001)(377454003)(51444003)(199003)(189002)(53754006)(13464003)(40100003)(68736005)(84392001)(5001830100001)(77096005)(5001860100001)(5001770100001)(1556002)(81156007)(1456003)(87976001)(50466002)(97736004)(33646002)(4001540100001)(66066001)(19580405001)(19580395003)(46102003)(14496001)(64706001)(47776003)(86362001)(116806002)(50986999)(5001960100002)(81686999)(107886002)(81816999)(76176999)(44716002)(62966003)(101416001)(77156002)(92566002)(62236002)(42186005)(106356001)(122386002)(23676002)(105586002)(50226001)(44736004)(61296003)(189998001)(74416001)(7726001);DIR:OUT;SFP:1102;SCL:1;SRVR:DBXPR07MB062;H:pc6;FPR:;SPF:None;PTR:InfoNoRecords;A:0;MX:1;LANG:en;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQlhQUjA3TUIwNjI7MjM6QlFuTHhrYklzNzNVV25wRlltT0dJbzBRYXVG?= =?utf-8?B?ZGpGN2NBaFFtR0IxbStxeDBRSWV5TThvTEFZcDRGNVI2eFdoWnV3alVMZ1pI?= =?utf-8?B?MlM0Mno2dkpqUEpNTHRTazlLVnY1aXhsN2F0NEljNGFEZWRGcGc2Sy9lK2cv?= =?utf-8?B?NVdoUy9EZWhpN3VYd0Y3S3Q3eWNMeDhQWGx5VTNZcktvNEU2UWwxRmlaeUIy?= =?utf-8?B?MThhZVBwdytBT01HN0xRVE93ODd4eE1MV2IxbEt2QjVRUFE2b0VGcEc0c3J0?= =?utf-8?B?MTE2KzI2Rjc1N2pCTW9nbE1KZ2Y5SHg5T1NzbW5lbXp3RGtMZ1FZcFZUUS9H?= =?utf-8?B?K2NXczJZaHZxWkVleUttak5XSHNLM2xBNWtZRWdkUlI5L0RRRStmOEg5L1Qw?= =?utf-8?B?SklhR2l2Y3d1bFV3WGtKdUQxOWJuNDZJVFAzRHczRUNSeEUrVGlRRElzcXN6?= =?utf-8?B?WmMrdSt0ckRySmZaUnFjMW5IV0k3R1YwM082eS9JclZhTDN0MkgrU1pZVFhp?= =?utf-8?B?UEN0TTQwVXFrT1Q2YUhNTE4ra1o0d0p3S0d1UmZ2NERESWUzdHozNVNTQUp3?= =?utf-8?B?U2xDNDhrcmRUY1lNL2QwVGdiUi9DbE9IRkc2cloxcmMrMTZiQWlyNkl5cDJ0?= =?utf-8?B?UXdic0ZKdll6OUg2amovd1djYWxJcFRXMGtZNTZ1Kzl5QUxLcU9FSmo0UmVQ?= =?utf-8?B?ME9OU3lmbE5MaFg1b3RsYUhLVHZ2dk1HNzlDOWQ0N0RldElaV2Qzbmg5VDA5?= =?utf-8?B?cUVINXNlUEsrYnBZcHJpVUhOcExWa2d3YklYVlJ1VmtEcFRsSEpPSnp6V2Mr?= =?utf-8?B?OHoyWnBaZ2txb0pLSzE2RzVwMGtVTjhiVDJBTVhFRUFtbmdXaW0yeHgySnpR?= =?utf-8?B?TE5aZ1dsT3FhN3pSUzd5UldXUTFBSEIvQk9mWEE3T24ydXZYbGpPd2pISjdu?= =?utf-8?B?ZERzQUpIT2l5S2xBeXpERjZMdUdVQysxY2c5bFVvVGtOVkdzbFdBOFBaN0Fy?= =?utf-8?B?ZDErcFl5cFpyRFZpbHJMc1k1eHN3RVptRklFVkZJTHNGVHlJbjZqYkJnZXVX?= =?utf-8?B?aU9waHFvVlpmQ1o0d2hsNDVMRFppL1prUElBRW9kY1gvU2hLaVlIOUJsbE9P?= =?utf-8?B?Y2g2YmthY3VRamQvM29SYzFPZzkrTmtFdUhLSjBhVExDSHordk81MDBCM0lq?= =?utf-8?B?Q0YweFN1eFBMRU9ocDU0MXJQbnYzZmIrdGQvNmE0eWRGTHhUSy9CK29qdHhy?= =?utf-8?B?bi9leU9zT1BRM3Q4ZEp6WHl3YkJZTFVhN3lJU2M2cXl4T2tseENEK1pHbWFV?= =?utf-8?B?Zm9nUHZlc0tsN1MrZHNrNi9OM0ltYzV1SlhiNDE5WEFnT0xGRUZ2WDFmUWZD?= =?utf-8?B?SDVLNGV0MzJiZ1ZpakcybnU2SVFyNU9HRzMycEY3ZUl3QXZ3UDJvTUZRS001?= =?utf-8?B?Nng5RFVVRFZoTzlCNDJWYkpKRFpCUG1BVE9uWmxpQ3VvVWlTL1dlNUxzU04v?= =?utf-8?B?MUh0MGlVV0w0b0VaMTF4c2VaSzNZWi9Rdm9md3c2WVZURFFERVZONnpaVzMy?= =?utf-8?B?K0dMcExnckZYM3hONG9nb2dlR2g4QW14RnJXaFdFSFEyVjVHdVUwRGxUcFQx?= =?utf-8?B?ZHgyd2lrVU9CVTZnejVUR2xiK05hMHpMUDJ5ZXhPVHZNRUlQM2FNTHh1L0Vk?= =?utf-8?B?dkF2MDRnTzRzc1hFY0N0NmwvckthcmYyWkp4aTlLM1VWbURBVDcxaGhJTnVn?= =?utf-8?B?cWp4b0VDM3FCM1NRUFJEM0k0ZENPQ29JeEczci93SU1YVTlTekVIMUJlMm03?= =?utf-8?B?ZUhqYUM5akJKM3AzRVFyUUZ5TkF0aHFScjBKclkxRVNnUT09?=
X-Microsoft-Exchange-Diagnostics: 1;DBXPR07MB062;5:HqKbQvtI6QZen5l6z3oID1F6b+eIyBc4kdShHUsj51SN+IIihNmt1EmbUk5iqqH3IW84FSQxVCGecUheDHjsb4aFaBetDK3dAfsgtRJnWbu/QzLpu4xpS51WHgrjK1r9Zasv+Y5Q8wXiC7B7WSF6Jg==;24:SXmsmP8HKCKDV10yyXip1v4yyPP4iETUMe9Bd3g6/VzWkI9ltAH92hiB5JTRqLbtK1gBct9/TH2ma4uACVi4GoZQYZ8UuddZiEShqolmd94=;20:/tEUIsinYesUiiMNwkc5ZcMmbaeYXuxqUrnxeL79g/8hVBxabRgdcvQLrtEyJNaCShoiANVpW7o8/0Vc54DZrA==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Aug 2015 09:41:40.6435 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBXPR07MB062
X-Microsoft-Exchange-Diagnostics: 1;DBXPR07MB032;2:IFgLN1vN3bBSCVM8PbdmaoFzP0JJVxzihNsewaheL2jlz0WeRyf6cIC+cc4EY0sLi4hVYukmUnnQ2Cj4efFXY8ZE8bNKdXZP8wjmdBlPCiH6VrSvPvDjHtN8OHRoJ2JBcswlsBaftCw4LKU1ci6YS6uERHykT9J04SVggdBot8M=;3:BGLslDCnic47xJ1wYBAFNNrteA7/vH+MeTCajVLPCaI3sySIy60HEs7+gQpwuAt0TytMDYVb27EaN2kReDuZyp9coXYPu7JTuPGYALZ3PEg1Kk6MqoMW1UFZDHcvlk+mhw6fthyhiFtdei0xH0zZJg==;25:GgNKS2UffXGqPUgcymr7AH8BDi3tMOra1RF37sWuohn6+T9OKTu9Awrm/Nyc3teH5dxOjMstISKtnD/YYW9aXtQ3Ib97HIZjIGvcecNsMHHvAvCwxaeXwvsbHTC9ghV+NlvmKP2Wf/8wHZB7GS3ockO5d7y/Enx7X5dHETRABuaEoq6lzinTpqtUw+3lTiwJF2YzONv/FCMFRodAMlLIJjHpuR3kjV+ta7X33QN/wdBHoejDcCtzh1uNwn6lKyHPIQkW+o6xfI18VrLs3TLeSg==;23:pbhYNJlIRJ9CnZ0hvzOiGJkEElfJMG29yZeYj8yVkCow0ISQHFQkj9D/mMD+Z9UzBdTt1BC9GthG0dsZa8HWFoJhNMchGNUGcIkCi/A2EVfLh5lcnWxGb8wi2tVRI4oCJfmQNTnp8HtOQ4+8td65tnSDbz5C9NJ/p30xAWmXL2w=
X-OriginatorOrg: btconnect.com
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

----- Original Message -----
From: "Phil Lello" <phil@dunlop-lello.uk>
To: <ietf-ssh@netbsd.org>
Sent: Tuesday, August 11, 2015 7:27 AM
> Hi all,
>
> Is this list still in use? I am working on an extension to SSH
> authentication, and would like to create an RFC to standardise the
> mechanism.

It still forwards messages but the last discussion I recall seeing on it
was in May 2014, and that was quite brief.  I assume that you have tried
saag after your post to apps-discuss in which case I think that you have
covered the bases (apart, perhaps, from the Individual/Independent
Submission of an RFC-to-be).

Tom Petch






>
> Best wishes,
>
> Phil Lello
>


From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Mon Aug 24 22:00:16 2015
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F561B29C3 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon, 24 Aug 2015 22:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 N56uJrq4azpM for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon, 24 Aug 2015 22:00:15 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) (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 457921B29E0 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Mon, 24 Aug 2015 22:00:15 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 9E4DC14A199; Tue, 25 Aug 2015 05:00:11 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: by mail.netbsd.org (Postfix, from userid 1347) id 4577C14A198; Tue, 25 Aug 2015 05:00:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id A65FB14A218 for <ietf-ssh@NetBSD.org>; Mon, 24 Aug 2015 23:09:31 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id G1UeEUZKeC2p for <ietf-ssh@NetBSD.org>; Mon, 24 Aug 2015 23:09:31 +0000 (UTC)
Received: from smtp02.srv.cs.cmu.edu (smtp02.srv.cs.cmu.edu [128.2.217.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 08B6A14A208 for <ietf-ssh@NetBSD.org>; Mon, 24 Aug 2015 23:09:29 +0000 (UTC)
Received-SPF: none (cmu.edu: No applicable sender policy available) receiver=smtp02.srv.cs.cmu.edu; identity=mailfrom; envelope-from="jhutz@cmu.edu"; helo="[128.2.193.239]"; client-ip=128.2.193.239
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id t7OLKfOG008634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 24 Aug 2015 17:20:42 -0400 (EDT)
Message-ID: <1440451241.4502.259.camel@minbar.FAC.CS.CMU.EDU>
Subject: Re: Is this list still in use?
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Phil Lello <phil@dunlop-lello.uk>
Cc: jhutz@cmu.edu, ietf-ssh@NetBSD.org
Date: Mon, 24 Aug 2015 17:20:41 -0400
In-Reply-To: <CAPofZaHxdFUwi5yw6NxUniakwz35KAKh=hRPz53Q0ZiCtY8RSg@mail.gmail.com>
References:  <CAPofZaHxdFUwi5yw6NxUniakwz35KAKh=hRPz53Q0ZiCtY8RSg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Scanned-By: mimedefang-cmuscs on 128.2.217.201
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

On Tue, 2015-08-11 at 07:27 +0100, Phil Lello wrote:
> Hi all,
> 
> Is this list still in use? I am working on an extension to SSH
> authentication, and would like to create an RFC to standardise the
> mechanism.


As Tom points out, this list doesn't get much traffic these days.
However, it's probably still the best place to reach SSH implementors
and other protocol experts.  So by all means, if you have an extension
to propose, tell us about it.

-- Jeff

From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Wed Aug 26 10:46:32 2015
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D952C1B2DD3 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Wed, 26 Aug 2015 10:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.287
X-Spam-Level:
X-Spam-Status: No, score=-1.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 gguhNlADModW for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Wed, 26 Aug 2015 10:46:30 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) (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 BEC6D1B2DCF for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Wed, 26 Aug 2015 10:46:30 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 535F914A1A4; Wed, 26 Aug 2015 17:46:27 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: by mail.netbsd.org (Postfix, from userid 1347) id E1E0214A19D; Wed, 26 Aug 2015 17:46:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 511C414A1D7 for <ietf-ssh@netbsd.org>; Tue, 25 Aug 2015 09:29:52 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id sridhLfNn484 for <ietf-ssh@netbsd.org>; Tue, 25 Aug 2015 09:29:51 +0000 (UTC)
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com [209.85.215.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 3AEF314A1B9 for <ietf-ssh@netbsd.org>; Tue, 25 Aug 2015 09:29:48 +0000 (UTC)
Received: by labgv11 with SMTP id gv11so26458925lab.2 for <ietf-ssh@netbsd.org>; Tue, 25 Aug 2015 02:29:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=AoQH+0R0q3WWno7hQcLZcdKdzafjyi26MSED3qWGIuE=; b=Q+XcQN4FB5M6WcrEqspwG/WES659/9oHNRLd2IbC2urOlRdSDrEpnVLThnfCvbcrgw Dxqi656+uJC31hY4lUyB5m+05jv0UoHnz2dRjdjChOmGIhiTgl8LtFY8IYydzWGDI82/ MwVjv6K0sRh63wdF1ErBJk7msJkE/JS4pxVvf4ImaM4sWx4myEynhdxz0Q1CabFi3lUl 5hmQ/JqWu0xVJDgLefCSRaV7ZmxkFJFcsUkY68RdQHphrKMctSfxJ4avCAF+LllY7cXa eae7YDzDJm/+EU52fdk3TsoitHkjt+HUS051ltrIHtv8TcqwctNODSNwAY7SA9+aNGgY rsXA==
X-Gm-Message-State: ALoCoQlPjDjxx5NSNurtytvvIfmwGMciOvG4vfHM6OW+elz/HYJmByGgVZ9e6wJcuTIoJUweY/AP
MIME-Version: 1.0
X-Received: by 10.152.22.4 with SMTP id z4mr24910978lae.81.1440494987276; Tue, 25 Aug 2015 02:29:47 -0700 (PDT)
Received: by 10.25.144.193 with HTTP; Tue, 25 Aug 2015 02:29:47 -0700 (PDT)
Date: Tue, 25 Aug 2015 10:29:47 +0100
Message-ID: <CAPofZaH0bkosr3JxgG6j+b9nZPOSag3UDCibLivgsDghaJFX0Q@mail.gmail.com>
Subject: SSH extensions for Asserted Identities and WebSocket transport
From: Phil Lello <phil@dunlop-lello.uk>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Cc: ietf-ssh@netbsd.org
Content-Type: multipart/alternative; boundary=089e0158b8e204972d051e1f60e9
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

--089e0158b8e204972d051e1f60e9
Content-Type: text/plain; charset=UTF-8

Hi Jeff et al.,

Many thanks for the encouragement. I've exchanged a few emails on other
IETF lists, and am currently working on test implementations as time
permits.

Before I dive into the proposed solution(s), I'll describe my motivation.
Essentially, I'd like to be able to extend existing application-servers
that use SecSH as a transport to support authentication by federated
identities such as SAML.

My initial point of attack was going to be adding a generic "asserted
identity" mechanism to the protocol to allow a client to present
time-limited signed assertions that the server would accept or reject
according to local policy.

I have now shifted focus slightly, and am looking to add support for SASL
mechanisms to SSH, and leverage efforts already made at integrating SAML
and OpenID with non-web transports. Since the SAML and OpenID RFCs still
involve a web loop, it probably makes sense to add an "asserted identity"
SASL mechanism too.

A related extension is a standard WebSocket binding for SecSH; this is
specifically intended for applications that support the SSH protocol and
also expose a web interface. I'm specifically thinking of Gerrit here, but
I'd be surprised if there aren't others. Making the HTTP portion of an
application server widely accessible is generally simpler in a corporate
environment than opening up access to other port numbers, so this would
enable wider deployment of SSH-as-a-transport.

Phil

On Mon, Aug 24, 2015 at 10:20 PM, Jeffrey Hutzelman <jhutz@cmu.edu> wrote:

> On Tue, 2015-08-11 at 07:27 +0100, Phil Lello wrote:
> > Hi all,
> >
> > Is this list still in use? I am working on an extension to SSH
> > authentication, and would like to create an RFC to standardise the
> > mechanism.
>
>
> As Tom points out, this list doesn't get much traffic these days.
> However, it's probably still the best place to reach SSH implementors
> and other protocol experts.  So by all means, if you have an extension
> to propose, tell us about it.
>
> -- Jeff
>
>

--089e0158b8e204972d051e1f60e9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Jeff et al.,<br><br></div>Many thanks fo=
r the encouragement. I&#39;ve exchanged a few emails on other IETF lists, a=
nd am currently working on test implementations as time permits.<br><br></d=
iv>Before I dive into the proposed solution(s), I&#39;ll describe my motiva=
tion. Essentially, I&#39;d like to be able to extend existing application-s=
ervers that use SecSH as a transport to support authentication by federated=
 identities such as SAML.<br><br>My initial point of attack was going to be=
 adding a generic &quot;asserted identity&quot; mechanism to the protocol t=
o allow a client to present time-limited signed assertions that the server =
would accept or reject according to local policy.<br><br></div><div>I have =
now shifted focus slightly, and am looking to add support for SASL mechanis=
ms to SSH, and leverage efforts already made at integrating SAML and OpenID=
 with non-web transports. Since the SAML and OpenID RFCs still involve a we=
b loop, it probably makes sense to add an &quot;asserted identity&quot; SAS=
L mechanism too.<br><br></div><div>A related extension is a standard WebSoc=
ket binding for SecSH; this is specifically intended for applications that =
support the SSH protocol and also expose a web interface. I&#39;m specifica=
lly thinking of Gerrit here, but I&#39;d be surprised if there aren&#39;t o=
thers. Making the HTTP portion of an application server widely accessible i=
s generally simpler in a corporate environment than opening up access to ot=
her port numbers, so this would enable wider deployment of SSH-as-a-transpo=
rt.<br><br></div><div>Phil<br></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Mon, Aug 24, 2015 at 10:20 PM, Jeffrey Hutzelman <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:jhutz@cmu.edu" target=3D"_blank">jhutz@=
cmu.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">On Tue, 2015-08-11 at 07:27 +0100, Phil Lello wrote:<br>
&gt; Hi all,<br>
&gt;<br>
&gt; Is this list still in use? I am working on an extension to SSH<br>
&gt; authentication, and would like to create an RFC to standardise the<br>
&gt; mechanism.<br>
<br>
<br>
</span>As Tom points out, this list doesn&#39;t get much traffic these days=
.<br>
However, it&#39;s probably still the best place to reach SSH implementors<b=
r>
and other protocol experts.=C2=A0 So by all means, if you have an extension=
<br>
to propose, tell us about it.<br>
<br>
-- Jeff<br>
<br>
</blockquote></div><br></div></div>

--089e0158b8e204972d051e1f60e9--
