Closed (fixed)
Project:
OpenPGP
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Issue tags:
Reporter:
Anonymous (not verified)
Created:
24 Jun 2009 at 19:16 UTC
Updated:
11 Jun 2024 at 12:23 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedA time line would be very good b/c the GnuPG module was indicated as unsupported w/o an initial release of the OpenPGP module.
Comment #2
Arto commentedGlad to see there's interest in the module - that helps motivate work on it ;-)
I'm finishing up an initial release and should have it out later this week.
Comment #3
Arto commentedGlad to see there's interest in the module - that helps motivate work on it ;-)
I'm finishing up an initial release and should have it out later this week.
Comment #4
Tim_O commentedYou have any update on that for us, please?
Comment #5
Arto commentedA development version of this module is currently available via drupal.org CVS. I will create a 6.x-1.x-dev release node presently so that those not familiar with CVS can also test it out; this should be available within 12 hours.
The current status of the module is basically that it works for me (i.e., e-mails are encrypted when sent to users who have public keys on file), but doesn't yet have much documentation, and still requires the GnuPG command-line tools to be installed on the server where it will be used.
I am hoping to eliminate that external dependency before releasing 6.x-1.0. I have already implemented OpenPGP encryption from scratch in OpenPGP.rb (an OpenPGP library for Ruby) and intend to port this to PHP shortly. This will allow e-mail encryption without any cumbersome external dependencies (needing only libraries almost always readily available in PHP installations, such as OpenSSL or Mcrypt), which should greatly facilitate the use of this module.
Comment #6
Tim_O commentedCool, Arto. Thank you for your efforts and your anwser.
About the external dependency thingy. Cryptography is quite prone to vulnerabilities within implementation. While the idea surely is good, I myself would currently prefer to have this dependency thus being able to rely on the probably better tested gnupg implementation (also utilising set preferences do get rid of SHA-1 and stuff, also). Please don't understand this wrong, I do value your effort and in the long-term it might even be the better alternative or something, but for me it currently just isn't. Therefore my question to you: Could you do that as something optional?
And on a side-node, you will have to implement quite a lot of algorithms and stuff if you intend to be compatible with all options of gnupg. The algorithms alone would make me go nuts ;) So maybe you can even decide simply not to do this (aka "keep it simple") thus having more time for the rest.
Anyways, I will have a look at your module after I get the migration to 6 done. And as I said already: Thank you for doing this, this is something the world really needs!
Comment #7
Arto commentedTim, the cryptographic algorithms themselves are still implemented by the underlying standard OpenSSL/Mcrypt libraries. The OpenPGP standard (RFC 4880) simply involves a standard binary message format on top of that, and assorted utilities like ASCII armoring those messages. So, by "OpenPGP encryption" it is only this message parsing & creation I mean, not the actual finicky details of the underlying cipher algorithms - I assure you I am quite happy letting those libraries take care of e.g. RSA & AES encryption ;-)
And in any case, this will merely be the default mode. GnuPG support will always continue to be available as an optional submodule, which when installed will use the
gpgbinary to handle all encryption, decryption, signing and verification tasks, just like before.So, no worries - the idea is only to enable more widespread adoption, and certainly not to inadvertently compromise your security. I am very much aware of how easily security can be compromised, and have use cases for this module that require the utmost care to prevent such compromises.
Comment #8
Anonymous (not verified) commentedIt works for me, too. Thank you very much!
If I send myself a copy of the message, this copy isn't encrypted although I have my public key in the profile.
But I should open an issue for this and a feature request for the encryption of the site-wide contact form.
Comment #9
Anonymous (not verified) commentedThe module works with the site-wide contact form.
It works with the Mass Contact module as long as you don't use BCC addresses for sending mails.
Comment #10
deekayen commentedThere's no public release on the front of the project page still. Did the ruby library get ported? Is this all stalled out? What's going on?
Comment #11
Anonymous (not verified) commentedPlease take a look at my statement here and mcload's post.
Unfortunately, nothing has changed. :-|
On my new server the encryption with this module doesn't work. (Encryption with a script works well.) Without a dev release and without continuous development I'm not able to test the module and help to bring the module to a final release.
Comment #12
Arto commented@BENNYSOFT, there has been a dev release available since July 14. See:
http://drupal.org/node/467664/release
If you want to help contribute to this project, you need to do more than make snarky ad hominem statements. You could start by figuring out the source of the problem you are experiencing and telling me about it. Even if you are unable to contribute a patch, your input could pinpoint and enable an immediate fix.
Software doesn't write itself, and my input is limited by constraints such as sponsors' internal requirements & schedules, summer vacations, and, in the case of unsponsored modules like this one, my available time & interest to work, for free (!), on something that just happens to be useful to you, too. You understand, I hope, that my motivation to work on this project does not increase through personal attacks.
To better understand what constitutes incentives vs disincentives for open-source developers, you may wish to refer to:
http://enfranchisedmind.com/blog/posts/fyi-my-open-source-users/
Comment #13
Anonymous (not verified) commentedFirstly, you should stop writing such helpless statements. You have understood nothing.
Secondly, you should reduce the number of the projects you started and you haven't continued. Many projects and little concrete results.
I would pay for this module. But for the reasons I mentioned above I wouldn't pay you any single dollar.
Just my two cents. I waste my valuable time here.
Comment #14
Arto commented@BENNYSOFT: code talks, BS walks. Since you have nothing to contribute but abuse, please go do that somewhere else. Your trolling is unsolicited, unproductive & unwelcome here.
Comment #15
Arto commentedReturning back to the topic at hand, I have added installation instructions, fixed a couple of minor issues reported to me, and today released the first beta version of this module. This version is running fine on a number of production sites and will be released as 1.0 unless unexpected problems crop up elsewhere.
(The previously mentioned future pure-PHP version, which will lessen the GPG dependency, will then eventually be called 2.0. See ROADMAP.txt.)
Please open new issues for bug reports or feature requests.