HEX
Server: Apache/2.4.41 (Ubuntu)
System: Linux ip-172-31-42-149 5.15.0-1084-aws #91~20.04.1-Ubuntu SMP Fri May 2 07:00:04 UTC 2025 aarch64
User: ubuntu (1000)
PHP: 7.4.33
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
Upload Files
File: //proc/self/root/usr/share/doc/gnome-keyring/README.Debian
gnome-keyring for Debian
========================

 Password caching
 ----------------
GNOME keyring caches the passwords in memory, and when asked to, it will 
store them on disk (in .gnome2/keyrings). They are encrypted with the
AES128 cipher, using a master password as key.

 Login keyring
 -------------
If you use GDM, and libpam-gnome-keyring is installed, the GNOME keyring 
daemon is spawned directly at the time of authentication, and the 
keyring named "login" is unlocked. This keyring uses the authentication 
token as a master password.

Otherwise, it is launched by the session manager, and you will be asked 
for a password for the "Default" keyring.

If you change your authentication password (using passwd or 
gnome-control-center for example), the password for the login keyring
should be updated automatically.

 SSH agent
 ---------
The GNOME keyring includes the functionality of the SSH agent, and it
can break some setups, especially if ssh-agent is started by hand.
You can disable it by removing the gnome-keyring-ssh element from the
startup applications.