Feature #2454: OpenSSL has no maintainer

I am rather interested in Cryptography and have used this library before and found
the documentation rather lacking.

I would be interested in picking this project up though I am having some issues.

I've tried checking out the code through here:
http://savannah.nongnu.org/projects/rubypki/

I keep getting errors when I try to checkout using 'git cvsimport' or by using cvs.

Anyone having similar problems and or suggestions?

Well, the code for the OpenSSL extension is inside the Ruby repository, so you'll have to look for the code there. Take a look at:

http://www.ruby-lang.org/en/community/ruby-core/#following-ruby

I've been working on getting the OpenSSL extension running on Rubinius. I'm happy to finish doing some cleanup and submitting the changes back. Since we'll have our own changes, I'll be doing maintenance on it, and i'm happy to to push that maintenance into the normal OpenSSL extension.

• Status changed from Open to Assigned
• Assignee set to matz (Yukihiro Matsumoto)

Chris Saunders wrote:
> I am rather interested in Cryptography and have used this library before and found
> the documentation rather lacking.

In the long term, Chris' point is important.
Current ext/openssl is too low layer, and net/http is also low.
We should introduce another wrapper layer in the future.


Evan Phoenix wrote:
> I've been working on getting the OpenSSL extension running on Rubinius.
> I'm happy to finish doing some cleanup and submitting the changes back.
> Since we'll have our own changes, I'll be doing maintenance on it,
> and i'm happy to to push that maintenance into the normal OpenSSL extension.

Interesting suggestion.
How about this, matz?

Hi,

In message "Re: [ruby-core:27095] [Feature #2454](Assigned) OpenSSL has no maintainer"
    on Tue, 8 Dec 2009 14:23:43 +0900, Yui NARUSE <[e-mail]> writes:

|Evan Phoenix wrote:
|> I've been working on getting the OpenSSL extension running on Rubinius.
|> I'm happy to finish doing some cleanup and submitting the changes back.
|> Since we'll have our own changes, I'll be doing maintenance on it,
|> and i'm happy to to push that maintenance into the normal OpenSSL extension.
|
|Interesting suggestion.
|How about this, matz?

If Evan wants committer privilege to check in his update, I'd love to
grant him a right.  I am more than happy if he's willing to maintain
openssl extension for MRI as well, but I don't think he has offered
so.

							matz.

Hi,

In message "Re: [ruby-core:27105] Re: [Feature #2454](Assigned) OpenSSL has no maintainer"
    on Wed, 9 Dec 2009 07:09:08 +0900, Evan Phoenix <[e-mail]> writes:

|Sorry about the confusion. I'm happy to take over maintenance of the extension for MRI as well. This will allow me to have MRI and rubinius use the same extension.

Thank you!  Please send your GPG signed ssh2 public key to
<[e-mail]> with sought account name.  We will grant you
the privilege.

							matz.

• Assignee changed from matz (Yukihiro Matsumoto) to ephoenix (Evan Phoenix)

Evan, did you mail your key?

On Dec 21, 2009, at 12:53 , Evan Phoenix wrote:

> Ack. I have not. I do not have GPG installed, is there an easier way to get you my ssh2 key?

They generously allowed me to use Mail.app encryption. I know several of them are sporting macs now. :)

> On Dec 20, 2009, at 11:17 PM, Yui NARUSE wrote:
> 
>> Issue #2454 has been updated by Yui NARUSE.
>> 
>> Assigned to changed from Yukihiro Matsumoto to Evan Phoenix
>> 
>> Evan, did you mail your key?
>> ----------------------------------------
>> http://redmine.ruby-lang.org/issues/show/2454
>> 
>> ----------------------------------------
>> http://redmine.ruby-lang.org
>> 
>> 
> 
> 
> 

You can use following:
* http://macgpg.sourceforge.net/
* http://www.sente.ch/software/GPGMail/English.lproj/GPGMail.html

We need some signed message.
Following articles describes how to use GPG on Mail App on Mac OS X including Snow Leopard, but in Japanese.
Can anyone who has Snow Leopard teach him?

http://blog.macfeeling.com/old_article/gpg/gpg01
http://blog.macfeeling.com/old_article/gpg/gpg02
http://blog.macfeeling.com/old_article/gpg/gpg03
http://blog.macfeeling.com/old_article/gpg/gpg04
http://blog.macfeeling.com/old_article/gpg/gpg05

The ssh key and the GPG key are two different things.

The ssh public key lives in ~/.ssh/.id_dsa.pub.

Here's a GPG tutorial: http://aplawrence.com/Basics/gpg.html
For email encryption/signing, I've found Thunderbird + Enigmail to be an excellent combination.

• Target version set to 2.0.0

• Status changed from Assigned to Rejected
• Assignee deleted (ephoenix (Evan Phoenix))

This ticket is timeouted.