Re: [openpgp] New S2K specifiers?
Nils Durner <ndurner@googlemail.com> Sun, 31 March 2019 12:16 UTC
Return-Path: <ndurner@googlemail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60CFF12012B for <openpgp@ietfa.amsl.com>; Sun, 31 Mar 2019 05:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com
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 6STPiZZfu2gu for <openpgp@ietfa.amsl.com>; Sun, 31 Mar 2019 05:16:31 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AB221200C7 for <openpgp@ietf.org>; Sun, 31 Mar 2019 05:16:31 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id b7so4299368lfg.9 for <openpgp@ietf.org>; Sun, 31 Mar 2019 05:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NzIJ5OfhlhPua/3b9ijNvulD22U/2EpExSmV+S6ku3A=; b=LfHkgDwI1yUZ9OMVvct3RcUiyKvB//oQ7oUNG4704inQ+L9pypsckSF516V61EagaS IRUEfrxUbt8jL+aOO2AQEOGkCPCezuwLonZd3MVi6BlZmERCo4FUjgcSfnartfx/LIM3 a3BQ5K62oOJQCowyEsCtJ1kNFWRjlQ6cjG3Bl4AbBGN+GN2fx9suPX5SUSZ6vwlY1Wji MtZeQNRLOZAGEcrt4I57Pj65spUYs0ZdNZz4tPdLWes+MqpXOxlI/fU0xMogQcNNJyCL yxhQr7ZjVLN/2BbGg2tQUpgIBUJJ7xxfUP827enCq8mHxMUKiHzvmnCmdrHWghzmNkru zWIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NzIJ5OfhlhPua/3b9ijNvulD22U/2EpExSmV+S6ku3A=; b=VfqgCR/ZZrVJa661XwEjVyeqd9rfOw/WBxmAhDtHVywir0IITB68BI9Gw6o8Erf6WT i3AcKS4XgtrouoPgDxyXMtl/Y0noqrdh4pY23dfSkFNV2AMppJtaIWuNWFMydaBZCMtn F13mku41FWbjcNjZZOE8/dz1hb+WRIxf8430QXZsb8c7hxNcrKICSAJVf/AZ7gcXsuJd sKd7a9di9qJIv09LlfwIdFc8BROMF5ildVwC2oa8nM2pgZGxKTSe8jLlxDlfA6yBe0JB zEHt3ysgki4+aiiJXsLBI8CscBT6+cB3MUk1JnvOSUtvNICYXrbHGh6ayRMoTV07GAzC z1/Q==
X-Gm-Message-State: APjAAAVGpvzIMNFLx80ik1Rcy2yM5nMPhmp3gPslvV+RcKMYI79J6a2Y 8PgvAoEe7NAmzSwbcsoOgsP2ZhsqX7+HP1p9SJI=
X-Google-Smtp-Source: APXvYqxkOq9JM+ulhl4Pgp1nomVuCKYLUCL7kdOcSkaHfV1Rvt/9kKKqg5pY5G8GbvGXhsLx/4pFRlyYQnc99nuDriQ=
X-Received: by 2002:a19:c204:: with SMTP id l4mr29433296lfc.143.1554034589205; Sun, 31 Mar 2019 05:16:29 -0700 (PDT)
MIME-Version: 1.0
References: <20190331121024.cgta3emx6vefex6x@aurora.local.incenp.org>
In-Reply-To: <20190331121024.cgta3emx6vefex6x@aurora.local.incenp.org>
From: Nils Durner <ndurner@googlemail.com>
Date: Sun, 31 Mar 2019 14:16:18 +0200
Message-ID: <CAOyHO0xvK0zzEBPJHLOFDfhGkKe2a2-PKb2ptHSu5ehY_RJ7HA@mail.gmail.com>
To: Damien Goutte-Gattat <dgouttegattat=40incenp.org@dmarc.ietf.org>
Cc: openpgp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a88ae5058562df6f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/8YptnFTY_4E50sLD_HKSaJGjE_g>
Subject: Re: [openpgp] New S2K specifiers?
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Mar 2019 12:16:33 -0000
Hi Damien, thanks for bringing this up! I would also like to see it included in the standard, but have no immediate application that would use it. If there is general interest, however, I would be happy to work on getting it included. The last comments I have gotten have not been included in my patch. So... is there general interest? What's the best way to proceed? Best regards, Nils
- [openpgp] New S2K specifiers? Damien Goutte-Gattat
- Re: [openpgp] New S2K specifiers? Nils Durner
- Re: [openpgp] New S2K specifiers? Daniel Kahn Gillmor
- Re: [openpgp] New S2K specifiers? vedaal
- Re: [openpgp] New S2K specifiers? Jon Callas
- Re: [openpgp] New S2K specifiers? Jon Callas
- Re: [openpgp] New S2K specifiers? Neal H. Walfield
- Re: [openpgp] New S2K specifiers? vedaal
- Re: [openpgp] New S2K specifiers? Daniel Kahn Gillmor