Maybe move these closures to separate function?

What is the best file to add the function so that both key.rs and init.rs can access

crates/rustic_core/src/password.rs, but I'm not sure

First, this PR IMO doesn't allow to confirm the password, but enforces it.
I personally wouldn't need that, but if you think this is a worthwhile addition, I'm open for it ;-)

About the place: Please not in rustic_core. This crate provides core functionality to access repositories and perform operations on it. All UI topics should stay outside - and this is for sure just a UI topic!

@istudyatuni @aawsome what do you think about having a function called prompt_password_twice in rustic/src/helpers that both init.rs and key.rs can call

I'm afraid to make those decisions in this project 😁

As discussed @Aderemi-Adesada on discord, I also think that the best idea is to replace rpassword with dialoguer which already implements this functionality.

rpassword has been replaced with dialoguer in init.rs and key.rs when prompting for new key

rpassword have been removed completely and src/command/key.rs now uses read_password_from_reader as used in crates/rustic_core/src/repository.rs

@Aderemi-Adesada there are syntax errors in lib.rs - can you have a look at it?

syntax error

I will fix that right now

@aawsome syntax error have been fixed

Can you please rebase to main and squash all commits instead of re-merging master back into your branch? That will keep commit history clean. Thanks a lot!

Oh, clicked wrong - actually wanted to run the tests.
Anyway, we'll see in the CI. Thanks a lot @Aderemi-Adesada - looks good to me!

You are welcome