<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://albinoloverats.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://albinoloverats.github.io/" rel="alternate" type="text/html" /><updated>2026-06-11T11:03:48+00:00</updated><id>https://albinoloverats.github.io/feed.xml</id><title type="html">albinoloverats ~ Software Development</title><subtitle></subtitle><entry><title type="html">AMA Messaging Architecture</title><link href="https://albinoloverats.github.io/2026/02/05/AMA_Messaging_Architecture.html" rel="alternate" type="text/html" title="AMA Messaging Architecture" /><published>2026-02-05T14:37:10+00:00</published><updated>2026-02-05T14:37:10+00:00</updated><id>https://albinoloverats.github.io/2026/02/05/AMA_Messaging_Architecture</id><content type="html" xml:base="https://albinoloverats.github.io/2026/02/05/AMA_Messaging_Architecture.html"><![CDATA[<p>This is the first usable release of our new messaging framework: AMA
Messaging Architecture. It may not be big and professional like Kafka,
but it sure is a hell of a lot easier to get up and running; certainly
based on my own experience in my day job!</p>

<p>There is a server that can easily be pulled via <a href="https://hub.docker.com/repository/docker/albinoloverats/messaging-server/general">Docker</a>
Compose; a single dependency for client services (and a sneaky second
dependency for testing) that is available from the
<a href="https://central.sonatype.com/artifact/net.albinoloverats.messaging/messaging-client/overview">Maven Central Repository</a>.
There is also a demo project that showcases how to make use of it all.</p>

<p>More information can be found on the <a href="/projects/messaging">project page</a>.</p>

<p>Java, love it or hate it, it pays the bills.</p>

<p>Peace</p>]]></content><author><name>The messaging Development Team</name></author><category term="messaging" /><category term="messaging" /><summary type="html"><![CDATA[This is the first usable release of our new messaging framework: AMA Messaging Architecture. It may not be big and professional like Kafka, but it sure is a hell of a lot easier to get up and running; certainly based on my own experience in my day job!]]></summary></entry><entry><title type="html">Move To Github Pages</title><link href="https://albinoloverats.github.io/2025/10/22/Move_To_Github_Pages.html" rel="alternate" type="text/html" title="Move To Github Pages" /><published>2025-10-22T12:20:31+00:00</published><updated>2025-10-22T12:20:31+00:00</updated><id>https://albinoloverats.github.io/2025/10/22/Move_To_Github_Pages</id><content type="html" xml:base="https://albinoloverats.github.io/2025/10/22/Move_To_Github_Pages.html"><![CDATA[<p>It’s been a long time coming, but we’ve finally simplified our site and
moved everything to Github. Student life with its ample free time is a
distant memory these days and keeping up with the changes in PHP to
ensure our site runs well is less of a priority. And using Jekyll on top
of Github Pages is more than capable of hosting (mostly) static pages,
as well as providing a bug tracker.</p>

<p>Although we have migrated all of the previous posts there is still some
polishing of rough edges, particularly getting SSL to work as expected;
we will also need to see what solutions exist for email (maybe we’ll
move over to AWS?)…</p>

<p>Anyway, that’s all for now.</p>]]></content><author><name>Ashley</name></author><category term="miscellaneous" /><category term="miscellaneous" /><category term="site" /><category term="update" /><summary type="html"><![CDATA[It’s been a long time coming, but we’ve finally simplified our site and moved everything to Github. Student life with its ample free time is a distant memory these days and keeping up with the changes in PHP to ensure our site runs well is less of a priority. And using Jekyll on top of Github Pages is more than capable of hosting (mostly) static pages, as well as providing a bug tracker.]]></summary></entry><entry><title type="html">encrypt 2025.05</title><link href="https://albinoloverats.github.io/2025/05/23/encrypt_2025_05.html" rel="alternate" type="text/html" title="encrypt 2025.05" /><published>2025-05-23T17:17:57+00:00</published><updated>2025-05-23T17:17:57+00:00</updated><id>https://albinoloverats.github.io/2025/05/23/encrypt_2025_05</id><content type="html" xml:base="https://albinoloverats.github.io/2025/05/23/encrypt_2025_05.html"><![CDATA[<p>It’s not been quite as long between updates this time around, but Google kind of forced our hand by threatening to close our developer account due to lack of use. So here we are with a few minor bug fixes and maybe a dependency update or two.</p>

<p>Hopefully people are still find it useful to have local file encryption applications that are cross-platform; we still find it useful if we need sensitive documents on difference devices and it needs to be secure when at rest, though for transferring SSH obviously helps a lot.</p>

<p>Anyway, until next time,</p>

<p>The encrypt Development Team</p>]]></content><author><name>The encrypt Development Team</name></author><category term="encrypt" /><category term="encrypt" /><category term="release" /><summary type="html"><![CDATA[It’s not been quite as long between updates this time around, but Google kind of forced our hand by threatening to close our developer account due to lack of use. So here we are with a few minor bug fixes and maybe a dependency update or two.]]></summary></entry><entry><title type="html">encrypt 2024.01</title><link href="https://albinoloverats.github.io/2023/12/30/encrypt_2024_01.html" rel="alternate" type="text/html" title="encrypt 2024.01" /><published>2023-12-30T09:57:49+00:00</published><updated>2023-12-30T09:57:49+00:00</updated><id>https://albinoloverats.github.io/2023/12/30/encrypt_2024_01</id><content type="html" xml:base="https://albinoloverats.github.io/2023/12/30/encrypt_2024_01.html"><![CDATA[<p>Biennially seems to be how we release recently, if you can call the last 8 or 9 years recent! Again, there aren’t too many <em>on the surface</em> changes, but there are a handful of bug fixes and improvements in reliability—especially on Android.</p>

<p>Library dependencies have been updated, and this is especially relevant on OS X as there the dependency management was incomplete and dependant on <a href="https://brew.sh/">Homebrew</a> (building encrypt still is but at least is should now function properly without it).</p>

<p>Stay secure,</p>

<p>The encrypt Development Team</p>]]></content><author><name>The encrypt Development Team</name></author><category term="encrypt" /><category term="encrypt" /><category term="release" /><summary type="html"><![CDATA[Biennially seems to be how we release recently, if you can call the last 8 or 9 years recent! Again, there aren’t too many on the surface changes, but there are a handful of bug fixes and improvements in reliability—especially on Android.]]></summary></entry><entry><title type="html">encrypt 2022.01</title><link href="https://albinoloverats.github.io/2022/01/25/encrypt_2022_01.html" rel="alternate" type="text/html" title="encrypt 2022.01" /><published>2022-01-25T16:14:54+00:00</published><updated>2022-01-25T16:14:54+00:00</updated><id>https://albinoloverats.github.io/2022/01/25/encrypt_2022_01</id><content type="html" xml:base="https://albinoloverats.github.io/2022/01/25/encrypt_2022_01.html"><![CDATA[<p>Well, it’s been another 2 years but we’re back with another release of <a href="/projects/encrypt">encrypt</a>! On the face of it, it would appear that very little has changed but there has been significant changes under the covers, a lot of which should help with error reporting and debugging (if you’re unlucky enough to need it).</p>

<p>There is now a PKG installer for Apple OS X, although as encrypt is not yet signed (and distributed via the AppStore), it will generate a warning about being untrusted; this can be overridden in the security settings. There is also still not a complete Gentoo eBuild solution, but we’ll get there one day.</p>

<p>That’s all for now,</p>

<p>The encrypt Development Team</p>]]></content><author><name>The encrypt Development Team</name></author><category term="encrypt" /><category term="encrypt" /><category term="release" /><summary type="html"><![CDATA[Well, it’s been another 2 years but we’re back with another release of encrypt! On the face of it, it would appear that very little has changed but there has been significant changes under the covers, a lot of which should help with error reporting and debugging (if you’re unlucky enough to need it).]]></summary></entry><entry><title type="html">encrypt 2020.01</title><link href="https://albinoloverats.github.io/2019/12/31/encrypt_2020_01.html" rel="alternate" type="text/html" title="encrypt 2020.01" /><published>2019-12-31T18:05:29+00:00</published><updated>2019-12-31T18:05:29+00:00</updated><id>https://albinoloverats.github.io/2019/12/31/encrypt_2020_01</id><content type="html" xml:base="https://albinoloverats.github.io/2019/12/31/encrypt_2020_01.html"><![CDATA[<p>It may be long overdue, but finally, after over two years (although a day early if you check the release notes), we are back with another release of our flagship product <a href="/projects/encrypt">encrypt</a>. The big ticket item this time around is configurable KDF iterations.</p>

<p>We have also put together a Solaris package and the start of a Gentoo eBuild file. One snag that we have discovered is that the OS X application—once copied from the disk image to Applications—the extended attribute  gets set and this seems to break the applications checksum. As such, a warning message that says the application may be damaged is displayed. This can be worked-around by opening the terminal and executing the following: . This will recursively clear all extended attributes, and solves the problem. It’s not ideal, but it’ll have to do for now; we’re working on a more user-friendly solution (perhaps distributing via the App Store is the way to go).</p>

<p>That’s it for now, hopefully everything works smoothly and we haven’t missed any compatibility issues/major bugs. So all that’s left to say is Happy New Year and bring on 2020!</p>

<p>The encrypt Development Team</p>]]></content><author><name>The encrypt Development Team</name></author><category term="encrypt" /><category term="encrypt" /><category term="release" /><summary type="html"><![CDATA[It may be long overdue, but finally, after over two years (although a day early if you check the release notes), we are back with another release of our flagship product encrypt. The big ticket item this time around is configurable KDF iterations.]]></summary></entry><entry><title type="html">encrypt 2017.09</title><link href="https://albinoloverats.github.io/2017/09/15/encrypt_2017_09.html" rel="alternate" type="text/html" title="encrypt 2017.09" /><published>2017-09-15T17:36:58+00:00</published><updated>2017-09-15T17:36:58+00:00</updated><id>https://albinoloverats.github.io/2017/09/15/encrypt_2017_09</id><content type="html" xml:base="https://albinoloverats.github.io/2017/09/15/encrypt_2017_09.html"><![CDATA[<p>It’s been nearly two years, but we have finally brought out a new release of our flagship <a href="/projects/encrypt">encrypt</a>ion application.</p>

<p>There have been a host of changes and bug fixes, including improved key derivation and MAC authentication. There are two new binary packages available: FreeBSD and Windows (64 bit); Win32 has gone the way of the dodo and is no longer available. We have also fixed the Android version to work properly with its latest permission handling.</p>

<p>Downloads are available in all the usual places; so until next time, stay secure.</p>

<p>The encrypt Development Team</p>]]></content><author><name>The encrypt Development Team</name></author><category term="encrypt" /><category term="encrypt" /><category term="release" /><summary type="html"><![CDATA[It’s been nearly two years, but we have finally brought out a new release of our flagship encryption application.]]></summary></entry><entry><title type="html">stegfs 2015.08.1 - a quick fix</title><link href="https://albinoloverats.github.io/2016/07/21/stegfs_2015_08_1_a_quick_fix.html" rel="alternate" type="text/html" title="stegfs 2015.08.1 - a quick fix" /><published>2016-07-21T19:16:35+00:00</published><updated>2016-07-21T19:16:35+00:00</updated><id>https://albinoloverats.github.io/2016/07/21/stegfs_2015_08_1_a_quick_fix</id><content type="html" xml:base="https://albinoloverats.github.io/2016/07/21/stegfs_2015_08_1_a_quick_fix.html"><![CDATA[<p>It’s been nearly a year, and during that time there has been numerous updates to the FUSE library, one of which started causing problems with stegfs. We’ve been able to quickly push out a fix, and hopefully this will give the motivation to resume working on stegfs instead of neglecting it. As there are no new features or changes to the file system layout there shouldn’t be any issues with compatibility with 2015.08 but if there are just let us know.</p>

<p>So here it is, the quick fix that is: <a href="/projects/stegfs">stegfs 2015.08.1</a></p>

<p>Enjoy</p>]]></content><author><name>The stegfs Development Team</name></author><category term="stegfs" /><category term="stegfs" /><category term="release" /><summary type="html"><![CDATA[It’s been nearly a year, and during that time there has been numerous updates to the FUSE library, one of which started causing problems with stegfs. We’ve been able to quickly push out a fix, and hopefully this will give the motivation to resume working on stegfs instead of neglecting it. As there are no new features or changes to the file system layout there shouldn’t be any issues with compatibility with 2015.08 but if there are just let us know.]]></summary></entry><entry><title type="html">encrypt 2015.10</title><link href="https://albinoloverats.github.io/2015/10/04/encrypt_2015_10.html" rel="alternate" type="text/html" title="encrypt 2015.10" /><published>2015-10-04T15:12:57+00:00</published><updated>2015-10-04T15:12:57+00:00</updated><id>https://albinoloverats.github.io/2015/10/04/encrypt_2015_10</id><content type="html" xml:base="https://albinoloverats.github.io/2015/10/04/encrypt_2015_10.html"><![CDATA[<p><a href="/projects/encrypt">encrypt</a> 2015.10 brings with it one significant new feature, as well as several bug fixes.</p>

<p>The major update is that encrypt can now correct read errors in the encrypted file (when decrypting). If several bytes are not what they should be, then encrypt will detect and fix these errors - however if there are too many then you really should find out why the bytes on disk are not what they should be! It won’t fix bad storage, but instead is to correct possible data transmission errors.</p>

<p>Bug fixes include fixing the infinite loop when attempting to decrypt a file that isn’t actually encrypted, fixing the compatibility menu on Android, and most significantly: allowing AES on Windows 8! This was achieved by using a different build of the GNU libgcrypt library.</p>

<p>The only other item of note is that there is now a free version available on Android (supported by ads).</p>

<p>That’s all now this October release,
The encrypt Development Team</p>]]></content><author><name>The encrypt Development Team</name></author><category term="encrypt" /><category term="encrypt" /><category term="release" /><summary type="html"><![CDATA[encrypt 2015.10 brings with it one significant new feature, as well as several bug fixes.]]></summary></entry><entry><title type="html">stegfs 2015.08</title><link href="https://albinoloverats.github.io/2015/08/13/stegfs_2015_08.html" rel="alternate" type="text/html" title="stegfs 2015.08" /><published>2015-08-13T18:37:39+00:00</published><updated>2015-08-13T18:37:39+00:00</updated><id>https://albinoloverats.github.io/2015/08/13/stegfs_2015_08</id><content type="html" xml:base="https://albinoloverats.github.io/2015/08/13/stegfs_2015_08.html"><![CDATA[<p>Okay, so here we are, back again <em>(finally)</em> with a completely new <a href="/projects/stegfs">stegfs</a>! And when we say new, we mean totally rewritten! It’s much better at not overwriting your existing files (although it can and will still happen) and it’s a lot more customisable.</p>

<p><strong>Warning!</strong> stegfs 2015.08 is not backwards compatible!</p>

<p>However, onto the good stuff:</p>

<ul>
  <li>More bytes for data, less for metadata</li>
  <li>Choose your crypto at mkfs time (now using [libcrypt])</li>
  <li>File systems are no longer architecture dependant (score one for
network byte order!)</li>
  <li>There’s no longer any need to prefix directories with +</li>
  <li>And hopefully the code generally all round better than before (having
been rewritten with a few more years experience, et cetera)</li>
</ul>

<p>Lo, there too are a number of sad points:</p>

<ul>
  <li>stegfs is not (yet) multi-threaded—if you have a large
read/write, it will block—this is something we’re looking at
working on soon</li>
  <li>As was mentioned above: it’s not backwards compatible, but hopefully
it will be as we move forward</li>
</ul>

<p>I think that’s pretty much everything for now; sorry it’s been so long, but (as far as file systems go I feel) too many releases are likely to negatively affect stability, hence the delay.</p>

<p>Stay safe,
Ashley</p>]]></content><author><name>The stegfs Development Team</name></author><category term="stegfs" /><category term="stegfs" /><category term="release" /><summary type="html"><![CDATA[Okay, so here we are, back again (finally) with a completely new stegfs! And when we say new, we mean totally rewritten! It’s much better at not overwriting your existing files (although it can and will still happen) and it’s a lot more customisable.]]></summary></entry></feed>