On Tue, Jun 17, 2014 at 10:00:06PM +0200, Joop wrote:
> Thanks Kevin for your answer. I didn't link this pref with the
> Decrypt/Encrypt links in the transactions.
Doc patches welcome, I had to grep to convince myself it was the only
thing.
> Follow up question on this is: It is the admins respon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17-6-2014 20:55, Kevin Falcone wrote:
> On Sat, Jun 14, 2014 at 05:59:44PM +0200, Joop wrote:
>> AllowEncryptDataInDB: allows encrypted data in the database.
>>
>> While having this set or unset I don't see any difference in the
>> contents of the
On Sat, Jun 14, 2014 at 05:59:44PM +0200, Joop wrote:
> AllowEncryptDataInDB: allows encrypted data in the database.
>
> While having this set or unset I don't see any difference in the
> contents of the attachments table contents.
It shows an Encrypt/Decrypt link on Transactions in a ticket hist
Hi All,
I'm playing around with GPG integration in RT and once grasped the
concept of keys and configuring server side and client side it seems to
work beautifully. Reading the docs I came across the following and don't
understand what its meaning/use case is.
AllowEncryptDataInDB: allows encrypte
