[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>

All, I needed a nonblocking socket connect for my asynchronous-event

18 messages 2006/05/14
[#7873] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/14

In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,

[#7874] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about introducing the method Socket#set_nonblocking, or alternatively

[#7875] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

[#7876] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

Well, it's ok then. I'm comfortable adding in the nonblocking

[#7877] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

Re: (security-related) patch to ALLOC macros to prevent integer overflow bugs

From: Yukihiro Matsumoto <matz@...>
Date: 2006-05-04 14:21:38 UTC
List: ruby-core #7820
Hi,

In message "Re: (security-related) patch to ALLOC macros to prevent integer overflow bugs"
    on Thu, 4 May 2006 10:14:00 +0900, "Dominique Brezinski" <dominique.brezinski@gmail.com> writes:

|While fixing the integer overflow in rb_ary_fill(), it occurred to me
|it would be better to fix the *ALLOC* macros in ruby.h. The patch is
|not perfect (though make test-all passes), and I will enumerate the
|issues I see with it (most likely a subset of the true issues). Here
|is the patch against 1.8.4:

1.9.0 has code against integer overflow attack.  If someone could
review the code from CVS trunk, I can backport it to 1.8.

							matz.

In This Thread