Suggest a data classification project to consider a need to know of your documentation and a risk assessment be performed on keeping seemingly sensitive documentation on a public server. Granting of course, that if someone is on your system with a UID that can perform backups, you have other big problems, but why make this problem bigger and easier to exploit? <rhetorical>
Defense in depth makes the blackhat work for every level. Also, good job for testing restores. Now is the time to find these problems.
On 14.08.2024 16:34, Jeffrey Walton wrote:
>>
>> On 14.08.2024 16:04, Jeffrey Walton wrote:
>>> On Wed, Aug 14, 2024 at 7:17 AM edgar.soldin--- via Duplicity-talk
>>>>
>>>> On 14.08.2024 06:30, Jeffrey Walton via Duplicity-talk wrote:
>>>>> [...]
>>>>> How can I get duplicity to recognize what is on our backup server?
>>>>
>>>> looks like it does not find any backups. please post a file listing of "sftp://<redacted>/". if it's big you may pastebin it.
>>>
>>> This was my mistake. I did not specify the remote directory:
>>>
>>> "sftp://<redacted>/<remote_dir>"
>>>
>>> (It is a gap in our internal documentation for a restore).
>>
>> is it? would you mind to point me to the documentation in question so we may fix it please. ..ede
>
sunny regards.. ede
_______________________________________________
Duplicity-talk mailing list