ZMQ_CURVE(7)

📦
version 4.3.5 · 10 versions
, in epel 10, fedora 43, fedora 44, opensuse-leap 16.0

✨ ZMQ_CURVE(7) — secure authentication and confidentiality 💅

okay bestie, welcome to zmq_curve, straight out of the 0MQ manual. This is the glow-up page about making your sockets actually trust each other. Let's get into it 🫶

🌸 NAME 🌸

zmq_curve — secure authentication and confidentiality. yes that's the whole vibe. 🔐

🎀 SYNOPSIS 🎀

The CURVE mechanism defines a mechanism for secure authentication and confidentiality for communications between a client and a server. CURVE is intended for use on public networks. The CURVE mechanism is defined by this document: http://rfc.zeromq.org/spec:25.

lowkey important: it's for public networks, so like, treat it like wearing your cutest outfit outside. you want to be seen, but not read. 😌

👑 CLIENT AND SERVER ROLES 👑

A socket using CURVE can be either client or server, at any moment, but not both. The role is independent of bind/connect direction.

A socket can change roles at any point by setting new options. The role affects all zmq_connect and zmq_bind calls that follow it.

So like… main character energy, but you can't be two characters at once, periodt.

To become a CURVE server, the application sets the ZMQ_CURVE_SERVER option on the socket, and then sets the ZMQ_CURVE_SECRETKEY option to provide the socket with its long-term secret key. The application does not provide the socket with its long-term public key, which is used only by clients.

To become a CURVE client, the application sets the ZMQ_CURVE_SERVERKEY option with the long-term public key of the server it intends to connect to, or accept connections from, next. The application then sets the ZMQ_CURVE_PUBLICKEY and ZMQ_CURVE_SECRETKEY options with its client long-term key pair.

If the server does authentication it will be based on the client's long term public key.

not me pointing out that the server only ever sees the public half of you. your secret stays yours. iconic. 💅

🦋 KEY ENCODING 🦋

The standard representation for keys in source code is either 32 bytes of base 256 (binary) data, or 40 characters of base 85 data encoded using the Z85 algorithm defined by http://rfc.zeromq.org/spec:32.

The Z85 algorithm is designed to produce printable key strings for use in configuration files, the command line, and code. There is a reference implementation in C at https://github.com/zeromq/rfc/tree/master/src.

so basically: raw bytes if you're feeling feral, cute printable strings if you want to paste them in a config file without crying. 🌈

🍓 TEST KEY VALUES 🍓

For test cases, the client shall use this long-term key pair (specified as hexadecimal and in Z85):

public:
    BB88471D65E2659B30C55A5321CEBB5AAB2B70A398645C26DCA2B2FCB43FC518
    Yne@$w-vo<fVvi]a<NY6T1ed:M$fCG*[IaLV{hID

secret:
    7BB864B489AFA3671FBE69101F94B38972F24816DFB01B51656B3FEC8DFD0888
    D:)Q[IlAW!ahhC2ac:9*A}h:p?([4%wOTJ%JR%cs

And the server shall use this long-term key pair (specified as hexadecimal and in Z85):

public:
    54FCBA24E93249969316FB617C872BB0C1D1FF14800427C594CBFACF1BC2D652
    rq:rM>}U?@Lns47E1%kR.o@n%FcmmsL/@{H8]yf7

secret:
    8E0BDD697628B91D8F245587EE95C5B04D48963F79259877B49CD9063AEAD3B7
    JTKVSB%%)wK0E.X)V>+}o?pNmC{O&4W4b!Ni{Lh6
bestie these are TEST keys. for testing. do not ship them. do not make them your whole personality. 🙈

🔥 SEE ALSO 🔥

iykyk 💜

💖 AUTHORS 💖

This page was written by the 0MQ community. To make a change please read the 0MQ Contribution Policy at http://www.zeromq.org/docs:contributing.

and that's the whole page, bestie!! this was ZMQ_CURVE(7) from the 0MQ manual — 0MQ 4.3.5, dated 10/09/2023. go forth and encrypt responsibly, mwah 💋✨

📦 where this page comes from