You don’t have to take my word for it, but when I was begin developing NouveauPG years ago I found that, 1.) DSA is just hours of testing debugging, etc. with little return on invest. Don’t get this twised, this was never designed to make me a millionaire but I thought is was something that should exist. We’re only here for a short time and we really have to think beyond the fleeting riches which so many in the current tech industry base their self worth. Just sort of proud that I saw that coming years ago. 🙂
Apart from the due to the limited role of NouveauPG’s ‘eco-system’ it is safe for the secure transmission of text messages of any length across insecure medium. Social media etc. NouveauPG was written from the ground up and shares no code with the c. 1994 code-base. Apart from myself accessing this site via Tor which could be AWS nonsense, all is secure.
For the time being, nouveaupg.info is the internet address. There are some very strange things happening with nouveaupg.com. I’m hoping to have everything back up ASAP, but for the meantime nouveaupg.info is the temporary address.
UPDATE: well this is weird, I can access nouveaupg.com via Tor, but not my home connection. I’m sure it’s nothing. I have more pressing matters, just thought this was interesting.
Another day another attack against GnuPGP tools. I have long believed that the complicated integration mechanism that GPGTools use to integrate with the Mail client are vulnerable to attack. Not too long ago Internet Explorer browser extensions were the attack vector into Windows PC’s.
Remember with NouveauPG, the entire app is sandboxed. The only way to get data in or out is by selecting a file using the system file dialog box, or using the clipboard. No internet access, third party plug-ins or anything. The only reason encryption is not ubiquitous by now is the trade-off between usability. More ‘convenient’ schemes always seem to backfire. NouveauPG is as simple as I know how to make it.
Welcome new users that got here via MacInformer.
I’m convinced almost nobody actually uses this functionality of GnuPG, because it is somewhat awkward and confusing for myself, having been a student of the OpenPGP protocol for many years. I thought this would make a good post to explain what to do with those PGP signature files you often see alongside the download links of free/open source software.
The vast majority of signatures use the RSA algorithm. GnuPGP/commercial PGP give you two choices, and they are both probably fine, but it makes the whole thing more confusing. The RSA algorithm can be used for encrypting and signing whereas the alternative ElGamal algorithm uses the official sounding DSA, Digital Signature Algorithm. I don’t even bother implementing ElGamal due to the amount of time it would take to implement and the nonexistent payoff. Since RSA is the de facto standard for even mainstream cryptography, combined with the fact that it can be used for both signing and encryption, I never though it worth my while to develop, debug, test, and all that comes with this labor of love (of the Fourth Amendment).
Ironically, for GnuPG 1.4.20, which is the easiest open source PGP distribution to build, the signing key is already expired. This is only a problem if somehow the private RSA key came into the possession of a malicious part. Before you do anything, you must import the signing certificates from the offical GnuPG website.
If there’s not enough evidence to support the waste of time that is implementing testing, regression testing, and supporting DSA, even the official GnuPG releases are signed with RSA.
Verifying a file using GnuPG and an attached signature is a simple command line argument that should only take a few tries to get right.
Again, this is the problem I see with GnuPG… we’re getting conflicting messages. First the good news: it appears that two parties have signed the tar ball with their private keys so unless both of those keys have been compromised the by malicious entities, the tar ball is intact. The first warning is that “there is no indication the signature belongs to the owner”. So apparently, importing the keys from GnuPG’s very own website 10 minutes ago which is secured by SSL/TLS is not enough assurance the key is valid. I wonder why they even bother to post them. The other is that the key is expired…
This would make sense since 1.4.20 is quite an old release, I’m just using that version since the compilation is so much more straightforward. Newer versions of GnuPG have a modularized codebase but the actual encryption code is line for line the same as 1.4.20 — and obviously showing it’s age since it’s based on streams which made a lot more sense in 1999 when memory was much more limited on the average enthusiast computer. Streaming is more memory efficient at the cost of code complexity. (i.e. bugs)
Thus a new Privacy Guard is needed. And open source is not a panacea, perhaps including a sane file verification function in the (long overdue) next update of NouveauPG.
Compiling from source code is a straightforward way to ensure that you have a genuine copy of GnuPG on your machine. Since GnuPG may be used to verify other software packages, it is important that your copy is not tampered with.
This post will outline the steps for compiling GnuPG classic v1.4.20 from source for Mac OS X rather than the latest version of GnuPG (v2.0.x) because it is much simpler to compile. Compiling GnuPG from source is certainly not any more difficult that using GnuPG, which is a command line program.
1.) Install command line developer tools for Mac OS X. This is dead simple on recent versions of Mac OS X 10.9 and up, simply open the Terminal and type “xcode-select –install”. The dialog below will appear and allow you to install the command line tools.
For older versions of Mac OS X, the procedure outlined here may work.
3.) Decompress and extract the source code archive.
bzip2 -d gnupg-1.4.20.tar.bz2
tar -xvf gnupg-1.4.20.tar
4.) From the source code directory, run the configure script to make sure your command line tools are installed.
5.) Assuming there are no errors, from the same directory run make to compile gnupg.
At this point, if everything went correctly, you should find the gpg executable in the g10 subfolder.
6.) If you wish to install GnuPG 1.4.20 as your default gpg:
sudo make install
You must uninstall other versions of gpg (including those installed by other software packages) before installing.
I finally have the Bitcoin activation system up and running. Now if you want to purchase NouveauPG, you don’t need to go through the Mac App Store. The first time NouveauPG is run on a Mac, it generates a random UUID. When you provide a valid UUID to the activation page, you will be assigned a Bitcoin deposit address. When you deposit enough Bitcoin, a signature will be generated that can be copied and pasted into NouveauPG to unlock it. No network access is necessary.
A few years ago, I swore to myself that I would not publish apps that I didn’t use myself. NouveauPG for iOS has some issues I don’t have the time to fix in the near future. I hope to have it back and better than ever in 2016, but I will not publish it until it is in good enough shape that I have it on my phone.
I use NouveauPG for OS X on a regular basis, so I want to concentrate on that for the time being.
Version 1.70 fixes an issue where older versions of GnuPG for Windows would generate output with extra linebreaks which would incorrectly fail to validate.
No need to update if you’re not affected by this issue.
App Store update should be approved and pushed in the next few days.