I haven’t found documentation that explains how to cache passwords that
will allow mailgate to decrypt messages sent to RT. I’ve set the home
directory to the default location and imported the appropriate keys. So I’m
able to encrypt a message to a user and I’m able to decrypt that message
and respond. But in the ticket itself the response I send back is displayed
as “Message body not shown because it is not plain text.” with a MIME type
of “application/pgp-encrypted”.
I know about gpg-agent and I’ve even gone as far as launching gpg-agent as
the user www-data (the user my webserver uses) but I’m unsure how to cache
the keys into gpg-agent. Or is this approach completely wrong?
Oliver
Details of RT Installation:
version: 4.0.7
OS: Debian Wheezy
webserver: Apache2
I haven’t found documentation that explains how to cache passwords that
will allow mailgate to decrypt messages sent to RT. I’ve set the home
directory to the default location and imported the appropriate keys. So I’m
able to encrypt a message to a user and I’m able to decrypt that message
and respond. But in the ticket itself the response I send back is displayed
as “Message body not shown because it is not plain text.” with a MIME type
of “application/pgp-encrypted”.
I know about gpg-agent and I’ve even gone as far as launching gpg-agent as
the user www-data (the user my webserver uses) but I’m unsure how to cache
the keys into gpg-agent. Or is this approach completely wrong?
You don’t need gpg decryption in UI unless you’re using encrypt attachments
in DB option. Can you tell more about your problem? At least URL where you
see encrypted content.
Oliver
Details of RT Installation:
version: 4.0.7
OS: Debian Wheezy
webserver: Apache2
–
RT Training in Seattle, June 19-20: http://bestpractical.com/training
Best regards, Ruslan.
I haven't found documentation that explains how to cache
passwords that will allow mailgate to decrypt messages sent to
RT. I've set the home directory to the default location and
imported the appropriate keys. So I'm able to encrypt a
message to a user and I'm able to decrypt that message and
respond. But in the ticket itself the response I send back is
displayed as "Message body not shown because it is not plain
text." with a MIME type of "application/pgp-encrypted".
I know about gpg-agent and I've even gone as far as launching
gpg-agent as the user www-data (the user my webserver uses)
but I'm unsure how to cache the keys into gpg-agent. Or is
this approach completely wrong?
You don’t need gpg decryption in UI unless you’re using encrypt
attachments in DB option. Can you tell more about your problem? At
least URL where you see encrypted content.
Hi Ruslan,
I will have sensitive information in the tickets I’ll create so I’d like
to encrypt the contents of the ticket. I created a test ticket, selected
myself as the owner and selected “encrypt” in the options to encrypt it
to my gpg key. An email was sent to me from the queue and I was able to
decrypt the message, reply, and encrypt the response to the queue’s
public key. When I look at the history of the ticket
(e.g. /rt/Ticket/History.html?id=31) the messages are encrypted and I’m
unable to see the contents and the error messages are described in my
previous email and in the screenshot attached.
Is there documentation on how to enable encrypting the attachments in
the DB? That sounds like an option I’d like as well.
Oliver
I haven't found documentation that explains how to cache
passwords that will allow mailgate to decrypt messages sent to
RT. I've set the home directory to the default location and
imported the appropriate keys. So I'm able to encrypt a
message to a user and I'm able to decrypt that message and
respond. But in the ticket itself the response I send back is
displayed as "Message body not shown because it is not plain
text." with a MIME type of "application/pgp-encrypted".
I know about gpg-agent and I've even gone as far as launching
gpg-agent as the user www-data (the user my webserver uses)
but I'm unsure how to cache the keys into gpg-agent. Or is
this approach completely wrong?
You don’t need gpg decryption in UI unless you’re using encrypt
attachments in DB option. Can you tell more about your problem? At
least URL where you see encrypted content.
Hi Ruslan,
I will have sensitive information in the tickets I’ll create so I’d like
to encrypt the contents of the ticket. I created a test ticket, selected
myself as the owner and selected “encrypt” in the options to encrypt it
to my gpg key. An email was sent to me from the queue and I was able to
decrypt the message, reply, and encrypt the response to the queue’s
public key. When I look at the history of the ticket
(e.g. /rt/Ticket/History.html?id=31) the messages are encrypted and I’m
unable to see the contents and the error messages are described in my
previous email and in the screenshot attached.
Is there documentation on how to enable encrypting the attachments in
the DB? That sounds like an option I’d like as well.
What you see is totally unexpected. RT should just show decrypted content
in UI. You should check logs for errors/warnings. May be enable debug
logging,
run a few tests and send us logs.
Oliver
Best regards, Ruslan.