Borgamtic asks 3 times for the archive password during a backup #351

New Issue

Closed

opened 2020-08-10 17:15:55 +00:00 by SergiyKolesnikov · 3 comments

SergiyKolesnikov commented 2020-08-10 17:15:55 +00:00

Copy Link

What I'm trying to do and why

During a backup borgmatic asks for the archive password 3 times: for "Pruning archives", "Creating archive", and "Starting archive consistency check..." steps.

I am not sure if it is by design. If not, it would be much more conviniet to enter the password only once.

Steps to reproduce (if a bug)

Init with:

sudo borgmatic init --encryption repokey

Run backup with:

sudo borgmatic

Expected behavior (if a bug)

Ask for the archive password only once.

Environment

borgmatic version: 1.5.1
borgmatic installation method: Debian package
Borg version: 1.1.13
Python version: 3.8
operating system and version: Debian testing bullseye

#### What I'm trying to do and why During a backup borgmatic asks for the archive password 3 times: for "Pruning archives", "Creating archive", and "Starting archive consistency check..." steps. I am not sure if it is by design. If not, it would be much more conviniet to enter the password only once. #### Steps to reproduce (if a bug) Init with: ``` sudo borgmatic init --encryption repokey ``` Run backup with: ``` sudo borgmatic ``` #### Expected behavior (if a bug) Ask for the archive password only once. #### Environment **borgmatic version:** 1.5.1 **borgmatic installation method:** Debian package **Borg version:** 1.1.13 **Python version:** 3.8 **operating system and version:** Debian testing bullseye

witten commented 2020-08-10 17:20:30 +00:00

Owner

Copy Link

Thank you for filing this! If you are referring to the encryption password, then my recommendation is to put the password in borgmatic's configuration file with the encryption_passphrase option. Or, if you prefer, you can run an external program to collect the passphrase with the encryption_passcommand option.

Finally, if you really don't want your passphrase sitting in borgmatic's configuration file, you can use the BORG_PASSPHRASE environment variable instead.

See the configuration reference for more information.

Please let me know if that does it for you!

Thank you for filing this! If you are referring to the encryption password, then my recommendation is to put the password in borgmatic's configuration file with the `encryption_passphrase` option. Or, if you prefer, you can run an external program to collect the passphrase with the `encryption_passcommand` option. Finally, if you really don't want your passphrase sitting in borgmatic's configuration file, you can use the `BORG_PASSPHRASE` environment variable instead. See the [configuration reference](https://torsion.org/borgmatic/docs/reference/configuration/) for more information. Please let me know if that does it for you!

witten added the

question / support

label 2020-08-10 17:20:38 +00:00

SergiyKolesnikov commented 2020-08-10 20:22:07 +00:00

Author

Copy Link

Thanks for the super quick answer! Now I see that the same info is available in the docs.

I think, I didn't pay a proper attention to it because the section starts with "Note that if you plan to run borgmatic on a schedule with cron". I planned to run borgmatic manually, so probably I just skipped the section. Maybe rewording that first sentence would help to avoid the confusion.

In my case, I am the only user with the root access and the disk is encrypted, so I will go with the easiest solution and put the encryption passpprase into the borgmatic's configuration file.

Thanks for the super quick answer! Now I see that the same [info is available in the docs](https://torsion.org/borgmatic/docs/how-to/set-up-backups/#encryption). I think, I didn't pay a proper attention to it because the section starts with "Note that if you plan to run borgmatic on a schedule with cron". I planned to run borgmatic manually, so probably I just skipped the section. Maybe rewording that first sentence would help to avoid the confusion. In my case, I am the only user with the root access and the disk is encrypted, so I will go with the easiest solution and put the encryption passpprase into the borgmatic's configuration file.

witten commented 2020-08-10 21:44:22 +00:00

Owner

Copy Link

Glad to hear that does it! I'll definitely reword that section for clarity. I appreciate the feedback.

Glad to hear that does it! I'll definitely reword that section for clarity. I appreciate the feedback.

witten closed this issue 2020-08-10 21:44:22 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#351

No description provided.