<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>KeePassRPC on Kee Vault Ltd</title>
    <link>https://www.kee.pm/tags/keepassrpc/</link>
    <description>Recent content in KeePassRPC on Kee Vault Ltd</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 Sep 2017 20:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.kee.pm/tags/keepassrpc/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Introducing Kee 2.0</title>
      <link>https://www.kee.pm/2017/09/19/introducing-kee-2.0/</link>
      <pubDate>Tue, 19 Sep 2017 20:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2017/09/19/introducing-kee-2.0/</guid>
      <description>KeeFox version 2.0 is nearly here and with it comes a change of name which reflects the broader support for multiple web browsers such as Google Chrome.
Kee 2.0 is currently undergoing final tests before being released to the beta testing channel. If your current version of KeeFox ends in &#34;b something&#34; (e.g. 1.7.2b1) you&#39;re on the beta channel and will be one of the first to try out Kee - thanks!</description>
    </item>
    
    <item>
      <title>Changes to KeeFox in 2017</title>
      <link>https://www.kee.pm/2017/03/26/changes-to-keefox-in-2017/</link>
      <pubDate>Sun, 26 Mar 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2017/03/26/changes-to-keefox-in-2017/</guid>
      <description>By the end of this year KeeFox will have to change significantly so this post is an overview of what will change, how, when and why. Many of the details are still uncertain and will depend partially on how much spare time can be found to implement the changes and how many people can contribute to help this process. I&#39;ll post updates throughout the year as changes are made so you know what to expect when the bulk of the changes arrive at the end of the year in the form of KeeFox version 2.</description>
    </item>
    
    <item>
      <title>Security update released</title>
      <link>https://www.kee.pm/2016/11/21/security-update-released/</link>
      <pubDate>Mon, 21 Nov 2016 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2016/11/21/security-update-released/</guid>
      <description>All KeeFox users should update to version 1.6.4  (or 1.6.4b1  if you are a beta tester). For most users, Firefox will do this for you automatically. Both the Firefox addon and KeePass plugin will need to be updated. The button on the KeeFox setup page should update the KeePass plugin for you if you&#39;re on Windows but otherwise just manually copy the KeePassRPC.plgx file to the KeePass plugins folder as with most KeeFox updates.</description>
    </item>
    
    <item>
      <title>Security documentation update</title>
      <link>https://www.kee.pm/2016/10/18/security-documentation-update/</link>
      <pubDate>Tue, 18 Oct 2016 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2016/10/18/security-documentation-update/</guid>
      <description>A small omission has been found in the KeeFox documentation which explains the different ways that you can protect the connection between Firefox and KeePass. It&#39;s not a serious problem but since this may have guided some people&#39;s choice of KeeFox configuration, I wanted to post a quick explanation of the situation. Firstly, thanks to lhernanz for bringing this to our attention. If your computer runs Microsoft Windows you can stop reading now - this only affects users that use KeePass on Linux, Mac and other Unix operating systems.</description>
    </item>
    
    <item>
      <title>Upcoming releases</title>
      <link>https://www.kee.pm/2013/08/18/upcoming-releases/</link>
      <pubDate>Sun, 18 Aug 2013 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2013/08/18/upcoming-releases/</guid>
      <description>KeeFox 1.2.5b1 released
Version 1.2.5 is nearly ready to be released so beta testers will soon be upgraded to this new version with a few small but important bug fixes:
A fix for Thunderbird 25A couple of bug fixes that caused some passwords to not save to KeePassDanish, French, Korean, Portuguese and Russian languages created / updated (some not complete yet)Fix for intermittent failed KeePass shutdown on Mono (Mac/Linux)Some other small changesBig changes in KeeFox 1.</description>
    </item>
    
    <item>
      <title>KeePass 2.18 compatibility</title>
      <link>https://www.kee.pm/2012/01/11/keepass-2.18-compatibility/</link>
      <pubDate>Wed, 11 Jan 2012 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2012/01/11/keepass-2.18-compatibility/</guid>
      <description>Thanks to everyone that notified me of the problems with the recently released version of KeePass. I hope to release a new version in 4-6 weeks with a beta available within a few weeks. In the mean time, the existing version of KeeFox will continue to work with KeePass 2.17. As with the previous problematic KeePass upgrade, your upgrade route will be much simplified if you continue using KeePass 2.17 until after you are running a new version of KeeFox*.</description>
    </item>
    
    <item>
      <title>KeePassRPC security and authentication</title>
      <link>https://www.kee.pm/2010/12/11/keepassrpc-security-and-authentication/</link>
      <pubDate>Sat, 11 Dec 2010 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2010/12/11/keepassrpc-security-and-authentication/</guid>
      <description>Another technical post here which explains why KeePassRPC is secure and how an application developer needs to handle authentication with the plugin to protect its users. Security conscious people might view a KeePass remote access system with fear and loathing and it is true that installing this plugin exposes a new attack vector. I’ll explain how KeePassRPC can be exploited to access a user’s password database but you will see that the installation of the plugin is safe provided that… A) Neither me nor any 3rd party developers of libraries used in this project have made a mistake in the plugin code B) Both client and server machines remain secured from 3rd party threats such as viruses, trojans, keyloggers, etc.</description>
    </item>
    
    <item>
      <title>KeePassRPC plugin technical overview</title>
      <link>https://www.kee.pm/2010/12/03/keepassrpc-plugin-technical-overview/</link>
      <pubDate>Fri, 03 Dec 2010 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2010/12/03/keepassrpc-plugin-technical-overview/</guid>
      <description>As announced earlier this year, KeePassRPC is a remote access interface plugin for KeePass Password Safe 2. This post is aimed at application developers; it outlines how you could use the plugin to enhance your user’s KeePass experience and references the latest version of the source code (0.8.5). There is currently no official release but you can see version 0.8.4 in use with KeeFox 0.8.4 and view the source code for 0.</description>
    </item>
    
    <item>
      <title>KeePassRPC plugin</title>
      <link>https://www.kee.pm/2010/03/24/keepassrpc-plugin/</link>
      <pubDate>Wed, 24 Mar 2010 00:00:00 +0000</pubDate>
      
      <guid>https://www.kee.pm/2010/03/24/keepassrpc-plugin/</guid>
      <description>KeePassRPC provides a remote access interface for KeePass Password Safe 2. There is currently no official release but you can view the source code in the KeeFox repository. The most interesting files are: DataExchangeModel.cs KeePassRPCService.cs  KeePassRPCServer.cs I’ll publish an more in depth introduction to those files soon. The RPC system is an implementation of JSON-RPC; this is a simple protocol and probably does not support every possible desired feature but clients are easy to implement and libraries already exist for most programming languages.</description>
    </item>
    
    <item>
      <title>KISS</title>
      <link>https://www.kee.pm/2010/03/22/kiss/</link>
      <pubDate>Mon, 22 Mar 2010 00:00:00 +0100</pubDate>
      
      <guid>https://www.kee.pm/2010/03/22/kiss/</guid>
      <description>Who doesn’t prefer the simple option? Software developers are no different and security software is generally better the simpler it is so a sensible rule-of-thumb is to always KISS whenever possible, that’s Keep It Simple, Stupid! Therefore, I am pleased that in the past few weeks I’ve been able to simplify the most crucial aspect of the way KeeFox communicates with KeePass. The key change is that KeeFox now requires a new KeePass plugin called KeePassRPC instead of the (now retired) KeeICE plugin.</description>
    </item>
    
  </channel>
</rss>