<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Keepass on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/keepass/</link>
    <description>Recent content in Keepass on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Apr 2026 08:26:08 +0200</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/keepass/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrate From Pass to KeepassXC</title>
      <link>https://janikvonrotz.ch/2026/04/13/migrate-from-pass-to-keepassxc/</link>
      <pubDate>Mon, 13 Apr 2026 08:26:08 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2026/04/13/migrate-from-pass-to-keepassxc/</guid>
      <description>&lt;p&gt;In 2017 I &lt;a href=&#34;https://janikvonrotz.ch/2017/07/24/migrate-keepass-to-pass/&#34;&gt;migrated from KeePass to Pass&lt;/a&gt; and now migrated back to KeePassXC. For almost 9 years I was a happy &lt;a href=&#34;https://www.passwordstore.org/&#34;&gt;pass&lt;/a&gt; user. It still does a very good job and keeping password management simple. But setting up pass on a new device was always a bit difficult.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Store Passkeys in KeePassXC</title>
      <link>https://janikvonrotz.ch/2025/07/04/store-passkeys-keepassxc/</link>
      <pubDate>Fri, 04 Jul 2025 08:04:42 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2025/07/04/store-passkeys-keepassxc/</guid>
      <description>&lt;hr&gt;&#xA;&lt;p&gt;The goal of Passkeys is to replace passwords.&lt;/p&gt;&#xA;&lt;p&gt;The idea is that instead of remembering a password and entering it to access your account, you own a device that generates a password for you.&lt;/p&gt;&#xA;&lt;p&gt;Remembering is replaced with Owning.&lt;/p&gt;&#xA;&lt;p&gt;In this post, I&amp;rsquo;ll give an example of such a device and how you can create and store a Passkey securely.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Store and load SSH keys in KeePass</title>
      <link>https://janikvonrotz.ch/2024/10/18/store-and-load-ssh-keys-in-keepass/</link>
      <pubDate>Fri, 18 Oct 2024 11:03:41 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2024/10/18/store-and-load-ssh-keys-in-keepass/</guid>
      <description>&lt;p&gt;I learned about this KeePass feature way too late. With KeePass you can store and load your SSH keys in a secure and encrypted way. No more worrying about your SSH private key being exposed or accessed on your local machine.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Migrate KeePass to Pass</title>
      <link>https://janikvonrotz.ch/2017/07/24/migrate-keepass-to-pass/</link>
      <pubDate>Mon, 24 Jul 2017 10:05:46 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2017/07/24/migrate-keepass-to-pass/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m using &lt;a href=&#34;http://keepass.info/&#34;&gt;KeePass&lt;/a&gt; for a few years now. It always has been the password manager of my choice.&#xA;Currently I&amp;rsquo;m using KeePass on my Mac and Windows connected to the same database file. The KeePass database file is stored in a OneDrive folder, encrypted with a password and keyfile, which is stored in the &lt;a href=&#34;https://keybase.io&#34;&gt;Keybase&lt;/a&gt; filesystem. This setup gives me maximum security and portability. However, it makes it impossible to use KeePass on my mobile device. Also I miss the possibility to use KeePass in my browser or on the command line. I&amp;rsquo;ve looked for an alternative solution, which doesn&amp;rsquo;t compromise on security and gives me the same level of portability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Add a new file type in SharePoint - KeePass example</title>
      <link>https://janikvonrotz.ch/2014/04/14/add-a-new-file-type-in-sharepoint-keepass-example/</link>
      <pubDate>Mon, 14 Apr 2014 08:15:07 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2014/04/14/add-a-new-file-type-in-sharepoint-keepass-example/</guid>
      <description>&lt;p&gt;In this post I&amp;rsquo;ll show you how to enable a new file type in SharePoint.&lt;/p&gt;&#xA;&lt;p&gt;The goal is simple, for the KeePass database file it should be possible to open them the same way as it works for office documents in SharePoint.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://janikvonrotz.ch/wp-content/uploads/2014/04/KeePass-on-SharePoint.jpg&#34; alt=&#34;KeePass on SharePoint&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Open a Windows Remote Connection using KeePass credentials</title>
      <link>https://janikvonrotz.ch/2013/11/13/open-a-windows-remote-connection-using-keepass-credentials/</link>
      <pubDate>Wed, 13 Nov 2013 15:15:16 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2013/11/13/open-a-windows-remote-connection-using-keepass-credentials/</guid>
      <description>&lt;p&gt;KeePass is a highly recommended Passwordsafe. Despite its supposed to be used mainly by private people it&amp;rsquo;s adaptable for business cases. In my company the KeePass password database is saved on a SharePoint folder and is encrypted with a password and a private key. The key has to be stored on the local machine.&lt;/p&gt;&#xA;&lt;p&gt;It could be difficult to force employees to store their passwords in the KeePass database as many won&amp;rsquo;t get along with it. They&amp;rsquo;ll more likely store their password in third party tools. &#xA;However storing a users password in another programm as KeePass f.e. microsoft remote desktop can be a security risk because the password is only encrypted in the user context.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
