[#10193] String.ord — David Flanagan <david@...>

Hi,

41 messages 2007/02/05
[#10197] Re: String.ord — Yukihiro Matsumoto <matz@...> 2007/02/06

Hi,

[#10198] Re: String.ord — David Flanagan <david@...> 2007/02/06

Yukihiro Matsumoto wrote:

[#10199] Re: String.ord — Daniel Berger <djberg96@...> 2007/02/06

David Flanagan wrote:

[#10200] Re: String.ord — David Flanagan <david@...> 2007/02/06

Daniel Berger wrote:

[#10208] Re: String.ord — "Nikolai Weibull" <now@...> 2007/02/06

On 2/6/07, David Flanagan <david@davidflanagan.com> wrote:

[#10213] Re: String.ord — David Flanagan <david@...> 2007/02/06

Nikolai Weibull wrote:

[#10215] Re: String.ord — "Nikolai Weibull" <now@...> 2007/02/06

On 2/6/07, David Flanagan <david@davidflanagan.com> wrote:

[#10216] Re: String.ord — David Flanagan <david@...> 2007/02/07

Nikolai Weibull wrote:

[#10288] Socket library should support abstract unix sockets — <noreply@...>

Bugs item #8597, was opened at 2007-02-13 16:10

12 messages 2007/02/13

[#10321] File.basename fails on Windows root paths — <noreply@...>

Bugs item #8676, was opened at 2007-02-15 10:09

11 messages 2007/02/15

[#10323] Trouble with xmlrpc — James Edward Gray II <james@...>

Some of the Ruby code used by TextMate makes use of xmlrpc/

31 messages 2007/02/15
[#10324] Re: Trouble with xmlrpc — "Berger, Daniel" <Daniel.Berger@...> 2007/02/15

> -----Original Message-----

[#10326] Re: Trouble with xmlrpc — James Edward Gray II <james@...> 2007/02/15

On Feb 15, 2007, at 1:29 PM, Berger, Daniel wrote:

[#10342] Re: Trouble with xmlrpc — James Edward Gray II <james@...> 2007/02/16

While I am complaining about xmlrpc, we have another issue. It's

[#10343] Re: Trouble with xmlrpc — Alex Young <alex@...> 2007/02/16

James Edward Gray II wrote:

[#10344] Re: Trouble with xmlrpc — James Edward Gray II <james@...> 2007/02/16

On Feb 16, 2007, at 12:08 PM, Alex Young wrote:

Re: [ ruby-Bugs-8903 ] openssl segmentation fault

From: Sam Roberts <sroberts@...>
Date: 2007-02-27 18:55:03 UTC
List: ruby-core #10444
On Tue, Feb 27, 2007 at 10:08:44AM +0900, noreply@rubyforge.org wrote:
> Initial Comment:
> I am not sure if this should be reported but I am getting a segmentation fault with the final line of the following code:
> 
> require 'openssl'
> require 'digest/sha2'
> c = OpenSSL::Cipher::Cipher.new("aes-256-cbc")
> c.encrypt
> c.key = key = Digest::SHA2.digest("yourpass")
> c.iv = iv = c.random_iv
> e = c.update("crypt this")
> OpenSSL::Debug = true
> e << c.final
> 
> (irb):9: [BUG] Segmentation fault
> 
> I realise that it is a typo to have Digest::SHA2.digest("yourpass") and not Digest::SHA256.digest("yourpass") but I figure it still shouldn't segfault.

I can't reproduce on my system, Ubuntu, with openssl 0.9.8b 04 May 2006,
and ruby 1.8.6 (2007-02-28 patchlevel 5000) [i686-linux].

Could you provide the stack backtrace from gdb? Do

 gdb <your ruby> core
 > bt


SHA2 is same as SHA256, they result in the same 32 byte key, so I don't
see how that is what is causing this. Are you saying if you use
Digest::SHA256 you *don't* get a segfault? What about if you use "x"*32
as a key?


Maybe you know, but running a straight digest on a password is not a
recomended way of generating a key from a pass phrase, it is quite
easily subject to attack. You might consider using Cipher#pkcs5_keyivgen().

Sam


In This Thread

Prev Next