Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sign outgoing Mails #5

Open
bastelfreak opened this issue Aug 18, 2013 · 9 comments
Open

sign outgoing Mails #5

bastelfreak opened this issue Aug 18, 2013 · 9 comments
Milestone

Comments

@bastelfreak
Copy link

Hi,

first of all, thanks for the script, it's working great :)

Would it be possible to not only crypt outgoing mails but also sign them? I tried by myself to implement that feature, but unfortunately I've no clue about python.

@infertux
Copy link
Owner

I'm not sure about adding this feature. That would mean having your private GPG key and its password stored on the server. I guess you could generate one key per server and revoke them should the server be compromised. But still, it doesn't sound really safe to me.

I'd like to add some sort of signing though to ensure integrity (i.e. make sure the message has not been tampered between the server and you).

What do you think? Did you have a better way of handling this issue in mind?

@bastelfreak
Copy link
Author

It should be no probem to sign the emails with a key + passphrases that's stored on the server if every server gets a own key. If someone breaks into my server I've probably bigger problems then a compromised key. Also I could store the revocation keys on my local maschine or keepass container.

@infertux
Copy link
Owner

That makes sense. Adding this to the roadmap for release 0.4.

@bastelfreak
Copy link
Author

awesome, thanks.

@stephenjamieson
Copy link

This sounds really useful to me if it gets implemented, kudos for the great project.

@bastelfreak
Copy link
Author

Hi infertux,

do you have any new infos about release 0.4?

On 30.03.2014 06:31, stephenjamieson wrote:

This sounds really useful to me if it gets implemented, kudos for the great project.


Reply to this email directly or view it on GitHub:
#5 (comment)

@infertux
Copy link
Owner

infertux commented Apr 3, 2014

Sorry for the delay @bastelfreak and @stephenjamieson, I can't seem to find the time to work on this project lately. I reckon release 0.4 is at least one month away. I'd happily give commit access to anyone willing to contribute.

@bastelfreak
Copy link
Author

I'm currently not able to write usefull python code, also the gpg library is bretty hard to understand ( or I used the wrong docs). Need to lern python for my job anyway, will let you know if I'm able to contribute in the future.

@infertux infertux modified the milestones: 1.0.0, Future Jun 13, 2015
@acatton acatton mentioned this issue Jul 30, 2015
9 tasks
@infertux infertux modified the milestones: 1.2.0, Future Oct 16, 2015
@acatton acatton modified the milestones: 2.0, 1.2.0 Mar 16, 2016
@kaosmonk
Copy link

Hey guys, no update on this one yet? It seems like signing is a tough nut to crack. I have tried implementing Context.encrypt_sign but have been hitting the wall with that one. @infertux any chance you'll be able to look into this any time soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants