[#46049] [ruby-trunk - Feature #6590] Dealing with bigdecimal, etc gems in JRuby — "mrkn (Kenta Murata)" <muraken@...>
4 messages
2012/07/01
[#46078] [ruby-trunk - Feature #2565] adding hooks for better tracing — "mame (Yusuke Endoh)" <mame@...>
4 messages
2012/07/01
[#46108] Re: [ruby-trunk - Feature #2565] adding hooks for better tracing
— Aaron Patterson <tenderlove@...>
2012/07/02
On Mon, Jul 02, 2012 at 03:06:59AM +0900, mame (Yusuke Endoh) wrote:
[#46127] [ruby-trunk - Feature #2565] adding hooks for better tracing — "vo.x (Vit Ondruch)" <v.ondruch@...>
4 messages
2012/07/03
[#46160] [ruby-trunk - Feature #6693][Open] Don't warn for unused variables starting with _ — "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
15 messages
2012/07/04
[#46163] [ruby-trunk - Feature #6695][Open] Configuration for Thread/Fiber creation — "ko1 (Koichi Sasada)" <redmine@...>
7 messages
2012/07/04
[#46172] [ruby-trunk - Feature #6697][Open] [PATCH] Add Kernel#Symbol conversion method like String(), Array() etc. — "madeofcode (Mark Dodwell)" <mark@...>
7 messages
2012/07/04
[#46236] [ruby-trunk - Bug #6704][Open] Random core dump — "trans (Thomas Sawyer)" <transfire@...>
7 messages
2012/07/07
[#46248] building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06 — Perry Smith <pedzsan@...>
I am just now starting to debug this but hoped someone has already blazed this trail.
10 messages
2012/07/08
[#46251] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Yutaka Kanemoto <kinpoco@...>
2012/07/08
Hi Perry
[#46252] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Perry Smith <pedzsan@...>
2012/07/08
[#46254] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Perry Smith <pedzsan@...>
2012/07/08
[#46259] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Perry Smith <pedzsan@...>
2012/07/09
[#46266] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Yutaka Kanemoto <kinpoco@...>
2012/07/09
Hi Perry,
[#46276] Lambdaification of Method Calls — Robert Klemme <shortcutter@...>
Hi,
3 messages
2012/07/09
[#46320] [ruby-trunk - Feature #6721][Open] Object#yield_self — "alexeymuranov (Alexey Muranov)" <redmine@...>
25 messages
2012/07/11
[#46339] [ruby-trunk - Bug #6724][Open] waaaaaaant! ( — "zenspider (Ryan Davis)" <redmine@...>
11 messages
2012/07/11
[#46537] Re: [ruby-trunk - Bug #6724][Open] waaaaaaant! (
— Aaron Patterson <tenderlove@...>
2012/07/17
On Thu, Jul 12, 2012 at 08:58:36AM +0900, zenspider (Ryan Davis) wrote:
[#46540] Re: [ruby-trunk - Bug #6724][Open] waaaaaaant! (
— Luis Lavena <luislavena@...>
2012/07/18
On Tue, Jul 17, 2012 at 6:27 PM, Aaron Patterson
[#46377] [ruby-trunk - Feature #6727][Open] Add Array#rest (with implementation) — "duckinator (Nick Markwell)" <nick@...>
25 messages
2012/07/13
[#46420] [ruby-trunk - Feature #6731][Open] add new method "Object.present?" as a counter to #empty? — "rogerdpack (Roger Pack)" <rogerpack2005@...>
4 messages
2012/07/14
[#46500] [ruby-trunk - Feature #6739][Open] One-line rescue statement should support specifying an exception class — Quintus (Marvin Gülker) <sutniuq@...>
22 messages
2012/07/15
[#46535] [ruby-trunk - Bug #6749][Open] rdoc of Time class (incorrect explanation of leap seconds) — "stomar (Marcus Stollsteimer)" <redmine@...>
7 messages
2012/07/17
[#46687] [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— "drbrain (Eric Hodel)" <drbrain@...7.net>
2012/07/23
[#46713] Re: [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— sto.mar@...
2012/07/24
Hi Eric,
[#46734] Re: [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— Eric Hodel <drbrain@...7.net>
2012/07/24
On Jul 23, 2012, at 11:52 PM, sto.mar@web.de wrote:
[#46763] Re: [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— sto.mar@...
2012/07/25
Am 24.07.2012 19:44, schrieb Eric Hodel:
[#46546] Fwd: [ruby-cvs:43609] ko1:r36433 (trunk): * thread.c (rb_thread_call_without_gvl2): added. — SASADA Koichi <ko1@...>
Hi,
4 messages
2012/07/18
[#46547] Re: Fwd: [ruby-cvs:43609] ko1:r36433 (trunk): * thread.c (rb_thread_call_without_gvl2): added.
— Eric Wong <normalperson@...>
2012/07/18
SASADA Koichi <ko1@atdot.net> wrote:
[#46553] [ruby-trunk - Feature #2565] adding hooks for better tracing — "tenderlovemaking (Aaron Patterson)" <aaron@...>
4 messages
2012/07/18
[#46564] Ruby under CI - Windows — Luis Lavena <luislavena@...>
Hello,
6 messages
2012/07/20
[#46574] [ruby-trunk - Feature #6762][Open] Control interrupt timing — "ko1 (Koichi Sasada)" <redmine@...>
39 messages
2012/07/20
[#46575] [ruby-trunk - Feature #6762] Control interrupt timing
— "ko1 (Koichi Sasada)" <redmine@...>
2012/07/20
[#46576] Re: [ruby-trunk - Feature #6762] Control interrupt timing
— Eric Wong <normalperson@...>
2012/07/20
"ko1 (Koichi Sasada)" <redmine@ruby-lang.org> wrote:
[#48390] [ruby-trunk - Feature #6762] Control interrupt timing
— "ko1 (Koichi Sasada)" <redmine@...>
2012/10/26
[#50542] Re: [ruby-trunk - Feature #6762][Open] Control interrupt timing
— Brent Roman <brent@...>
2012/12/03
I was suggesting "interruptible" as a better alternative for
[#46577] [ruby-trunk - Feature #6763][Open] Introduce Flonum technique to speedup floating computation on th 64bit environment — "ko1 (Koichi Sasada)" <redmine@...>
7 messages
2012/07/20
[#46586] [ruby-trunk - Bug #6764][Open] IO#read(size, buf) causes can't set length of shared string in trunk (2.0.0dev) — "nahi (Hiroshi Nakamura)" <nakahiro@...>
4 messages
2012/07/21
[#46641] [ruby-trunk - Bug #6780][Open] cannot compile zlib module, when cross-compiling. — "jinleileiking (lei king)" <jinleileiking@...>
14 messages
2012/07/23
[#46686] [ruby-trunk - Bug #6784][Open] Test failures related to numeric with x64 mingw — "h.shirosaki (Hiroshi Shirosaki)" <h.shirosaki@...>
5 messages
2012/07/23
[#46741] [ruby-trunk - Bug #6789][Open] parse.y compilation error due not updated id.h — "luislavena (Luis Lavena)" <luislavena@...>
8 messages
2012/07/24
[#46742] [ruby-trunk - Bug #6789][Assigned] parse.y compilation error due not updated id.h
— "luislavena (Luis Lavena)" <luislavena@...>
2012/07/24
[#46744] [ruby-trunk - Bug #6791][Open] ext/js on/generator/generator.c fails to compile on nightly build (AIX 6.1) — "pedz (Perry Smith)" <pedz@...>
4 messages
2012/07/25
[#46752] Re: [ruby-trunk - Bug #6791][Open] ext/js on/generator/generator.c fails to compile on nightly build (AIX 6.1)
— Yutaka Kanemoto <kinpoco@...>
2012/07/25
Hi Perry,
[#46772] Ruby 1.9.3 release? — Charles Oliver Nutter <headius@...>
JRuby will soon release 1.7.0pre2, the second preview of 1.7. Perhaps
6 messages
2012/07/25
[#46847] Re: Ruby 1.9.3 release?
— "NARUSE, Yui" <naruse@...>
2012/07/29
(2012/07/26 7:07), Charles Oliver Nutter wrote:
[#46864] Re: Ruby 1.9.3 release?
— Luis Lavena <luislavena@...>
2012/07/29
On Sat, Jul 28, 2012 at 10:59 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
[#46792] [ruby-trunk - Bug #6799][Open] Digest::*.hexdigest returns an ASCII-8BIT String — "Eregon (Benoit Daloze)" <redmine@...>
11 messages
2012/07/26
[#46832] [ruby-trunk - Bug #6807][Open] Can't compile ruby without ruby — "devcurmudgeon (Paul Sherwood)" <storitel@...>
13 messages
2012/07/28
[#46834] [ruby-trunk - Feature #6808][Open] Implicit index for enumerations — "trans (Thomas Sawyer)" <transfire@...>
15 messages
2012/07/28
[#46838] [ruby-trunk - Bug #6810][Open] `module A::B; end` is not equivalent to `module A; module B; end; end` with respect to constant lookup (scope) — "alexeymuranov (Alexey Muranov)" <redmine@...>
17 messages
2012/07/28
[#46854] [ruby-trunk - Feature #6811][Open] File, Dir and FileUtils should have bang-versions of singleton methods that fails silently — "prijutme4ty (Ilya Vorontsov)" <prijutme4ty@...>
7 messages
2012/07/29
[#46896] (Half-baked DRAFT) new `require' framework — SASADA Koichi <ko1@...>
Hi,
22 messages
2012/07/31
[#46897] Re: (Half-baked DRAFT) new `require' framework
— =?KOI8-R?B?4NLJyiDzz8vPzM/X?= <funny.falcon@...>
2012/07/31
2012/7/31 SASADA Koichi <ko1@atdot.net>
[#46899] Re: (Half-baked DRAFT) new `require' framework
— Alex Young <alex@...>
2012/07/31
On 31/07/12 13:29, SASADA Koichi wrote:
[#46902] Re: (Half-baked DRAFT) new `require' framework
— Trans <transfire@...>
2012/07/31
On Tue, Jul 31, 2012 at 12:07 PM, Alex Young <alex@blackkettle.org> wrote:
[#46903] Re: (Half-baked DRAFT) new `require' framework
— Clifford Heath <clifford.heath@...>
2012/07/31
On 01/08/2012, at 5:59 AM, Trans wrote:
[#47040] Re: (Half-baked DRAFT) new `require' framework
— SASADA Koichi <ko1@...>
2012/08/07
(2012/07/31 21:29), SASADA Koichi wrote:
[#47054] Re: (Half-baked DRAFT) new `require' framework
— Rocky Bernstein <rockyb@...>
2012/08/07
If one is considering importing archive files like zip, tar, jar, or gem, I
[#47056] Re: (Half-baked DRAFT) new `require' framework
— Charles Oliver Nutter <headius@...>
2012/08/07
On Tue, Aug 7, 2012 at 8:48 AM, Rocky Bernstein <rockyb@rubyforge.org> wrote:
[ruby-core:46100] [ruby-trunk - Feature #5741] Secure Erasure of Passwords
From:
"kenkeiter (Ken Keiter)" <ken@...>
Date:
2012-07-02 05:55:20 UTC
List:
ruby-core #46100
Issue #5741 has been updated by kenkeiter (Ken Keiter). Is there any update on the status of this issue? This is simply a layperson's perspective (I'm not an expert regarding Ruby's internals), but I'd imagine this to be as easy as querying GC for all copies of the object, and overwriting the memory locations upon request? I can dig into the internals if I need to; I'd just love to get this on the roadmap! ---------------------------------------- Feature #5741: Secure Erasure of Passwords https://bugs.ruby-lang.org/issues/5741#change-27705 Author: MartinBosslet (Martin Bosslet) Status: Assigned Priority: Normal Assignee: matz (Yukihiro Matsumoto) Category: Target version: 2.0.0 In other languages it is considered good practice to securely erase passwords immediately after they were used. Imagine authentication in a web app - ultimately a String containing the password arrives at the server, where it will be processed and compared to some previously stored value. After this is done, there is no need to store these password Strings any longer, so they should be discarded right away (more on why later). In C, you would simply overwrite the array of bytes with zeroes or random values. In Java, Strings are immutable, that's why there it is common practice to use char[] for all things password and overwrite them when done. Currently, there is no way in Ruby to overwrite the memory that was used by a String. String#clear and String#replace both use str_discard internally, which only frees the underlying pointer without overwriting it. The problem with not erasing passwords is this: the contents of the String stay in memory until they are finally GC'ed. But even then only the pointer will be freed, leaving the contents mostly intact until the memory is reclaimed and overwritten later on. This could be exploited if an attacker had access to the memory of the server. This could happen in many ways: a core dump after a crash, access to the host if the server runs in a VM, or even by deep-freezing the DRAM :) [1] It could be argued that given the examples above, much more devastating attacks would be possible since in all of those cases you more or less have physical access to the machine. But I would still consider this to be a valid concern, if not only for the reason of never opening additional attack surfaces if they can be avoided relatively easily. I also found [2], which seems to show that Python deals with similar problems and it also contains more background info. Eric Hodel and I discussed this yesterday and Eric came up with a C extension that can be used to illustrate the problem (attached). If you inspect the resulting core dump, you will find the following: - the untouched String remains in memory fully intact - the String#clear'ed String remains to a large extent, typically the first character is missing - so if you typed "PASSWORD", search for "ASSWORD" (unintentional pun) instead - The String#clear_secure'ed will have been completely erased, no traces remain My questions: 1. Would you agree that we need this functionality? 2. Where would we ideally place it? I'm not sure whether String is the perfect place, but on the other hand, String is the only place where we have access to the implementation details. 3. Are there better alternative ways how we could achieve this? [1] http://www.schneier.com/blog/archives/2008/02/cold_boot_attac.html [2] http://stackoverflow.com/questions/728164/securely-erasing-password-in-memory-python -- http://bugs.ruby-lang.org/