ecma262
constant-time
ecma262 | constant-time | |
---|---|---|
22 | 4 | |
14,751 | 18 | |
0.4% | - | |
9.0 | 0.0 | |
1 day ago | about 2 years ago | |
HTML | WebAssembly | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ecma262
- TC39: Add Object.groupBy and Map.groupBy
-
The "well-known" Symbols in JavaScript
These aren't valid JavaScript (@@iterator would throw an error). They are actually internal Symbols used in JavaScript. They are used to implement features like iteration, instanceOf, and such internally. They actually might get removed or changed
-
📦🔓Closures in JavaScript decoded
Note that in previous editions, the ECMAScript® Language Specification used the term "lexical environment" before it decided to rename it to "Environment Record" so you might encounter this term in other definitions and tutorials.
- Document.all Willful Violation
- ES2023 Candidate source code + specification
- ES2023 candidate source code + spec
-
The Evolution of JavaScript
For a new specification to be written, you need two things, a_ technical committee_, and a standard. The standard specification for JavaScript is called ECMA-262, and the technical committee is Technical Committee-39(TC39).
- Why Async/Await Is More Than Just Syntactic Sugar
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]
While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535
For the version of it that is backwards compatible, they wouldn’t need to do anything other than recognise it as valid syntax. Their main concern is that it "could add confusion with very little benefit."
-
What happened to proper tail calls in JavaScript? (2021)
The spec for STC has a critique of PTC:
- performance
- developer tools
- Error.stack
- cross-realm tail calls
- developer intent
See: https://github.com/tc39/proposal-ptc-syntax#issues-with-ptc
Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535
- STC is part of the spec and will take too long to change.
- Now that they've implemented support for PTC, they don't want to regress web pages that rely on it.
- They don't want to discourage vendors from implementing PTC by agreeing to STC.
- They don't want to introduce confusion.
Some of these arguments about confusion and delays seem wrong hindsight, since on every point things would have been better if they'd just agreed to the compromise of STC.
- It would have been part of the spec years ago
- STC would have had a clear way for web pages to know when tail calls could be relied on (and PTC would have been optional)
- Other vendors didn't implement PTC in any case, despite no agreement on STC
- There's even more confusion as things are now
constant-time
-
A beginner's guide to constant-time cryptography (2017)
I noticed in July of 2022 that Go did exactly the vulnerable example and reported it to the security team.
https://github.com/golang/go/issues/53849
It was fixed as of Go 1.21 https://go.dev/doc/go1.21
---
The article cites JavaScript, which is not constant time. There's no sure way to do constant time operations in JavaScript and thus no secure way to do crypto directly in Javascript. Browsers like Firefox depend on low level calls which should be implemented in languages that are constant time capable.
JavaScript needs something like constant time WASM in order to do crypto securely, but seeing the only constant time WASM project on GitHub has only 16 stars and the last commit was 2 years ago, it doesn't appear to have much interest. https://github.com/WebAssembly/constant-time
However, for JavaScript, I recommend Paul's library Noble which is "hardened to be algorithmically constant time". It is by far the best library available for JavaScript. https://github.com/paulmillr/noble-secp256k1
-
Age WASM - age encryption tool in the browser
Also see the constant time spec: https://github.com/WebAssembly/constant-time
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
I'm waiting for constant time WASM. https://github.com/WebAssembly/constant-time/blob/main/propo...
-
Ed25519 Online Tool - Sign, Verify, and Generate Ed25519 Keys.
Also: We're excited for constant time Wasm.
What are some alternatives?
proposal-pattern-matching - Pattern matching syntax for ECMAScript
Ed25519Tool - Ed25519 signing and verification online tool.
spec - WebAssembly specification, reference interpreter, and test suite.
proposal-ptc-syntax - Discussion and specification for an explicit syntactic opt-in for Tail Calls.
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
io-ts - Runtime type system for IO decoding/encoding
agewasm - A simple and secure online client-side Age key generator, encryption and decryption tool built using wasm