chore(deps): update docker.io/restic/rest-server docker tag to v0.12.1 - autoclosed

This MR contains the following updates:

Package	Update	Change
docker.io/restic/rest-server	minor	0.11.0 -> 0.12.1

---

Release Notes

restic/rest-server (docker.io/restic/rest-server)

v0.12.1

Compare Source

============================================

The following sections list the changes in rest-server 0.12.1 relevant to users. The changes are ordered by importance.

Summary

• Fix #​230: Fix erroneous warnings about unsupported fsync
• Fix #​238: API: Return empty array when listing empty folders
• Enh #​217: Log to stdout using the --log - option

Details

• Bugfix #​230: Fix erroneous warnings about unsupported fsync

  Due to a regression in rest-server 0.12.0, it continuously printed WARNING: fsync is not supported by the data storage. This can lead to data loss, if the system crashes or the storage is unexpectedly disconnected. for systems that support fsync. We have fixed the warning.

  https://github.com/restic/rest-server/issues/230 https://github.com/restic/rest-server/pull/231

• Bugfix #​238: API: Return empty array when listing empty folders

  Rest-server returned null when listing an empty folder. This has been changed to returning an empty array in accordance with the REST protocol specification. This change has no impact on restic users.

  https://github.com/restic/rest-server/issues/238 https://github.com/restic/rest-server/pull/239

• Enhancement #​217: Log to stdout using the --log - option

  Logging to stdout was possible using --log /dev/stdout. However, when the rest server is run as a different user, for example, using

  sudo -u restic rest-server [...] --log /dev/stdout

  This did not work due to permission issues.

  For logging to stdout, the --log option now supports the special filename - which also works in these cases.

  https://github.com/restic/rest-server/pull/217

v0.12.0

Compare Source

============================================

The following sections list the changes in rest-server 0.12.0 relevant to users. The changes are ordered by importance.

Summary

• Fix #​183: Allow usernames containing underscore and more
• Fix #​219: Ignore unexpected files in the data/ folder
• Fix #​1871: Return 500 "Internal server error" if files cannot be read
• Chg #​207: Return error if command-line arguments are specified
• Chg #​208: Update dependencies and require Go 1.17 or newer
• Enh #​133: Cache basic authentication credentials
• Enh #​187: Allow configurable location for .htpasswd file

Details

• Bugfix #​183: Allow usernames containing underscore and more

  The security fix in rest-server 0.11.0 (#​131) disallowed usernames containing and underscore "". The list of allowed characters has now been changed to include Unicode characters, numbers, "", "-", "." and "@​".

  https://github.com/restic/rest-server/issues/183 https://github.com/restic/rest-server/pull/184

• Bugfix #​219: Ignore unexpected files in the data/ folder

  If the data folder of a repository contained files, this would prevent restic from retrieving a list of file data files. This has been fixed. As a workaround remove the files that are directly contained in the data folder (e.g., .DS_Store files).

  https://github.com/restic/rest-server/issues/219 https://github.com/restic/rest-server/pull/221

• Bugfix #​1871: Return 500 "Internal server error" if files cannot be read

  When files in a repository cannot be read by rest-server, for example after running restic prune directly on the server hosting the repositories in a way that causes filesystem permissions to be wrong, rest-server previously returned 404 "Not Found" as status code. This was causing confusing for users.

  The error handling has now been fixed to only return 404 "Not Found" if the file actually does not exist. Otherwise a 500 "Internal server error" is reported to the client and the underlying error is logged at the server side.

  https://github.com/restic/rest-server/issues/1871 https://github.com/restic/rest-server/pull/195

• Change #​207: Return error if command-line arguments are specified

  Command line arguments are ignored by rest-server, but there was previously no indication of this when they were supplied anyway.

  To prevent usage errors an error is now printed when command line arguments are supplied, instead of them being silently ignored.

  https://github.com/restic/rest-server/pull/207

• Change #​208: Update dependencies and require Go 1.17 or newer

  Most dependencies have been updated. Since some libraries require newer language features, support for Go 1.15-1.16 has been dropped, which means that rest-server now requires at least Go 1.17 to build.

  https://github.com/restic/rest-server/pull/208

• Enhancement #​133: Cache basic authentication credentials

  To speed up the verification of basic auth credentials, rest-server now caches passwords for a minute in memory. That way the expensive verification of basic auth credentials can be skipped for most requests issued by a single restic run. The password is kept in memory in a hashed form and not as plaintext.

  https://github.com/restic/rest-server/issues/133 https://github.com/restic/rest-server/pull/138

• Enhancement #​187: Allow configurable location for .htpasswd file

  It is now possible to specify the location of the .htpasswd file using the --htpasswd-file option.

  https://github.com/restic/rest-server/issues/187 https://github.com/restic/rest-server/pull/188

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot. Tell Nogweii if it blows up.