| Crates.io | fortress-server |
| lib.rs | fortress-server |
| version | 1.0.0 |
| created_at | 2022-10-03 07:59:53.988595+00 |
| updated_at | 2022-10-03 07:59:53.988595+00 |
| description | Fortress password manager sync server |
| homepage | https://github.com/fpgaminer/fortress-server |
| repository | https://github.com/fpgaminer/fortress-server |
| max_upload_size | |
| id | 678806 |
| size | 80,966 |
Fortress Server is the sync server for the Fortress password manager.
Authorization header required for all requests. It must contain the hex encoded 32 byte LoginId followed by the hex encoded 32 byte LoginKey (total 128 characters).
GET /objectsReturns a list of all objects in the database belonging to the user. The response is a JSON array where each element is an array of the form [id, siv], and both are hex encoded.
GET /object/:idReturns the object's data. ID is hex encoded.
POST /object/:id/:old_sivCreates or updates an object. The request body is the object's data (including the SIV). :id and :old_siv are hex encoded. If the object already exists, :old_siv must match the object's current SIV. If the object does not exist, :old_siv is ignored. Conflict (409) is returned if the object already exists and :old_siv does not match the object's current SIV. This is to prevent overwriting an object that has been updated since the last time the client fetched it.
./run-test-db.sh
cargo run
./run-test-db.sh
cargo test
docker build -t fortress-server .
docker tag fortress-server DEST
docker push DEST