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 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 instance: if a system is trying to choose a free port - either random or sequential - it will randomize from a pool of *free...
02/22/2014
-
- So is it ruby's concern, or should the system developers make appropriate patches?
Currently you've reinvented the wheel in a very bad way - it is unusable with nsswitch, it is unusable with custom firewall policies, unusable with cu... -
- Akira Tanaka wrote:
> I tested several OSs and I found NetBSD 6.1.3 still doesn't randomize port:
> ...
02/21/2014
-
- I'd like to mention that you've got a hardcoded range of ports that can be used to _bind()_, however every system imeplents its own method to change that range - for instance to lower the minimum port, or keep users in ports from range 6...
-
- EPERM may happen if you're using (like me) bind port filter policy. For instance, FreeBSD mac_portacl (http://www.freebsd.org/doc/handbook/mac-portacl.html) provides such a feature, to prevent users from running their own daemons on port...
-
- ### Problem
On one of my production servers I've noticed that customers were failing to install anything using gem and the latest ruby. After a bit of debugging we've found out, that it's related to ruby resolve module: