summary refs log tree commit diff
path: root/emacs
diff options
context:
space:
mode:
authornoa2024-09-07 08:47:16 +0000
committernoa2024-09-07 08:47:16 +0000
commit3be0e4987f76ccc5d3fe082a31eaeb55dae0141a (patch)
treebadc34af064945e0d1c6e8f9b21f4f72ae2109ba /emacs
parentc30bc2891807c7e46d255fe7f9854b8cf9dbad81 (diff)
Remove unused password management section
Diffstat (limited to 'emacs')
-rw-r--r--emacs/init.el18
1 files changed, 0 insertions, 18 deletions
diff --git a/emacs/init.el b/emacs/init.el
index 3a931b7..b261c53 100644
--- a/emacs/init.el
+++ b/emacs/init.el
@@ -1245,24 +1245,6 @@ The misspelled word is taken from OVERLAY.  WORD is the corrected word."
                   (buffer-substring (mark) (point)))
                 "\n\n"))
 
-;;; Password management
-;; I mostly don't use emacs for passage management.  Instead i use the wonderful [[https://keepassxc.org/][keepassxc]].  Keepassxc has many great features i make use of, including one time passwords, an ssh agent, and checking if my password appears in leaks.
-
-;; I used keepassxc for over a year, before deciding to throw the towel in and move to bitwarden for the convenience of having my passwords easily on multiple devices.  It turns out that things i took for granted with keepassxc, like not having to pay for one time password support, the ssh agent, browser integration that worked well all the time, and a decent desktop application, were not present in bitwarden.  Instead of running back to bitwarden, i moved again, first to pass, the so-called standard unix password manager, and then to passage, which does the same thing but uses age encryption instead of the fire-engine-on-fire that is gpg.
-
-;; The motivation for this move was because i wanted to start using a hardware token as extra protection for the passwords.  But sadly, the infrastructure around this solution just isn't there and it became a pile of jank.  I stopped accessing my email and xmpp from my computer, because it felt like too much of a headache.
-
-;; And so i'm back with keepassxc.  Luckily keepassxc supports the secret service api, and so does emacs's very own auth-source package, so everything should be perfect.  Right?
-
-;; Not quite.  The keys that auth-source expects don't quite align with the keys that keepassxc has.  So any passwords i want emacs to be able to easily deal with have to be moved around a little.  Luckily the passwords key itself is just where it should be, but i had to go the advanced options in my keepassxc entry and add things in the :user, :host, and :port slots.  I probably won't be updating these very often, so it's not a big deal.  But i'm writing it here because otherwise i will forget.
-
-;; (start-process-shell-command "keepassxc" nil "keepassxc")
-
-(require 'secrets)
-;; (secrets-open-session)
-(setopt auth-sources '("secrets:Passwords"))
-(auth-source-forget-all-cached)
-
 ;;; Other
 
 (setopt confirm-kill-emacs 'y-or-n-p)