of information is tldp.org
The Linux documentation Project
they are constantly working on including distro agnostic documentation for as many different packages as they can. Being volunteer driven they suffer from a lack of manpower, but they have a very complete set of documentation viewable online, most of which is also included in all distros. [ the how tos in the docs. ]
I tend to look for answers in the docs before looking for answers from people, since I learn more, and usually find the answers that way. :)
if TLDP doesn't have anything that helps, then the software package's specific help resources, usually email list based, or irc based, is the next best source.
I just recently checked out a special configuration question for ssh, which I was able to get the issue resolved through the ssh help email list. :)
a configuration setting that limits root access to a remote system to a "trusted" group of people, by stopping su from being used unless they are on a specific machine on their end.
[pre]
Easy... Compile sshd with the match keyword patch
(http://bugzilla.mindrot.org/show_bug.cgi?id=1180),
and use it to ensure that members of the admin group can only log in using public/private key
authentication.
Also make these users a member of the wheel group, and ensure that only they can su - check out etc/pam.d/su.
For example, in /etc/ssh/sshd_config add:
Match Group admins
PubkeyAuthentication yes
PasswordAuthentication no
ChallengeResponseAuthentication no
In /etc/pam.d/su ensure the following is uncommented:
# Uncomment the following line to require a user to be in the "wheel" group.
auth required
/lib/security/$ISA/pam_wheel.so use_uid
I use this method to ensure that admins can only log in using public/private keys and have access to perform admin functions while (hopefully) ensuring that "normal" users cannot mess about.
This also has the advantage that if any user uploads their own keys to ~/.ssh that they will not be able to gain admin rights!!!
[/pre]