2.0.0-alpha.5

We are changing the version numbering scheme by removing the v prefix, which was causing issues with deb tools.

Fixes

#143 When initializing the keyring or rotating the master password, the new password is now written without a trailing newline when the command output is redirected to a file.

Various

#141 Bump deps
#142 Dockerfile build from deb is now the main one

v2.0.0-alpha.4

Features

#134 few changes:

• add rotate-password command to rotate the master password. it returns a new random password and update the keyring (and removes the salt, which becomes useless since the new password is randomly generated)
• add the command init-keyring to intialize a new keyring with a corresponding random master password
• modify add-key to panic if no keyring is found at the provided path

Various

#135 update dependencies and rust to 1.93.1
#131 add docker_file to build container from deb
#137 fix write_once
#139 fix traversal_attack_detection

v2.0.0-alpha.3

important

#123 switches from amazing but deprecrated sodiumoxyde lib to the official libsodium_rs binding. Retro compatibility is included.

breaking changes

#122 removes the chunk-size cli parameter and the DS_CHUNK_SIZE env var
#124 moves the salt params from the command line argument to the keyring file

! see #124 to know how moving the salt, the new encoding could be made by using echo -n 'previous_salt' | base64

various

#127 simplify code by using serde_with

v2.0.0-alpha.2

breaking changes

#117 Some cli args have been renamed to better frame the s3 protocol :

--aws-access-key -> --s3-access-key
--aws-secret-key -> --s3-secret-key
--aws-region -> --s3-region
--bypass-aws-signature-check -> --bypass-s3-signature-check

also rename --verify-ssl-certificate -> --bypass-ssl-certificate-check

#120 in s3 mode, the Content-Length header is now mandatory

perf

in s3 mode, all the uploads are now processed in memory, whatever their size.

v2.0.0-alpha.1

This version brings together important changes regarding the use of ds-proxy in s3 mode.

breaking changes

In s3 mode, requests targeting upstream must now be signed using the Signature SigV4 spec. The server can be launched with the --bypass-aws-signature-check flag to disable this verification.

new features

• --bypass-aws-signature-check flag to disable signature verification for incoming s3 requests.
• --verify-ssl-certificate flag to enable/disable SSL certificate verification for upstream requests (enabled by default).
• PUT requests to upstream now record the x-amz-meta-original-content-length metadata with the unencrypted size of the uploaded file.
• HEAD requests to upstream return the x-amz-meta-original-content-length metadata in the content-length header when possible.

misc

use of the official AWS framework to verify s3 request signatures and sign upstream requests.

v1.0.0 : oldie but goodie

Last release before a major change in the tool's behavior in s3 mode.

This release establishes the ability to use redis to ensure write-once functionality for requests targeting upstream that include the temp_url_expires query parameter.

f03453afad8d13a4aa7176326cad9fed9976701d

f03453a

d035ba3ff39c4c5c93e872c793b58050382d2b31

d035ba3

13948bde51ec32598d06e28fc5aada619bc8db6d

13948bd

a887660de0f7341b943e2d650e925e930ca78466

a887660