Posted by zzolo on November 22, 2009 at 4:10pm
5 followers
Jump to:
| Project: | Encryption |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Since there are a couple large features that are in the queue, I am deciding to stop features on current branch (1.x) and starting a new branch (2.x) for the new features:
* #573728: Utilize ctools plugins for key methods
* #607918: Combination with AES Module
* #609592: Support for PHP Secure Communications Library (phpseclib)
This means I will be releasing a 1.0 in a few moments.
Comments
#1
Do you have a timeframe on the 2x release?
#2
I haven't had much time to put towards this module in a while. I also don't have any timeline for this. I open to patches and possibly co-maintainers.
#3
Maybe have a look at the several other encryption modules (sometimes not maintained for some time) and ask their maintainers to join; maybe together there is synergy and more 'horsepower'?
Think there should be one Encryption API module that does all the possible encryptions.
Same for a 'login security API' that has to do all types of login securities , but it should use encryption methods of the Encryption API as a dependency.
Then the USB keys authentications work with USB's that have to be bought, instead of that one puts its own key on its own USB-stick
http://drupal.org/project/yubikey - http://drupal.org/project/swekey
#4
In my opinion it no longer makes sense to have a 6.x-2.x branch of this module. If people want that code they can upgrade to 7.x-2.x.
I think that the 7.x-2.x branch is very close to being ready for a final 7.x-2.0 release. If anyone else has ideas on what to improve before then please post a comment here or an issue.