| bio | website | trestletechnology.net |
|---|---|---|
| location | Dallas, TX | |
| age | ||
| visits | member for | 1 year, 1 month |
| seen | Apr 13 '12 at 4:22 | |
| stats | profile views | 5 |
|
Apr 13 |
awarded | Scholar |
|
Apr 13 |
accepted | Allow apache to write to users' .ssh dir's |
|
Apr 11 |
awarded | Editor |
|
Apr 11 |
revised |
NSA RHEL5 Checklist ADded hyperlink. |
|
Apr 11 |
suggested | suggested edit on NSA RHEL5 Checklist |
|
Apr 10 |
comment |
Allow apache to write to users' .ssh dir's Thanks; that sounds like a pretty elegant solution and doesn't sacrifice the on-demand key generation, which is nice. Might I ask why you suggest that I "look hard for alternatives" to server-side key generation? |
|
Apr 10 |
awarded | Teacher |
|
Apr 10 |
awarded | Student |
|
Apr 10 |
awarded | Supporter |
|
Apr 10 |
answered | Will passphrases always be secure? |
|
Apr 10 |
comment |
Allow apache to write to users' .ssh dir's That sounds like a better idea, for sure. Can you help me think through the specifics of such a solution, though? I would essentially need to run that script as root, correct (or, at the least, a user with sudo privileges for chmod, chgrp, and useradd)? Is there a better approach by changing the user's default groups on useradd, for instance? |
|
Apr 10 |
asked | Allow apache to write to users' .ssh dir's |