When creating a new configuration file, always ask for ther user's
password unless it is found in the system keyring (instead of using the
SecretCache object to ask for the password later), and save that
password in the system keyring (if possible) or in the configuration
file.
This is likely what most users would expect. An user who doesn't want
her password to be written in the configuration file can still create or
edit the configuration file herself.
Rename the 'tls_no_check' configuration option to 'tls_verify' and
change its meaning to accept either:
- 'no', 'off', 'disabled', or 'false' to disable certificate validation;
- 'yes', 'on', 'enabled', or 'true' to enable validation against common
public CAs (this is purely for completeness, as it is already the
default behaviour);
- a pathname pointing to a custom CA bundle.
closes#8
"Insecure SSL" is a bit vague and could mean other things than disabled
certificate verification (e.g., it could mean use of obsolete SSL
versions or algorithms). So rename the 'allow_insecure_ssl' variables to
be more explicit.
Similarly, update the inline help for the --insecure option to more
explicitly state the purpose of the option.
If the configuration file does not contain a password and the keyring
module is not available, pbl fails with UnboundLocalError instead of
fallbacking to asking the user for her password (or running a
password_command), because the password variable has not been assigned.
closes#6
I've been using Pebble on a daily basis for more than 2 years now,
let's make a jump toward a future stable 1.0.0 release. Bump the
version number to 0.9.0, change development status to "beta" and
remove the warning about using write access "at your own risks".
In case click-shell's upstream does not fix the incompatibility with
Click 8+, we bundle our fixed version of the module. That version is
also stripped of all the Python 2 compatibility stuff.
Instead of only storing the vault's GUID in the cache, store all
the metadata returned by server.find_vault (as JSON). This notably
includes the 'challenge_password' field, that we can use to verify a
password (instead of using the first credential found in the vault).
Also do not cache anything (not even the vault's GUID or other
metadata) when we are under `nocache: true`.
Click 8.0.0 introduced some changes that broke click-shell. Until the
latter is fixed, we still try to import it, but allow the program to
continue running (without the shell feature) if it fails.
Wrap the call to the main function into a try/except block to catch
all expected errors and exit with a clean error message.
We only catch our own exception class. All other exceptions should
be catched deeper in the code and wrapped into a util.Error exception.
Set the umask to 0077 as soon as the program is started so that no
file (config or data file) is ever written with any permission for any
user other than the owner.
Add a command to create or edit the configuration file used by Pebble.
That command is automatically invoked if Pebble is called when no
configuration file exists.
Use the Python keyring module to query the user's system keyring
for the server password, if no password is specified in the
configuration file.
Tested on GNU/Linux with GNOME Keyring and Mac OS X with Apple
Keychain.
Closes#2.
Add a --force option to the verify command to empty the passphrase
cache. This allows the user to try to enter another passphrase without
having to exit the shell and start it again.
