<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>KeePass API on Kee Vault Ltd</title>
    <link>https://www.kee.pm/tags/keepass-api/</link>
    <description>Recent content in KeePass API on Kee Vault Ltd</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Aug 2013 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.kee.pm/tags/keepass-api/index.xml" rel="self" type="application/rss+xml" />
    
    
    <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>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>
    
  </channel>
</rss>