📅 Original date posted:2014-10-14
📝 Original message:FYI:
"In order to progress towards exit to Last Call for the Web Crypto API, the
chair suggests the following resolution for that bug.
resolution : Bug CLOSED. This problem will be addressed by the extension bug
25618 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25618.
If none objects before the 20th of Oct @20:00 UTC, this resolution will be
endorsed."
On 13 October 2014 19:18, Matt Corallo <bitcoin-list at bluematt.me> wrote:
> See-also: this related bug on Curve25519 and some MS Research curves
> that generated far more discussion.
>
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839
>
> Matt
>
> On 10/13/14 10:01, Melvin Carvalho wrote:
> > FYI:
> >
> > This is an issue I filed related to adding secp256k1 into Web Crypto API
> > which will be implemented natively in (some) web browsers.
> >
> > If there is any feedback from crypto implementers, please feel free to
> > add comments to this thread:
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444
> >
> > ---------- Forwarded message ----------
> > From: ** <bugzilla at jessica.w3.org <mailto:bugzilla at jessica.w3.org>>
> > Date: 13 October 2014 09:18
> > Subject: [Bug 24444] Named Curve Registry (adding secp256k1)
> > To: melvincarvalho at gmail.com <mailto:melvincarvalho at gmail.com>
> >
> >
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444
> >
> > Myron Davis <myrond at gmail.com <mailto:myrond at gmail.com>> changed:
> >
> > What |Removed |Added
> >
> ----------------------------------------------------------------------------
> > Status|RESOLVED |REOPENED
> > CC| |myrond at gmail.com
> > <mailto:myrond at gmail.com>
> > Resolution|NEEDSINFO |---
> >
> > --- Comment #2 from Myron Davis <myrond at gmail.com
> > <mailto:myrond at gmail.com>> ---
> > Could this be looked at again?
> >
> > Last response was waiting for feedback from crypto implementors.
> >
> > Currently secp256k1 is supported in the following SSL/TLS libraries now
> > Botan
> > NSS
> > openssl
> > LibreSSL
> > PolarSSL
> > JSSE
> >
> > The three other curves are all all have parameters which do not define
> > how they
> > were generated. secp256k1 curve has some great advantages in faster
> > signature
> > verification and how the values were determined for the curve. (i.e. not
> > random).
> >
> > http://www.ietf.org/rfc/rfc4492
> >
> > The curve has had a lot of eyes on it with lots of hardware and software
> > supporting this curve.
> >
> > With discovery of backdoor's in NIST's random number generator
> > (https://www.schneier.com/blog/archives/2007/11/the_strange_sto.html ) I
> > would
> > like to see a determined parameter curve instead of a "random" curve
> option.
> >
> > Thanks
> >
> > --
> > You are receiving this mail because:
> > You reported the bug.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> > http://p.sf.net/sfu/Zoho
> >
> >
> >
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20141014/486b7876/attachment.html>;
Melvin Carvalho [ARCHIVE] /
npub1uv…saxrt
2023-06-07 15:26:26
in reply to nevent1q…3wjw
Author Public Key
npub1uvtfvcegcn9kds68r8he57emc480vqtx8t22kpsctxgjxae44gvsksaxrtSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:26:26Event JSON
{
"id": "f497dceac17ea3fc6e5092ac58681e54184df3706c496e1fa57d5ad46e7249ef",
"pubkey": "e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19",
"created_at": 1686151586,
"kind": 1,
"tags": [
[
"e",
"6119596955585a89c0782840d3098b04d8ae1d7f2916897239a6ef3b6a641de9",
"",
"root"
],
[
"e",
"3fd390f04c13afd1327e965854f90a4304613c039b55e80aff23692a79f2bb8e",
"",
"reply"
],
[
"p",
"cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba"
]
],
"content": "📅 Original date posted:2014-10-14\n📝 Original message:FYI:\n\n\"In order to progress towards exit to Last Call for the Web Crypto API, the\nchair suggests the following resolution for that bug.\n\nresolution : Bug CLOSED. This problem will be addressed by the extension bug\n25618 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25618.\n\nIf none objects before the 20th of Oct @20:00 UTC, this resolution will be\nendorsed.\"\n\nOn 13 October 2014 19:18, Matt Corallo \u003cbitcoin-list at bluematt.me\u003e wrote:\n\n\u003e See-also: this related bug on Curve25519 and some MS Research curves\n\u003e that generated far more discussion.\n\u003e\n\u003e https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839\n\u003e\n\u003e Matt\n\u003e\n\u003e On 10/13/14 10:01, Melvin Carvalho wrote:\n\u003e \u003e FYI:\n\u003e \u003e\n\u003e \u003e This is an issue I filed related to adding secp256k1 into Web Crypto API\n\u003e \u003e which will be implemented natively in (some) web browsers.\n\u003e \u003e\n\u003e \u003e If there is any feedback from crypto implementers, please feel free to\n\u003e \u003e add comments to this thread:\n\u003e \u003e https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444\n\u003e \u003e\n\u003e \u003e ---------- Forwarded message ----------\n\u003e \u003e From: ** \u003cbugzilla at jessica.w3.org \u003cmailto:bugzilla at jessica.w3.org\u003e\u003e\n\u003e \u003e Date: 13 October 2014 09:18\n\u003e \u003e Subject: [Bug 24444] Named Curve Registry (adding secp256k1)\n\u003e \u003e To: melvincarvalho at gmail.com \u003cmailto:melvincarvalho at gmail.com\u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444\n\u003e \u003e\n\u003e \u003e Myron Davis \u003cmyrond at gmail.com \u003cmailto:myrond at gmail.com\u003e\u003e changed:\n\u003e \u003e\n\u003e \u003e What |Removed |Added\n\u003e \u003e\n\u003e ----------------------------------------------------------------------------\n\u003e \u003e Status|RESOLVED |REOPENED\n\u003e \u003e CC| |myrond at gmail.com\n\u003e \u003e \u003cmailto:myrond at gmail.com\u003e\n\u003e \u003e Resolution|NEEDSINFO |---\n\u003e \u003e\n\u003e \u003e --- Comment #2 from Myron Davis \u003cmyrond at gmail.com\n\u003e \u003e \u003cmailto:myrond at gmail.com\u003e\u003e ---\n\u003e \u003e Could this be looked at again?\n\u003e \u003e\n\u003e \u003e Last response was waiting for feedback from crypto implementors.\n\u003e \u003e\n\u003e \u003e Currently secp256k1 is supported in the following SSL/TLS libraries now\n\u003e \u003e Botan\n\u003e \u003e NSS\n\u003e \u003e openssl\n\u003e \u003e LibreSSL\n\u003e \u003e PolarSSL\n\u003e \u003e JSSE\n\u003e \u003e\n\u003e \u003e The three other curves are all all have parameters which do not define\n\u003e \u003e how they\n\u003e \u003e were generated. secp256k1 curve has some great advantages in faster\n\u003e \u003e signature\n\u003e \u003e verification and how the values were determined for the curve. (i.e. not\n\u003e \u003e random).\n\u003e \u003e\n\u003e \u003e http://www.ietf.org/rfc/rfc4492\n\u003e \u003e\n\u003e \u003e The curve has had a lot of eyes on it with lots of hardware and software\n\u003e \u003e supporting this curve.\n\u003e \u003e\n\u003e \u003e With discovery of backdoor's in NIST's random number generator\n\u003e \u003e (https://www.schneier.com/blog/archives/2007/11/the_strange_sto.html ) I\n\u003e \u003e would\n\u003e \u003e like to see a determined parameter curve instead of a \"random\" curve\n\u003e option.\n\u003e \u003e\n\u003e \u003e Thanks\n\u003e \u003e\n\u003e \u003e --\n\u003e \u003e You are receiving this mail because:\n\u003e \u003e You reported the bug.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e ------------------------------------------------------------------------------\n\u003e \u003e Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer\n\u003e \u003e Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports\n\u003e \u003e Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper\n\u003e \u003e Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer\n\u003e \u003e http://p.sf.net/sfu/Zoho\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e Bitcoin-development mailing list\n\u003e \u003e Bitcoin-development at lists.sourceforge.net\n\u003e \u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer\n\u003e Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports\n\u003e Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper\n\u003e Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer\n\u003e http://p.sf.net/sfu/Zoho\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20141014/486b7876/attachment.html\u003e",
"sig": "77f992c4625dcc2faac339f7da83774fd1c95f3a647eed7bedc51a5cace86108eeb1bbd97c14766efc1f5c4e5503b57980f8cda811adee5942fd8d8f1f3acb6b"
}