<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  
  
  <channel>
    <title>chrisjrob: password</title>
    <link>https://chrisjrob.com</link>
    <atom:link href="https://chrisjrob.com/tag/password/feed/index.xml" rel="self" type="application/rss+xml" />
    <description>GNU Linux, Perl and FLOSS</description>
    <language>en-gb</language>
    <pubDate>Fri, 13 Feb 2026 17:22:31 +0000</pubDate>
    <lastBuildDate>Fri, 13 Feb 2026 17:22:31 +0000</lastBuildDate>
    
    <item>
      <title>Moving From Keepassx To CLI Password Safe Using Vim And GPG</title>
      <link>https://chrisjrob.com/2011/05/04/moving-from-keepassx-to-cli-password-safe-using-vim-and-gpg/</link>
      <pubDate>Wed, 04 May 2011 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2011/05/04/moving-from-keepassx-to-cli-password-safe-using-vim-and-gpg</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/vim_logo.png" align="right" alt="Featured Image">
         
         <p>The more that I work from the command line, the more of a nuisance I
find it that all my passwords are in
<a href="http://www.keepassx.org" title="KeePassX">KeePassX</a> - an excellent GUI
application.</p>

<p>For some time I have intended moving to pwsafe, but am put off by the
time it will take to migrate the data. An alternative is to export the
KeePassX data into an encrypted text file and use the <code class="language-plaintext highlighter-rouge">gnupg.vim</code> Vim
plugin to read and edit it. This post describes how to accomplish this
in a very few steps.</p>

<!--more-->

<p>I first ran KeePassX and deleted the backup group (as I did not wish to
export all my previous generations of passwords). I then exported the
contents to a text file named “passwords” (you could be more
imaginative/secure if you wish!). Then I followed 
<a href="http://awesometrousers.net/post/vim-with-gpg-file-encryption/">these instructions</a>
to create a GPG secured file:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ gpg -c --cipher-algo AES256 passwords
</code></pre></div></div>

<p>And enter your secure passphrase twice. You should now have a new
password file “passwords.gpg”. You can now remove the plain text
version:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ shred --remove passwords
</code></pre></div></div>

<p>In order to edit/view the new passwords.gpg file, we need the Vim
gnupg.vim plugin, which is available in the debian vim-scripts package:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install vim-scripts
</code></pre></div></div>

<p>Then edit <code class="language-plaintext highlighter-rouge">/etc/vim/vimrc.local</code> to add the following line:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>set runtimepath+=/usr/share/vim-scripts/
</code></pre></div></div>

<p>This will import all of the vim-scripts plugins, which may not be what
you want. Alternatively you could probably just copy or perhaps symlink
the gnupg.vim plugin to your <code class="language-plaintext highlighter-rouge">~/.vim/plugin/</code> folder.</p>

<p>And that is it - now whenever you wish to view or edit your passwords
you simply type:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ vim passwords.gpg
</code></pre></div></div>

<p>This will prompt you for your password and open the file.</p>

<p>Initially I found this gave errors in relation to <code class="language-plaintext highlighter-rouge">exuberant ctags</code>,
which I suspect is related to vim-scripts and not to gnupg.vim and is
doubtless a feature of the way I have just pulled in all of the
vim-scripts. One option (and what I did) is just to install
exuberant-ctags as follows:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install exuberant-ctags
</code></pre></div></div>

<p>Now I just have to format passwords.gpg into something a bit more
structured, perhaps with Vim folding configured.</p>

<p>And if you are looking for a way to create passwords, the pwgen is one
option - it offers a selection of fairly memorable passwords from which
to choose.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install pwgen
</code></pre></div></div>

<p>There are some concerns with this approach - anyone can read your
passwords over your shoulder - if you work with others you might be
better off with something like pwsafe. Also some users are concerned
that the contents of the file might be written to memory, although I
believe this is not the case, you should satisfy yourself as to the
security of this approach, as I am certainly not qualified to advise you
on this aspect.</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>LTSP | LDM password expiry problem</title>
      <link>https://chrisjrob.com/2008/06/23/ldm-password-expiry-problem/</link>
      <pubDate>Mon, 23 Jun 2008 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2008/06/23/ldm-password-expiry-problem</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/ltsp_logo.png" align="right" alt="Featured Image">
         
         <p>I have had my first user’s password expire since our <a href="/2010/06/25/ltsp5-upgrade/">LTSP5 Upgrade</a>.</p>

<ol>
  <li>User enters username and hits enter</li>
  <li>User enters password and hits enter</li>
  <li>LDM tells user password has expired enter new password</li>
  <li>User enters new password and hits enter</li>
  <li>LDM tells user to verify password</li>
  <li>User enters new password again and hits enter</li>
</ol>

<!--more-->

<p>And then it enters a crazy loop where it just continually prompts for the password.  If you reboot the client you start from the beginning again, so clearly the password change has not been accepted.  I confidently told user that he had obviously entered his password incorrectly - I then rebooted the client and did exactly the same myself.  I believe this could be a bug, and I suspect it may be related to the following thread:</p>

<ul>
  <li><a href="http://marc.info/?t=121069447400001&amp;r=1&amp;w=2">ldm problems with debian etch</a></li>
</ul>


       ]]>
      </description>
    </item>
    
  </channel> 
</rss>
