% Setting up the document class for a formal letter
\documentclass[11pt,letterpaper]{letter}

% Including essential packages for formatting and compatibility
\usepackage{geometry}
\geometry{letterpaper, margin=0.65in}
\usepackage{parskip} % For paragraph spacing without indentation
\usepackage{enumitem} % For customized lists
\usepackage{hyperref} % For clickable links
\usepackage{microtype} % For improved typography
\usepackage{titlesec} % For section heading customization
\usepackage[utf8]{inputenc} % For proper character encoding

% Configuring font (default Computer Modern)


% Setting up hyperref to avoid conflicts
\hypersetup{
  colorlinks=true,
  linkcolor=blue,
  urlcolor=blue,
  pdfborder={0 0 0}
}

% Customizing section headings to match article style
\titleformat{\section}{\large\bfseries}{\thesection}{1em}{}
\titleformat{\subsection}{\normalsize\bfseries}{\thesubsection}{1em}{}

% Setting up letter-specific details
\signature{Jason Page\\ Laptop Ministry, Chicago\\ laptopministry.org}
\address{The Laptop Ministry\\ Benefactors}
\date{October 19, 2025}

\begin{document}

% Beginning the letter environment
\begin{letter}{To Developers of the Open Source Community}

% Opening the letter
\opening{Dear Developers Community,}

% Introducing the issue with GNOME Keyring
In the world of Linux distributions like Ubuntu and Linux Mint, the GNOME Keyring serves as a built-in credential manager designed to securely store passwords, encryption keys, and other sensitive data. Integrated into desktop environments like GNOME, Cinnamon, and MATE, it handles tasks such as Wi-Fi passwords, SSH keys, and application logins. However, for many users---particularly those who prefer not to use an additional password manager or who rely solely on their web browser's built-in one---the keyring manifests as an unwelcome prompt. This dialog box, demanding a ``keyring password'' upon login or when accessing certain features, feels redundant and intrusive, especially for novice, elderly, or disabled users who find this as a roadblock to accessing their computers functions.

While the keyring aims to enhance security by encrypting stored credentials, its enforced use in default setups has sparked significant debate. This letter outlines methods to disable or bypass the GNOME Keyring in Ubuntu and Linux Mint. More critically, we argue that the necessity of the keyring is overstated, as it alienates vulnerable users and risks driving them away from Linux, undermining the open-source ethos of inclusivity and choice.

\section{The Overplayed Importance of the GNOME Keyring: Prioritizing Accessibility Over Rigid Security}

% Arguing against enforced keyring use
Proponents of the GNOME Keyring argue it provides a critical layer of protection, preventing credential exposure if a device is compromised. However, for users who opt out of dedicated password managers, the keyring adds little meaningful security---it merely introduces an extra hurdle. Many rely exclusively on browser-based password managers (e.g., Google Chrome or Mozilla Firefox), which use their own encryption mechanisms, often tied to a user’s account and persisting across sessions on personal computers. In such cases, the keyring’s role is duplicative at best.

The real issue is the keyring’s impact on accessibility. For novice users, unaccustomed to Linux’s complexities, the prompt can be mistaken for a system error or lead to forgotten passwords, locking them out of essential credentials. Elderly individuals, who may struggle with memory retention or fine motor skills, find an additional dialog box disruptive to simple tasks like checking email or browsing. Disabled users, including those with cognitive impairments or visual challenges, face amplified barriers: screen readers like Orca may not handle the prompt intuitively, and the extra step can exacerbate conditions such as dyslexia or anxiety disorders.

This is not hyperbole---Linux’s accessibility ecosystem, despite improvements, remains less user-friendly for non-technical audiences. Updates to core components like GTK, used in GNOME, have been known to disrupt assistive tools, compounding these challenges. Enforcing the keyring ignores these realities, transforming an empowering open-source operating system into a roadblock. What a moderate user perceives as a ``simple'' security feature becomes an insurmountable obstacle for others, potentially deterring them from adopting Linux in favor of more prompt-free alternatives like Windows or macOS.

In low-risk environments, such as a home laptop used for casual browsing, the keyring’s benefits are marginal compared to its usability costs. Users who avoid storing sensitive data locally or employ two-factor authentication elsewhere gain little from this additional layer. By making the keyring optional rather than mandatory, distributions could foster inclusivity without compromising core security principles. True user empowerment lies in granting individuals the freedom to configure their systems as they see fit.

\section{Disabling the GNOME Keyring in Ubuntu}

% Providing instructions for Ubuntu
Ubuntu, including versions like 24.04 LTS and the upcoming 25.04 (as of 2025), tightly integrates the GNOME Keyring via the Seahorse application (Passwords and Keys). Disabling it involves either setting a blank password to unlock it permanently or removing the service entirely. Note that setting a blank password stores credentials unencrypted, which is suitable for low-risk setups but reduces security. Always back up your data before proceeding.

\subsection{Method 1: Set a Blank Password (Recommended for Most Users)}
\begin{enumerate}[label=\arabic*.]
  \item Open the ``Passwords and Keys'' application by searching in the Activities overview or running \texttt{seahorse} in a terminal.
  \item In the sidebar, locate the ``Login'' keyring (often under ``Passwords'').
  \item Right-click on ``Login'' and select ``Change Password.''
  \item Enter your current keyring password (typically your login password) in the ``Old Password'' field.
  \item Leave the ``New Password'' and ``Confirm'' fields blank, then click ``Continue.'' Confirm any warnings about reduced security.
\end{enumerate}
This method eliminates prompts while preserving functionality for applications that may rely on the keyring.

\subsection{Method 2: Remove Keyring Files or Uninstall the Package (Complete Disable)}
\begin{enumerate}[label=\arabic*.]
  \item Open a terminal (\texttt{Ctrl+Alt+T}).
  \item Navigate to the keyring directory: \texttt{cd \string~/.local/share/keyrings}.
  \item Delete the files: \texttt{rm login.keyring} (or \texttt{rm *} if certain no other files are needed).
  \item For full removal, uninstall the package: \texttt{sudo apt remove gnome-keyring}.
  \item Reboot the system.
\end{enumerate}
If prompts persist in applications like Google Chrome, edit the browser’s desktop file: right-click the Chrome icon, select Properties, go to the Command field, and append \texttt{--password-store=basic}. Test changes, as some network features may require re-entering credentials.

\section{Disabling the GNOME Keyring in Linux Mint}

% Providing instructions for Linux Mint
Linux Mint, built on Ubuntu and using Cinnamon or MATE desktops (e.g., Mint 22 based on Ubuntu 24.04 in 2025), follows a similar process, accessible via the menu or Synaptic Package Manager.

\subsection{Method 1: Set a Blank Password}
\begin{enumerate}[label=\arabic*.]
  \item Go to Menu \textgreater{} Accessories \textgreater{} Passwords and Keys (or search for it).
  \item Right-click the ``Login'' keyring.
  \item Select ``Change Password.''
  \item Enter your current password, leave the new password fields blank, and confirm.
\end{enumerate}
This is the simplest approach, maintaining system integrity.

\subsection{Method 2: Delete Files and Remove Package}
\begin{enumerate}[label=\arabic*.]
  \item Open File Manager and navigate to \texttt{/home/yourusername/.local/share/keyrings}.
  \item Delete the files inside (e.g., \texttt{login.keyring} and \texttt{user.keystore}).
  \item Launch Synaptic Package Manager (install if needed: \texttt{sudo apt install synaptic}).
  \item Search for \texttt{gnome-keyring-pkcs11}, mark it for removal, and apply changes.
  \item Reboot the system.
\end{enumerate}
For browser-specific issues, apply the \texttt{--password-store=basic} flag as described for Ubuntu.

\section{A Plea for an Optional Keyring}

% Addressing the issue of updates and making the case for optional keyring
Despite these efforts, system updates in Ubuntu and Linux Mint often reinstate the GNOME Keyring as the default password manager, reintroducing unwanted prompts. Permanently disabling it requires advanced steps---such as marking packages as held (\texttt{sudo apt-mark hold gnome-keyring}) or editing PAM configurations (\texttt{/etc/pam.d/gdm-password})---that are inaccessible to novice, elderly, or disabled users. This persistent reinstatement undermines the open-source ethos of user choice and accessibility.

We urge developers of GNOME, Cinnamon, MATE, and other desktop environments to make the keyring an optional feature, not a compulsory one. The open-source community has long positioned Linux as a refuge from the rigid, user-hostile practices of proprietary systems like Microsoft Windows, which often impose features without consent. Mandating the keyring mirrors this compulsion, creating barriers for users who seek simplicity, particularly those new to Linux or with cognitive, visual, or motor impairments. A single unexpected prompt can render a system inaccessible, driving away the very users we aim to welcome.

By making the keyring opt-in, Linux distributions can uphold the principle of freedom, ensuring platforms are inclusive and adaptable to diverse needs, not rigid systems that confuse and alienate. Let us build an open-source ecosystem that empowers all users, not just the technically adept.

\section{Conclusion: Empowering Users Through Simplicity}

% Concluding with a call to action
Disabling the GNOME Keyring restores a seamless experience for users who find it unnecessary, but the need for ongoing vigilance against updates highlights a broader issue. By advocating against its enforced use, we underscore a critical need in Linux development: balancing security with accessibility. For novices, the elderly, and disabled users, every extra prompt is a potential deal-breaker, emphasizing why options like browser-only password management should be respected without judgment. If Linux aims to be for everyone, it must prioritize inclusivity by eliminating mandatory features that overcomplicate the basics. We call on the community to implement these changes, ensuring Linux remains a welcoming environment for all.

\closing{Sincerely,}
\end{letter}

\end{document}