<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Experience on Tech Philosopher</title><link>https://blog.bktus.com/en/tags/experience/</link><description>Recent content in Experience on Tech Philosopher</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 12 Nov 2025 23:24:37 +0100</lastBuildDate><atom:link href="https://blog.bktus.com/en/tags/experience/index.xml" rel="self" type="application/rss+xml"/><item><title>The Past and Present of GpgFrontend: My Journey with an Open-Source Encryption Tool</title><link>https://blog.bktus.com/en/archives/u8hywl/</link><pubDate>Wed, 12 Nov 2025 23:24:37 +0100</pubDate><guid>https://blog.bktus.com/en/archives/u8hywl/</guid><description>&lt;h2 id="how-it-started-running-into-gnupg-gpg">How It Started: Running into GnuPG (GPG)&lt;/h2>
&lt;p>I first came across GPG around April 2021. Back then I was just a student who was curious about everything in the computer world, and my understanding of cryptography didn&amp;rsquo;t go much further than “a password is an encrypted string”. Then I read about how asymmetric encryption works: anyone can use a public key to encrypt a message, but only the person who holds the private key can decrypt it. That really amazed me. I liked this kind of “mathematical trust”. It&amp;rsquo;s elegant, rigorous and irreversible, and at that moment I felt it was just as beautiful as any piece of art. So I started learning the GPG command line, from generating keys to verifying signatures, trying things again and again to understand the logic behind them.&lt;/p></description><content:encoded><![CDATA[<h2 id="how-it-started-running-into-gnupg-gpg">How It Started: Running into GnuPG (GPG)</h2>
<p>I first came across GPG around April 2021. Back then I was just a student who was curious about everything in the computer world, and my understanding of cryptography didn&rsquo;t go much further than “a password is an encrypted string”. Then I read about how asymmetric encryption works: anyone can use a public key to encrypt a message, but only the person who holds the private key can decrypt it. That really amazed me. I liked this kind of “mathematical trust”. It&rsquo;s elegant, rigorous and irreversible, and at that moment I felt it was just as beautiful as any piece of art. So I started learning the GPG command line, from generating keys to verifying signatures, trying things again and again to understand the logic behind them.</p>
<p>But I also found a problem: the command line is really hard to get into. Sometimes I just wanted to do something simple quickly, and I still had to type a long string of commands, which honestly annoyed me. For non-technical users, the GPG command line is like an obscure wasteland, and it stops almost everyone who wants to try it. So I started thinking: what if GPG had a simple, easy-to-use graphical interface, so it felt like a crypto machine you can actually see and touch? If everyone could easily have a small, durable “crypto machine”, maybe more people would be willing to try it. At the time this idea seemed pretty small, but it was what started the next several years of my technical work.</p>
<blockquote>
<p>The term “crypto machine” immediately evokes a sense of reliability,
something like the mechanical encryption devices of the past, such as the
Enigma. It’s not just technology, but also a belief in security. Such a device
doesn’t need endless features. It just needs to be <strong>precise and dependable</strong>.
When a user presses a button, the result must be <strong>predictable and safe</strong>. That
pursuit of control and predictability is the soul of a crypto machine.</p></blockquote>
<p>I started looking for existing solutions. There were already some GUI tools back then, like Kleopatra. But a lot of them had complicated interfaces and too many features, and some even brought in the X.509 certificate system, which put me off right away. I wanted something lighter and simpler. Later I found a project called <a href="https://git.bktus.com/gpgfrontend/gpg4usb/">gpg4usb</a>, which was very close to what I had in mind: lightweight, portable and cross-platform. Unfortunately, it had stopped being updated long ago and only supported GPG 1.4. That meant compatibility problems with modern systems were almost unavoidable, and it couldn&rsquo;t support subkeys either.</p>
<p>So I started thinking: could I rewrite part of it and bring it back to life? Around May, I spent about half a month in my dorm reading its source code, figuring out how to call GPG&rsquo;s interfaces, and learning about the Qt framework and cross-platform compatibility. It was a lonely process, but a really fulfilling one. Every time I got a new feature working, I felt a sense of achievement that&rsquo;s hard to describe. When I finally got it running with GPG 2 and fixed quite a few of the original bugs, I decided to give the refreshed project a new name: <a href="https://gpgfrontend.bktus.com/">GpgFrontend</a>. It&rsquo;s a graphical frontend for GPG, and it was also the first complete open-source project of my life.</p>
<p><img alt="GpgFrontend" loading="lazy" src="https://img.bktus.com/P7a8YV8G.webp"></p>
<h2 id="going-public-from-dorm-room-code-to-github">Going Public: From Dorm Room Code to GitHub</h2>
<p>After I uploaded the first version to GitHub, I didn&rsquo;t expect much attention. After all, this is a very niche area, and GPG itself isn&rsquo;t something most people use. But a few days later, I got my first issue. A user said the program didn&rsquo;t run on a certain operating system. They provided logs and even suggested a fix. That was the first time I felt something that made me want to keep putting time into this project.</p>
<p>After that, more and more people started using GpgFrontend. They reported problems, made suggestions and even contributed translations. Every piece of feedback showed me that this project was no longer just my own tech toy. It was a tool people actually used. From then on, my understanding of open source changed completely. To me, it&rsquo;s not just sharing code anymore. It&rsquo;s a whole ecosystem that keeps getting feedback and keeps changing.</p>
<p>Over the next two or three years, I gradually understood that GpgFrontend can&rsquo;t be, and doesn&rsquo;t need to be, an all-in-one tool. Its purpose is very clear: to help users encrypt, decrypt, sign and verify more easily. Its value isn&rsquo;t in the number of features, it&rsquo;s in being easy to use and reliable. So now I clearly define it as a <strong>lightweight, secure crypto machine</strong>, which is exactly what I wanted when I first started using GPG.</p>
<p>For experienced users who know the command line, it&rsquo;s a tool that saves time. For beginners, it&rsquo;s a bridge into the world of cryptography. So in the UI, I try to keep things simple, so that every core operation is clear at a glance. Under the hood, every action maps directly to a native GPG command, to keep it stable and compatible. Later I realized that this “small but focused” positioning actually became what makes GpgFrontend different. While other projects go after more features, I chose to keep it focused.</p>
<h2 id="growing-using-the-project-as-my-testing-ground">Growing: Using the Project as My Testing Ground</h2>
<p>As the versions went on, GpgFrontend became my training ground for learning new technology. I kept trying to bring new ideas I picked up at work and in my studies into the project. I studied Chromium&rsquo;s multithreading architecture and brought its ideas of thread scheduling and task isolation into GpgFrontend, so the interface no longer freezes during encryption, and race conditions and other common multithreading bugs are reduced as much as possible. I designed a plugin system and an SDK, so third parties can extend features at runtime. I improved the build scripts and added CI/CD, so packaging for different platforms is more automated and more reliable. Also, through the cross-platform support, I learned about the many implementation differences between Windows, macOS and Linux, and how packaging works on different operating systems and distribution platforms.</p>
<p>These experiments made the tool itself better, and they also gave me real engineering experience: how to design an architecture that can be maintained, how to balance stability and new ideas, and how to refactor without breaking old features. Step by step, GpgFrontend grew from a simple experiment into an open-source tool with a reasonable structure that people can rely on.</p>
<p>When I was taking a network security course, the professor talked about why data security and key management matter so much. Suddenly I realized that some of the things I had implemented early in the project had hidden risks. For example, the key derivation algorithm was too simple, stored data had no key rotation, and some memory wasn&rsquo;t protected. So I started a full security refactoring.</p>
<p>In <a href="https://github.com/saturneric/GpgFrontend/releases/tag/v2.1.9">version 2.1.9</a>, I added security levels, startup self-checks, AES-GCM encryption mode, key rotation and secure memory. I also redesigned the program&rsquo;s data structures, so that temporary secrets in memory are wiped as safely as possible after they&rsquo;re used. These changes happen behind the scenes, but they made GpgFrontend noticeably more secure and reliable. As I&rsquo;ve always believed, security isn&rsquo;t a feature, it&rsquo;s an attitude. Only when security is built in from the design stage can a tool keep people&rsquo;s trust over time.</p>
<p>Over the years of maintaining the project, I&rsquo;ve gradually felt a kind of satisfaction that goes beyond the technology. GpgFrontend isn&rsquo;t a popular project, but it has really helped some real users. Some people use it to verify the signatures of software packages, some use it to handle secure communication quickly at work, and someone told me it was their first way into learning GPG. I don&rsquo;t track users, and I don&rsquo;t collect download numbers from each platform either. Honestly, I don&rsquo;t know how many people are using it. But I like not knowing. It makes me feel that GpgFrontend is a pure contribution. To put it more concretely, it&rsquo;s a small crypto machine that&rsquo;s always within reach, can go anywhere with you, and quietly does its job wherever people need it.</p>
<h2 id="looking-ahead-stable-focused-and-in-it-for-the-long-term">Looking Ahead: Stable, Focused and in It for the Long Term</h2>
<p>Over the next few years, I won&rsquo;t make big changes to GpgFrontend. Updates will continue, but they&rsquo;ll mostly be about a better user experience, more stability, bug fixes and small optimizations. I&rsquo;d rather keep it light and under control. The software industry today is full of fast iteration, and I actually hope GpgFrontend can be an exception: a steady, reliable tool you can trust. Maybe it will never be popular or make the tech headlines. But as long as it keeps helping the people who really need it, I think it&rsquo;s all worth it.</p>
<p>In recent years, I&rsquo;ve been paying close attention to how Rust is growing in the security field. I&rsquo;ve looked into a few Rust-based alternatives to the GPG libraries, like RPGP and Sequoia. They have better memory safety and concurrency management, and they support some of the newest OpenPGP features. I think this is clearly the direction things are going. But I also have to face reality: the Rust ecosystem isn&rsquo;t fully mature yet, and its compatibility with the existing GPG ecosystem still needs to be tested.</p>
<p>So I plan to set up a separate branch in the future, plug in Rust-based crypto libraries there as an experiment, and wrap them with a new key database layer. This kind of gradual migration lets me find out whether the new technology works without breaking the stability of the main line. I&rsquo;ve always believed that steady updates matter more than chasing new things. After all, the value of a security tool isn&rsquo;t in being new, it&rsquo;s in being trusted. And building that kind of trust may take something like ten years.</p>
]]></content:encoded></item></channel></rss>