L2CPBG

Hi Michael.

Thanks a lot for your feedback!

Michael Gruth wrote:

great performance, yesterday's request will be fullfilled today.

Quite thanks for the flowers, but for sure it highly depends of my other workload ;-)

Everything was working as described,

Cool!

if you like to optimize it, then you should add the password automaticly into the config file, but just a feature, will work as it is,

For sure, would be more comfortable, but I fear about multiple editors (L2CPBG + User) of one file. In addition it could become tricky to place it to the correct position.
Once the Webfrontend (1.0) is live, functionality like this become quite more comfortable.

but maybe you should add a comment to your readme file that the password needs to be copied into the config file to work.

Good point!!
The readme currently point out:

pass : Related user password. If you don't like to store your CardDAV-Server password in clear-text here, you've also the possibility to use the AES-256 encrypted variant of the password here. Please check l2cpbg's command line option --encryptPassword via l2cpbg --help. If you already stored the encrypted password variant here, you can also check/validate it with command line option --testDavPassword.

I changed the relevant output of command-line option --help now to:

--encryptPassword=<clear text password>
        Encrypt the given clear-text-password to get a config sample for
        manual copy as [dav] pass="<encrypted password>"

and the output of command-line option --encryptPassword to:

Password encryption succeed. Copy/replace the following within your config:
[dav]
pass="[AES256]..."

Is it clear enough?

The new readme explanation is quite perfect.

Take care
Michael

Am 04.11.2021 um 14:03 schrieb Jörg Ebeling: