Crypto Sessions

Secure end-to-end client sessions & API calls. No cookies, storage, or state management required. Just modern key cryptography!

Description

The goal of this project is to demonstrate the use of private/public key pairs for user authentication, rather than session cookies or passwords.

The advantage of this approach is that you do not have to mess with managing sessions or passwords, which can be a source of friction for a new project. All users are authenticated in real-time via cryptograhy, so there is no need to manage passwords, session tokens, session expiration / revocation, etc.

The disadvantage of this approach is that key management is now pushed into the hands of the user / client, which is a much different paradigm than today. Browsers tend to handle this responsibility very poorly (XSS attacks anyone?), and the loss / leak of passwords is still an issue.

A side-benefit of this approach is that all requests/responses are cryptgraphically signed end-to-end, and data payloads are encrypted end-to-end as well.

The session authentication middleware is also relatively simple, as we are just checking the signature included with the request. This is in contrast to current auth middleware (like Firebase / Oauth) that may involve multiple servers and intermediary requests to issue a session token (then manage that token).

This is dumb. Why change things?

It is a fun experiment! Plus, using public keys for identity works well with cryptocurrency and other emerging protocols (like nostr? ;-)).

There's also a severe lack of tooling when it comes to client-side key management and rotation. DIDs make promises to tackle these issues, but so far there is nothing material (many great devs are working on it!).

But I like to experiement, and state-less user sessions with no password management sounds like it would be fun for small projects. Let me know what you think!

How to Use

This library is designed to work in both Nodejs and browser environments. This library should also work within Cloudflare workers (but I have not tried it yet).

Packages are available on NPM as @cmdcode/crypto-sessions with CDN support:

1<script src="https://unpkg.com/@cmdcode/crypto-sessions"></script>

The library contains three main components:

1. A fetch client (for sending requests to a server)
2. Session handler (can be used client <-> server or standalone p2p)
3. Server middleware (for receiving requests from a client).

Fetch Client

For traditional client requests, this library provides a SecureFetch method that works as a drop-in replacement for the fetch() method API.

1import { SecureFetch } from '@cmdcode/crypto-sessions'
2
3/* Returns a secure fetch method for making requests. */
4
5const fetch = new SecureFetch(
6  // Used for encrypting traffic end-to-end.
7  serverPubkey    : string | Uint8Array,
8  // Used for signing each request.
9  clientSecretKey : string | Uint8Array,
10  // Extends the default Request object.
11  options? : SecureFetchOptions
12)
13
14/* Options for initializing SecureFetch. */
15
16interface SecureFetchOptions {
17  hostname? : string,    // Provides a default hostname to prepend to requests.
18  fetcher?  : Function,  // Use to set a custom fetcher method. Defaults to fetch.
19  verbose?  : boolean,   // Dumps a copy of all outgoing requests to console. useful for debugging!
20  ...Request             // All Request options will work here, and act as defaults for each request.
21}

The new method should act as a drop-in replacement for fetch, and can be configured using the typical Request API.

1const res : SecureResponse = await fetch(
2  'http://localhost:3000/api/endpoint',
3  { 
4    headers : { 'key' : 'value' },
5    method  : 'GET' | 'POST',
6    body    : { content: 'hello world!' }
7  }
8)

The returned Response object will also be similar, but include a few extra fields.

1// The response will look slightly different.
2interface SecureResponse {
3  ...Response  // Typical Response object.
4  data? : any  // Decrypted data returned from the server, if any.
5  err?  : any  // Authentication errors returned from the client, if any.
6}

Session Handler

Underneath the hood, the SecureFetch client is using your keys to create a new CryptoSession object. This object is used to sign and encrypt requests to the server, plus decrypt and verify the server response.

t

1// Example import of the CryptoSession object.
2import { CryptoSession } from '@cmdcode/crypto-sessions'
3
4/* Create a client <-> peer CryptoSession instance.
5 * Your peer must also configure a matching instance.
6 */
7const session = new CryptoSession(
8  // Used for encrypting traffic end-to-end.
9  peerPublickey : string | Uint8Array,
10  // Used for signing each request.
11  yourSecretKey : string | Uint8Array
12)
13
14// Encode a data payload to send outbound.
15const { 
16  token   : string, // Base64urlEncode(clientPubKey + signature)
17  payload : string  // Base64urlEncode(encrypted(payload))
18} = await session.encode(data : string | object)
19
20// Decode and verify an incoming payload.
21const { data, isValid } = await session.decode(token, payload)

When sending a request, yourSecretKey is used to perform the following:

• For GET : Hash + sign the full URL of the request (including query string).
• For POST: Hash + sign the contents of req.body.
• For POST: Encrypt the contents of req.body using the peerPublicKey.
• Provide a token (pubkey + signature) for decryption and verification.

The peerPublicKey is used to encrypt the outgoing payload, plus decrypt and verify the returned response.

You can use the encode and decode methods on the CryptoSession object to establish end-to-end signed and encrypted connection with another peer (ex. via websockets or nostr :-)), or your can use it to authenticate with a traditional HTTP server via a middleware function.

Full API of the CryptoSession object:

Server Middleware

For convenience, this package includes a generic middleware function, plus a wrapper for Express (req, res, next) and NextJs (req, res) style servers.

1import { useCryptoAuth } from '@cmdcode/crypto-sessions'
2
3/* We have to set some environment variables first. */
4
5// The hostname of your server. The client
6// will include your hostname when they sign.
7process.env.CRYPTO_SESSION_HOST
8
9// The secret key to use for establishing sessions.
10process.env.CRYPTO_SESSION_KEY
11
12/* Example of a generic middleware function. */
13
14export async function useMiddleWare(
15  req: Request, res: Response, next: NextFunction
16) {
17  try {
18    // Apply middleware
19    await useCryptoAuth(req, res)
20    // Return next function.
21    return next()
22  } catch (err) {
23    // Catch any errors, return failed response.
24    console.log(err)
25    return res.status(401).end()
26  }
27}

The useCryptoAuth middleware will check req.headers.authorization for any tokens, then use it to create a CryptoSession that decrypts and verifies the request.

Once verified, the CryptoSession instance is stored in req.session, with linked response methods stored in res.secure.

1// Example express API endpoint.
2app.get('http://localhost:3001/api/hello?name=world!', async (
3  req : Request, 
4  res : Response
5) : => {
6
7  // A helper boolean is provided for checking authentication status.
8  req.isAuthorized = true | false
9
10  // You have access to the client/server CryptoSession object.
11  const {
12    peerKey       // The public key of the client.
13    peerHex       // Hex-encoded string of the peerKey.
14    pubKey        // The public key of your server.
15    sharedSecret  // The shared secret between the client <-> server.
16    sharedHash    // The sha256 hash of the shared secret.
17  } = req.session
18
19  // You also have access to all CryptoSession methods.
20  req.session
21    .encode()   // Same encoding method as above.
22    .decode()   // Same decoding method as above.
23    .sign()     // Provides a signature for the provided payload.
24    .verify()   // Verifies a payload signature and key.
25    .encrypt()  // Encrypt an outgoing payload using current CryptoSession.
26    .decrypt()  // Decrypt an incoming payload using current CryptoSession.
27
28  // In addition, you have access to secure response methods.
29  // Use these methods to send a secured response to the client.
30  res.secure
31    .send(data: string, status: number) => Promise<Response>
32    .json(data: object, status: number) => Promise<Response>
33})

Example of using useAuthWithExpress middleware method with Express.

1// Example import of the middleware.
2import { useAuthWithExpress } from '@cmdcode/crypto-sessions'
3
4// Example configuration of the express server.
5const app = express()
6
7app.use(express.urlencoded())
8app.use(express.json())
9app.use(useAuthWithExpress)
10
11app.listen(3000)

Example of using useAuthWithNext middleware method with NextJs.

1// Example import of the middleware.
2import { useAuthWithNext } from '@cmdcode/crypto-sessions'
3
4// Example Next API method.
5async function helloAPI(
6  req : NextApiRequest, 
7  res : NextApiResponse
8) {
9  const { name } = req.query
10  return res.secure.json({ message: `Hello ${name}!` })
11}
12
13// The middleware is used to wrap the method export.
14export default useAuthWithNext(helloAPI)

Cryptography

This library uses the Secp256k1 curve for cryptography, ECDH for shared secret derivation, AES-CBC for encryption, and Schnorr for signatures.

Questions / Issues

Feel free to ask questions and submit issues. All are welcome!

Contributing

Looking for contributors. Feel free to contribute!

Resources

This project aims to be very light-weight. ith minimal dependencies.

@noble/secp256k1
Implementation of secp256k1 in Javascript.
https://github.com/paulmillr/noble-secp256k1

zod
Run-time schema validation with static type inference.
https://github.com/colinhacks/zod

Crypto-Utils
Utility library that wraps WebCrypto and @noble/secp.
https://github.com/cmdruid/crypto-utils

Buff-Utils
Utility library for working with byte arrays.
https://github.com/cmdruid/bytes-utils