You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Schweber Thanks for opening the issue! Unfortunately I cannot reproduce the issue. If put "test " (without ", of course) in the password file it works exactly like putting it in the config profile or using --password "test ".
The logic of reading the password from the file is very simple:
read the whole file
if it ends with "\r\n" (windows newline), remove that newline and use the remaining as password.
if it ends with "\n" (unix newline), remove that newline and use the remaining as password.
else use the complete content as password
What does your password file exactly contain? "password " (including the ")? In this case, you have to remove the ".
Or could it be that your file.txt contains a newline followed by the spaces?
aawsome
added
C-question
Category: Further information is requested
and removed
S-triage
Status: Waiting for a maintainer to triage this issue/PR
labels
Mar 11, 2024
The file just contained one line with the password (without ", that was misleading in my post). gpg was content to use it as a passphrase-file but rustic wasn't for some reason.
After reading your post i added an empty newline and it worked from then on. I then removed the empty newline again and it still works with rustic, so i'm a bit confused.
Mhh - could be that there was some unprintable character at the end which you removed by inserting and removing the newline...
Anyway, as it seems there is nothing to reproduce, so I'm closing this issue.
Feel free to open again if you discover something new!
I tried
The file just contains
"password "
(2 spaces after password) but rustic tells me that the password is not correct. If i useit works fine (also 2 spaces after password). It appears to me that the spaces at the end are not properly recognized.
Can you reproduce this?
The text was updated successfully, but these errors were encountered: