mcarpenter (Martin Carpenter)
- Login: mcarpenter
- Email: mcarpenter@free.fr
- Registered on: 03/21/2015
- Last sign in: 02/26/2021
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 3 | 3 |
Activity
02/26/2021
-
10:04 AM Ruby Bug #17658: DNS resolution failure with multiple named resolvers
- Fixing commit is below.
#12838 states that the problem is intermittent and due to duplicate responses. That's not what I have observed: I can consistently reproduce the problem. Can this one-line change + test please be back-ported to... -
09:38 AM Ruby Bug #17658: DNS resolution failure with multiple named resolvers
- I tested ruby 3.0.0 and it works fine so I guess something got fixed:
```ruby
Resolv::DNS.new({nameserver: ['dns.google', 'one.one.one.one']}).getresources('example.com', Resolv::DNS::Resource::IN::A)
=> [#<Resolv::DNS::Resource::I... -
09:32 AM Ruby Bug #17658 (Closed): DNS resolution failure with multiple named resolvers
- ## Description
I created a `Resolv::DNS` resolver with two nameservers described using their domain names. Calling `#getresources` on this for an `A` or `NS` (and possibly other resource types) of domain `example.com` returns an empty...
04/07/2015
-
09:39 PM Ruby Bug #11047: SEGV in ruby_yyparse
- ps. originally discovered under 2.1.5
-
09:37 PM Ruby Bug #11047 (Closed): SEGV in ruby_yyparse
- Hello,
Please find attached half a dozen test cases that cause the ruby parser (either in a script or via `eval` as below) to throw a segmentation violation due to stack corruption. Using 2.2-head on Ubuntu 14.04.
To reproduce:
...
03/22/2015
-
04:02 PM Ruby Bug #10991: SIGSEGV in Marshal.load
- Nobuyoshi Nakada wrote:
> Are those dumped data generated from real objects, and expected to be loaded successfully?
Data was not generated from real objects and I would not expect them to load successfully.
I expected eg TypeErro...
03/21/2015
-
10:22 AM Ruby Bug #10991 (Closed): SIGSEGV in Marshal.load
- I've fuzzed some crashes in the marshal loader. The docs are explicit about not handing untrusted data to these methods and all appear to be `NULL` derefs from `RSTRING_PTR()` (I checked the first few by hand and ran exploitable over the...