tag:gpgtools.tenderapp.com,2011-11-04:/discussions/feedback/11954-gpgsuite-is-now-in-violation-of-the-gpl-licenseGPGTools: Discussion 2022-03-10T08:05:16Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/461324332018-11-03T03:00:14Z2018-11-03T03:00:14ZGPG Suite might now be in violation of the GPL License<div><p>Where is the open source version of GPG Tools which will run on mojave or high sierra?</p>
<p>Since I was not warned about the paid upgrade to gpgtools 2018.5 why not bite the bullet make everyone happy offer a free update version gpgtools 2018.6?</p>
<p>Then when you figure out all your legal issues providing an open source product that works under Apple's current operating system consider producing free software with the option for your user base to purchase an optional support package !</p></div>paultag:gpgtools.tenderapp.com,2011-11-04:Comment/461324332018-11-03T04:54:51Z2018-11-14T22:06:32ZGPG Suite might now be in violation of the GPL License<div><p>sorry guys I installed a free Comodo signing key which actually has no bearing on this thread. and have no way to delete this entry.</p>
<p>I have to use the Services dropdown to use GPG Suite 2018.5 (6f26711) in Apple Mail app</p></div>paultag:gpgtools.tenderapp.com,2011-11-04:Comment/461324332018-11-15T15:51:50Z2018-11-15T15:51:52ZGPG Suite might now be in violation of the GPL License<div><p>I am writing on this thread just to confirm that the ope source code does actually run on Mail 12 on Mojave. But, I had a lot of problems and thought my experience would help others, and put to rest worries about the actual code is somehow hidden or the provided code is spiked.</p>
<p>There were three independent problems: first, Mail was not recognizing the presence of any mailbundles in ~/Library/Mail/Bundles, so no option to manage them appeared in the menu. I spent a lot of time on this, and it got fixed when I installed the distributed binary (without actually activating the GPGMailLoader plugin). I haven't investigated this issue; it probably has something to do with the systemwide /Library/Mail/Bundles needing to exist, or some caching problem or something like that. Someone who knows better may be able to comment. For the rest of the experiments, I started putting the mailbundle in /Library rather than ~/Library, but I think both work.</p>
<p>Next, if obtaining the code from github, it is important to move to the mojave branch. As opposed to expectations, the different branches for different major OS versions are not yet merged.</p>
<p>Third, even after all this, Mail complained about the plugin not being for the current Mail version. This is due to a corruption in signature as mentioned by someone else above. I fixed this by creating a self-signed code-signing key, and force signing the included Framework in the source tree: codesign -s --deep --force Frameworks/RegexKit.framework (This gives a security error if the keychain where the codesigning key for is located can't be unlocked, typically when it cannot open a window to ask for the password). If it gives the error that it can't figure out whether it is an app or a framework, it is due to a corruption of the tree where a symbolic link called 'Current' a few folders down has been copied rather than being left as a link.</p>
<p>And fourth, Copy the final mailbundle to the right place maintaining symbolic links as symbolic links. For example cp -a works, but cp -pr corrupts.</p>
<p>Hope this description helps others like me who came to this thread believing the authors were deliberately trying to fool the internet :-)</p></div>Tanmoy Bhattacharyatag:gpgtools.tenderapp.com,2011-11-04:Comment/461324332018-11-15T15:58:54Z2018-11-15T15:58:55ZGPG Suite might now be in violation of the GPL License<div><p>Sorry it does not let me edit my message. Two things: first the codesign command needs the signing identity after the -s. I put in <identity> while posting, but the formatter took that for an html tag ...</p>
<p>Second, I forgot to mention that the signing has to be done before the make. If you have already done a make, a make clean is needed before you make afresh.</p></div>Tanmoy Bhattacharya