Skip to content

Incorrect file permissions after backup via sftp #5487

@brad2014

Description

@brad2014

Output of restic version

restic 0.18.0 compiled with go1.24.1 on linux/amd64

What backend/service did you use to store the repository?

sftp

Problem description / Steps to reproduce

Similar to #4447, but affecting backup files.

"restic backup" is creating data files with user (and for my case group) read-write permission when the repo is accessed via sftp:restic@repohost, while the local files (on repohost) are all read only.

For example, the first of these data files was created during a local backup (as root on repohost), and the other during a sftp backup (to sftp:restic@repohost:...), both to the same repo.

1887814808    628 -r--r-----   1 root     restic     640063 Sep  5 22:39 ./index/5bebf47942e1d47fd25453f42c3d53dcd43959cc4898e7f27230307b9ea93405
1612200155     28 -rw-rw----   1 restic   restic      26374 Sep  5 22:58 ./index/9587e9696220eda5f2611ca508e6e5b5ac7c27faca544ee84e96f66434abb61c

Expected behavior

All repo files uploaded by sftp should have the same permission as if the repo file was created by a local backup.

Actual behavior

Repo files have read-write permission instead of read-only.

Do you have any idea what may have caused this?

Probably something similar to #4447.

Did restic help you today? Did it make you happy in any way?

restic makes me happy every day (at 3am).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions