> In fact, gpg epitomizes a perfect anti-UNIX design. (See Eric S. Raymond > for details, what UNIX philosophy means)
Mmmhmm. > For instance, even for basic operations (encrypt, decrypt), where no > modifications to my key pair are necessary, gpg still requires my > ~/.gnupg/ to be writable (cannot me on read-only filesystem) Again, you're criticizing a design before learning why that design is the way it is. > That is another example of hard-requiring something, that it does not > need (same as agent for symmetric decryption) You don't understand the design, which means you don't know what the system needs and/or doesn't need. You're not displaying judgment here, you're displaying prejudice. > That is why I a m giving here my honest feedback. You are of course welcome to give what feedback you like. I respectfully suggest that if you start by learning why these various tradeoffs were made, it will allow you to make better criticisms that will be taken more seriously by the development team.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
