aboutsummaryrefslogtreecommitdiffstats
path: root/Cargo.toml
Commit message (Collapse)AuthorAgeFilesLines
* keys: a party's key may be ecdsa-sha2-nistp256, its signature low-S onlyslopulus64 min.1-0/+2
| | | | | | | | | | | | | | | | | | | | A party's keys may be held where no file has them, in a Secure Enclave or a phone, and those are ECDSA keys on NIST P-256. Everywhere a party's key counts (a version's keys, a key set, the key an event is signed with) such a key is taken beside an Ed25519 one, spelled as `ssh-keygen` writes it, without a comment: `ecdsa-sha2-nistp256`, a space, and the base64 of its SSH encoding, its point uncompressed and on the curve. Its signature is SSHSIG as an Ed25519 one is, hashed with `sha512`, its inner signature over SHA-256 as SSH signs with such a key. ECDSA signatures are malleable: of `s` and the curve's order less `s`, both check. So the federation takes one spelling alone: `s` low, at most half the order, `r` and `s` each SSH's shortest mpint, and the blob reading back to itself as an Ed25519 one does. What anyone makes of a party's signature is then none, as before. The vectors are a key `ssh-keygen -t ecdsa -b 256` made, a first version naming it, and a write and a key set `ssh-keygen -Y sign` signed with it, each taken; the signature's high-S twin, which checks as ECDSA, and its `r` spelled longer are none. Ed25519 keys and signatures are spelled and checked as they were.
* continuum-party: a party's client of a federationtv23 hours1-2/+7
| | | | | | | | | | | | | | | | | | | | | | A second binary, behind the `federation` feature: a party's client, which signs its party's events with one of its keys (`--key`, an OpenSSH private key file), puts them through a node's API (`--node`, its user and password in the URL, or `--token`), and keeps its party's record (`--record`), by which it votes, written before a vote is sent (`federation::party`, run by `continuum::party`): * `init PARTY` begins a record of `PARTY` on the version current now; * `write PATH VALUE`, `keys KEY...`, `nodes NODE...` and `propose FILE` sign events on the node's heads, recorded, and put; * `vote PROPOSAL yes|no` votes on the proposal of that hash on the current version, by the record: with a `true`, the votes on its party's earlier proposal, from the node, checked, kept as the nays that freed it; * `again` signs again, of the latest event it signed at each place, its key set and its node list, what the node refuses as not above its checkpoint's heads, or as built on one it refuses; * `twice RECORD...` names, from the records of parties' clients, a party that voted twice. The feature brings reqwest along, the client's HTTP.
* continuum is a librarytv23 hours1-0/+5
| | | | | | | | Everything the node is moves from the binary into a library (`src/lib.rs`), so that other binaries can use it: a party's client of a federation next. The node's binary (`src/main.rs`) runs it (`continuum::run`), which wires things together as `main` did. The library's doc comments are prose, not examples to test (`doctest = false`); its tests are the library's, as `cargo quick` and `cargo sim` run them.
* federation: the feature, and the store's foldtv28 hours1-0/+3
| | | | | | | | | | | | `federation`, a feature of its own, builds what `docs/federation.md` and `docs/store.md` design, stage by stage; without it continuum builds and behaves as it does. The aliases build with it, and `docs/development.md` says so. Its first part is the store's: an event's ID, the SHA-256 of its bytes written as 64 lower-case hex digits and read back only so, and the `Fold` trait as `docs/store.md` gives it. The trait reads a checkpoint's parts too, the heads it was built at and the events it keeps, which a node taking a pinned checkpoint needs; the design names it. Nothing uses either yet, but a test.
* arti-client: 0.47 -> 0.48tv7 days1-5/+5
|
* api: a stream opened with a token ends with ittv8 days1-3/+3
| | | | | | | | | | | | | | | | | | | | A token was checked when a request came, and a stream answered to it (the dashboard's events, a subscription's links and messages, the store's streams) then went on for as long as the client kept it open: past the token's expiry, past its user's tokens being revoked, its user disabled or removed, its session ended. Now a middleware inside `login::bearer` (`login::streams_end`) ends a streaming answer (`text/event-stream`, `application/x-ndjson`) to a request with a token at the token's deadline, its expiry, or as soon as the document no longer takes it (`token::still_taken`, the checks `verify` makes of the document, now its own function): looked at when a change touches protocol data (the root, a switch, among it), and when a session ends on the node itself in a swarm without a registry (`AppState::session_ended`). No polling: a timer for the expiry, and the changes as they come. The client reconnects with the token it has then; a refreshed token is a new one, so a stream lasts a token's lifetime at most (12 hours by default). `futures` is a dependency of every build now (for `take_until`), not only of libp2p's and Tor's.
* measure deflated chunkstv13 days1-0/+2
|
* api: add application/vnd.continuum.* scalar typestv2026-11-021-0/+2
|
* config: use individual transport enable flagstv2026-11-011-4/+4
|
* add links messagestv2026-10-301-0/+2
| | | | | | | | | Introduce two new wire messages, LINKS and LINKS_REPLY (swarm::links). A member answers with its links: for each peer, the transport, whether it’s relayed, the RTT, and whether it’s dormant. It answers members only, at most every 5 s. This bumps wire::VERSION to 7. Every build answers, with or without the feature, so every node needs this patch before the map shows anything beyond its own node.
* use rustls with ring for reqwesttv2026-10-301-2/+5
|
* make mycelium optionaltv2026-10-301-2/+7
|
* libp2p: add UPnP supporttv2026-10-291-1/+1
|
* libp2p: keep fastest connectiontv2026-10-291-1/+1
|
* bump libp2p & libp2p-streamtv2026-10-281-2/+2
|
* add dev profile and quick/sim aliasestv2026-10-281-0/+10
|
* add tor transporttv2026-10-281-1/+17
|
* add challenge handshaketv2026-10-281-0/+2
|
* add support for public libp2p infrastructuretv2026-10-271-1/+1
|
* use libp2p mDNStv2026-10-271-1/+1
|
* register relays in member list & use AutoNATtv2026-10-271-1/+1
|
* add libp2p relay supporttv2026-10-271-1/+1
|
* use libp2p identify protocol & announce alt addrstv2026-10-271-1/+1
|
* add libp2p transporttv2026-10-271-1/+4
|
* add transports optiontv2026-10-271-0/+2
|
* introduce node keystv2026-10-271-0/+1
|
* replace utoipa by static openapi.yamltv2026-10-261-1/+0
|
* cleanup Cargo.toml (fixup)tv2026-10-241-6/+1
|
* add configuration filestv2026-10-241-0/+1
|
* cleanup Cargo.tomltv2026-10-241-2/+2
|
* add tokio-console feature (fixup)tv2026-10-241-1/+4
|
* edition = "2024" (fixup)tv2026-10-241-1/+1
|
* add Cargo.tomltv2026-10-191-0/+40