forge
PageSigner
| forge | PageSigner | |
|---|---|---|
| 4 | 2 | |
| 4,952 | 1 | |
| 0.5% | - | |
| 0.0 | 1.8 | |
| 6 days ago | 10 months ago | |
| JavaScript | JavaScript | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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.
forge
- Forge: Native implementation of TLS in JavaScript for web apps
-
Generate a public-private keypair from a seed/passphrase/password?
Maybe look into forge: https://github.com/digitalbazaar/forge
-
Environment variables & Its best practices
You might use the .env file, which sits inside a server, to store important passwords and keys to databases and APIs. Keeping it in text inside a .env is risky as it may get exposed if the server is compromised. To avoid this issue, one should use Encryption and Decryption. There are a couple of tools and libraries which offer similar functionality. You can try any of those, but we recommend using CryptoJS or Forge.
- Digitalbazaar/forge: A native implementation of TLS in JavaScript
PageSigner
-
Vampire Attack Twitter
> how do you ensure that they are indeed scraping and not just making up spam?
https://tlsnotary.org/pagesigner
-
Daily General Discussion - January 9, 2022
Cool! Now you can prove to anyone that you have access to private data in ANY server which supports TLS! (Virtually all do). The server didn't have to change anything, it was completely transparent to them. And you didn't have to grant the notary access to the data. That's pretty huge. This technique has, to my surprise, existed for quite some time: TLSNotary and more recently DECO which has been acquired by... Chainlink. DECO looks to be the holy grail, it takes it further by mixing in ZK proofs so that you can selectively reveal certain parts of the server response. I'm not informed enough to say for certain, but I think the 2PC could be expanded to (N)PC which would give you a 1 of N trust model! Alternatively you could just re-execute the same query multiple times with different notaries and have them all agree, still 1 of N.
What are some alternatives?
certstrap - Tools to bootstrap CAs, certificate requests, and signed certificates.
portal-network-specs - Official repository for specifications for the Portal Network
link-lock - Password-protect URLs using AES in the browser; create hidden bookmarks without a browser extension
CryptoLyzer - CryptoLyzer is a fast, flexible and comprehensive server cryptographic protocol (TLS, SSL, SSH, DNSSEC) and related setting (HTTP headers, DNS records) analyzer and fingerprint (JA3, HASSH tag) generator with Python API and CLI/.
js-jose - JavaScript library to encrypt/decrypt data in JSON Web Encryption (JWE) format and to sign/verify data in JSON Web Signature (JWS) format. Leverages Browser's native WebCrypto API.
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
certigo - A utility to examine and validate certificates in a variety of formats
rotki - A portfolio tracking, analytics, accounting and management application that protects your privacy
2Password - 2Password: A cryptography experiment
magit - It's Magit! A Git Porcelain inside Emacs.
Tiling-Assistant - An extension which adds a Windows-like snap assist to GNOME. It also expands GNOME's 2 column tiling layout.
vscodium - binary releases of VS Code without MS branding/telemetry/licensing