samu (Jakub Szafranski)
- Login: samu
- Email: rubybugs@samu.pl
- Registered on: 02/21/2014
- Last sign in: 03/15/2014
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 1 | 1 |
Activity
03/15/2014
- 08:17 PM Ruby master Bug #9544: Ruby resolver not using autoport
- Just a little follow-up:
I still think that OS should take care of that, this is a wrong layer for me.
For inst...
02/22/2014
- 02:34 PM Ruby master Bug #9544: Ruby resolver not using autoport
- So is it ruby's concern, or should the system developers make appropriate patches?
Currently you've reinvented th... - 12:51 PM Ruby master Bug #9544: Ruby resolver not using autoport
- Akira Tanaka wrote:
> I tested several OSs and I found NetBSD 6.1.3 still doesn't randomize port:
>
> % ruby ...
02/21/2014
- 09:12 PM Ruby master Bug #9544: Ruby resolver not using autoport
- I'd like to mention that you've got a hardcoded range of ports that can be used to _bind()_, however every system ime...
- 11:01 AM Ruby master Bug #9544: Ruby resolver not using autoport
- EPERM may happen if you're using (like me) bind port filter policy. For instance, FreeBSD mac_portacl (http://www.fre...
- 12:41 AM Ruby master Bug #9544 (Closed): Ruby resolver not using autoport
- ### Problem
On one of my production servers I've noticed that customers were failing to install anything using gem...
Also available in: Atom