Newsgroups: php.doc,php.internals Path: news.php.net Xref: news.php.net php.doc:969386570 php.internals:98917 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73476 invoked from network); 29 Apr 2017 23:27:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Apr 2017 23:27:08 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@ohgaki.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@ohgaki.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ohgaki.net designates 180.42.98.130 as permitted sender) X-PHP-List-Original-Sender: yohgaki@ohgaki.net X-Host-Fingerprint: 180.42.98.130 ns1.es-i.jp Received: from [180.42.98.130] ([180.42.98.130:36224] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D7/9B-01540-A4125095 for ; Sat, 29 Apr 2017 19:27:07 -0400 Received: (qmail 39175 invoked by uid 89); 29 Apr 2017 23:27:02 -0000 Received: from unknown (HELO mail-qt0-f171.google.com) (yohgaki@ohgaki.net@209.85.216.171) by 0 with ESMTPA; 29 Apr 2017 23:27:02 -0000 Received: by mail-qt0-f171.google.com with SMTP id m36so72550821qtb.0; Sat, 29 Apr 2017 16:27:02 -0700 (PDT) X-Gm-Message-State: AN3rC/5GjlJt334oEtSLhQDemFgnP7xDJ831JE6DNQbcFjw3a1gWRA5q FuBPHvIXwhoRACxgImCVyIdenFGeeA== X-Received: by 10.200.50.183 with SMTP id z52mr17478862qta.272.1493508416536; Sat, 29 Apr 2017 16:26:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.27.179 with HTTP; Sat, 29 Apr 2017 16:26:15 -0700 (PDT) In-Reply-To: References: <1924612862.1298112.1492071094545.JavaMail.zimbra@pieterhordijk.com> <690015854.1384408.1492163148986.JavaMail.zimbra@pieterhordijk.com> Date: Sun, 30 Apr 2017 08:26:15 +0900 X-Gmail-Original-Message-ID: Message-ID: To: Andrey Andreev Cc: Niklas Keller , Pieter Hordijk , Joe Watkins , internals , phpdoc , Nikita Popov Content-Type: multipart/alternative; boundary=001a113a1dfaa31202054e56863c Subject: Re: [PHP-DEV] [RFC][VOTE] Improve hash_hkdf() parameter From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a113a1dfaa31202054e56863c Content-Type: text/plain; charset=UTF-8 On Sun, Apr 30, 2017 at 8:14 AM, Yasuo Ohgaki wrote: > I don't need your view of HKDF RFC or usage, but I do need good practical > examples that justify your point of view. Please don't waste of your/my > time, > just give some good examples in next reply. Thanks. > BTW, valid (yet not common/proper) example that I can think of is, while it does not even require HKDF, though. should be good enough. Even with "Info", following HMAC is enough. -- Yasuo Ohgaki yohgaki@ohgaki.net --001a113a1dfaa31202054e56863c--