代码拉取完成，页面将自动刷新
The Python keyring library provides an easy way to access the system keyring service from python. It can be used in any application that needs safe password storage.
These recommended keyring backends are supported:
Other keyring implementations are available through Third-Party Backends.
On Linux, the KWallet backend relies on dbus-python, which does not always install correctly when using pip (compilation is needed). For best results, install dbus-python as a system package.
macOS keychain supports macOS 11 (Big Sur) and later requires Python 3.8.7 or later with the "universal2" binary. See #525 for details.
The basic usage of keyring is pretty simple: just call
keyring.set_password and keyring.get_password:
>>> import keyring
>>> keyring.set_password("system", "username", "password")
>>> keyring.get_password("system", "username")
'password'
Keyring supplies a keyring command which is installed with the
package. After installing keyring in most environments, the
command should be available for setting, getting, and deleting
passwords. For more usage information, invoke with no arguments
or with --help as so:
$ keyring --help $ keyring set system username Password for 'username' in 'system': $ keyring get system username password
The command-line functionality is also exposed as an executable package, suitable for invoking from Python like so:
$ python -m keyring --help $ python -m keyring set system username Password for 'username' in 'system': $ python -m keyring get system username password
The python keyring lib contains implementations for several backends. The
library will attempt to
automatically choose the most suitable backend for the current
environment. Users may also specify the preferred keyring in a
config file or by calling the set_keyring() function.
The configuration is stored in a file named "keyringrc.cfg" found in a platform-specific location. To determine where the config file is stored, run the following:
python -c "import keyring.util.platform_; print(keyring.util.platform_.config_root())"
Some keyrings also store the keyring data in the file system. To determine where the data files are stored, run:
python -c "import keyring.util.platform_; print(keyring.util.platform_.data_root())"
To specify a keyring backend, set the default-keyring option to the
full path of the class for that backend, such as
keyring.backends.OS_X.Keyring.
If keyring-path is indicated, keyring will add that path to the Python module search path before loading the backend.
For example, this config might be used to load the
SimpleKeyring from the simplekeyring module in
the ./demo directory (not implemented):
[backend] default-keyring=simplekeyring.SimpleKeyring keyring-path=demo
In addition to the backends provided by the core keyring package for the most common and secure use cases, there are additional keyring backend implementations available for other use cases. Simply install them to make them available:
The interface for the backend is defined by keyring.backend.KeyringBackend.
Every backend should derive from that base class and define a priority
attribute and three functions: get_password(), set_password(), and
delete_password(). The get_credential() function may be defined if
desired.
See the backend module for more detail on the interface of this class.
Keyring employs entry points to allow any third-party package to implement
backends without any modification to the keyring itself. Those interested in
creating new backends are encouraged to create new, third-party packages
in the keyrings namespace, in a manner modeled by the keyrings.alt
package. See the
setup.cfg file
in that project for hints on how to create the requisite entry points.
Backends that prove essential may be considered for inclusion in the core
library, although the ease of installing these third-party packages should
mean that extensions may be readily available.
To create an extension for Keyring, please submit a pull request to have your extension mentioned as an available extension.
Keyring additionally allows programmatic configuration of the
backend calling the api set_keyring(). The indicated backend
will subsequently be used to store and retrieve passwords.
To invoke set_keyring:
# define a new keyring class which extends the KeyringBackend
import keyring.backend
class TestKeyring(keyring.backend.KeyringBackend):
"""A test keyring which always outputs the same password
"""
priority = 1
def set_password(self, servicename, username, password):
pass
def get_password(self, servicename, username):
return "password from TestKeyring"
def delete_password(self, servicename, username):
pass
# set the keyring for keyring lib
keyring.set_keyring(TestKeyring())
# invoke the keyring lib
try:
keyring.set_password("demo-service", "tarek", "passexample")
print("password stored successfully")
except keyring.errors.PasswordSetError:
print("failed to store password")
print("password", keyring.get_password("demo-service", "tarek"))
In many cases, uninstalling keyring will never be necessary. Especially on Windows and macOS, the behavior of keyring is usually degenerate, meaning it will return empty values to the caller, allowing the caller to fall back to some other behavior.
In some cases, the default behavior of keyring is undesirable and it would be preferable to disable the keyring behavior altogether. There are several mechanisms to disable keyring:
PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring
in the environment, and the Null (degenerate) backend
will be used. This approach affects all uses of Keyring where
that variable is set.keyring --disable or python -m keyring --disable.
This approach affects all uses of keyring for that user.Keyring provides a mechanism to alter the keyring's behavior through
environment variables. Each backend implements a
KeyringBackend.set_properties_from_env, which
when invoked will find all environment variables beginning with
KEYRING_PROPERTY_{NAME} and will set a property for each
{NAME.lower()} on the keyring. This method is invoked during
initialization for the default/configured keyring.
This mechanism may be used to set some useful values on various keyrings, including:
The following is a complete transcript for installing keyring in a virtual environment on Ubuntu 16.04. No config file was used:
$ sudo apt install python3-venv libdbus-glib-1-dev
$ cd /tmp
$ pyvenv py3
$ source py3/bin/activate
$ pip install -U pip
$ pip install secretstorage dbus-python
$ pip install keyring
$ python
>>> import keyring
>>> keyring.get_keyring()
<keyring.backends.SecretService.Keyring object at 0x7f9b9c971ba8>
>>> keyring.set_password("system", "username", "password")
>>> keyring.get_password("system", "username")
'password'
It is possible to use the SecretService backend on Linux systems without X11 server available (only D-Bus is required). In this case:
Install the GNOME Keyring daemon.
Start a D-Bus session, e.g. run dbus-run-session -- sh and run
the following commands inside that shell.
Run gnome-keyring-daemon with --unlock option. The description of
that option says:
Read a password from stdin, and use it to unlock the login keyring or create it if the login keyring does not exist.
When that command is started, enter a password into stdin and
press Ctrl+D (end of data). After that, the daemon will fork into
the background (use --foreground option to block).
Now you can use the SecretService backend of Keyring. Remember to run your application in the same D-Bus session as the daemon.
It is possible to use keyring with the SecretService backend in Docker containers as well. All you need to do is install the necessary dependencies and add the --privileged flag to avoid any Operation not permitted errors when attempting to unlock the system's keyring.
The following is a complete transcript for installing keyring on a Ubuntu 18:04 container:
docker run -it -d --privileged ubuntu:18.04
$ apt-get update
$ apt install -y gnome-keyring python3-venv python3-dev
$ python3 -m venv venv
$ source venv/bin/activate # source a virtual environment to avoid polluting your system
$ pip3 install --upgrade pip
$ pip3 install keyring
$ dbus-run-session -- sh # this will drop you into a new D-bus shell
$ echo 'somecredstorepass' | gnome-keyring-daemon --unlock # unlock the system's keyring
$ python
>>> import keyring
>>> keyring.get_keyring()
<keyring.backends.SecretService.Keyring object at 0x7f9b9c971ba8>
>>> keyring.set_password("system", "username", "password")
>>> keyring.get_password("system", "username")
'password'
The keyring lib has a few functions:
get_keyring(): Return the currently-loaded keyring implementation.get_password(service, username): Returns the password stored in the
active keyring. If the password does not exist, it will return None.get_credential(service, username): Return a credential object stored
in the active keyring. This object contains at least username and
password attributes for the specified service, where the returned
username may be different from the argument.set_password(service, username, password): Store the password in the
keyring.delete_password(service, username): Delete the password stored in
keyring. If the password does not exist, it will raise an exception.In all cases, the parameters (service, username, password)
should be Unicode text.
The keyring lib raises the following exceptions:
keyring.errors.KeyringError: Base Error class for all exceptions in keyring lib.keyring.errors.InitError: Raised when the keyring cannot be initialized.keyring.errors.PasswordSetError: Raised when the password cannot be set in the keyring.keyring.errors.PasswordDeleteError: Raised when the password cannot be deleted in the keyring.Python keyring lib is an open community project and eagerly welcomes contributors.
Available as part of the Tidelift Subscription.
This project and the maintainers of thousands of other packages are working with Tidelift to deliver one enterprise subscription that covers all of the open source you use.
To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.
Each built-in backend may have security considerations to understand
before using this library. Authors of tools or libraries utilizing
keyring are encouraged to consider these concerns.
As with any list of known security concerns, this list is not exhaustive. Additional issues can be added as needed.
keyring from that same Python executable without the operating
system prompting the user for a password. To cause any specific
secret to prompt for a password every time it is accessed, locate
the credential using the Keychain Access application, and in
the Access Control settings, remove Python from the list
of allowed applications.This project makes use of automated releases and continuous integration. The simple workflow is to tag a commit and push it to Github. If it passes tests in CI, it will be automatically deployed to PyPI.
Other things to consider when making a release:
Tests are continuously run in Github Actions.
To run the tests locally, install and invoke tox.
The project was based on Tarek Ziade's idea in this post. Kang Zhang initially carried it out as a Google Summer of Code project, and Tarek mentored Kang on this project.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
马建仓 AI 助手