FS#2377 - (openssh package) sshd must be stande alone server, not tcp_wraper

Attached to Project: Arch Linux
Opened by Darius Kučisnkas (dariuzk) - Tuesday, 15 March 2005, 16:38 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

(openssh package) sshd must be stande alone server, not tcp_wraper.
This task depends upon

Closed by  Judd Vinet (judd)
Friday, 18 March 2005, 21:27 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Leaving wrapper support in place, I think many people use it.
Comment by Judd Vinet (judd) - Tuesday, 15 March 2005, 19:12 GMT
Why?
Comment by Darius Kučisnkas (dariuzk) - Wednesday, 16 March 2005, 14:26 GMT
It's more reliable to have sshd as stande alone server. I am concerned about bugs in wrappers (then sshd is stand alone server it's only 1 soft,
wrappers adds one more layer of soft). Wrappers slow down sshd and then sshd eats more resources of the system.
Comment by Judd Vinet (judd) - Friday, 18 March 2005, 21:26 GMT
I don't think tcp_wrappers eat up many resources. It's a simple ACL match at connect time, and it provides a nice central place to restrict/allow access.

If you really want a wrapper-less openssh, you can build a custom package in /var/abs.

Loading...