hacked - looking for doc/suggestions on hardening/securing systems from the start
badouglas at gmail.com
Thu Dec 19 18:17:38 UTC 2013
The project that the corrupt system is going to be driving will create
a distributed network of systems, where the edge systems, are tied
back into the central server(s). Think of the BOINC/SETI project,
where you have a bunch of edge systems doing "work" and communicating
back to the master system/process.
The project was looking to use secure SSH in a manner, where there are
public/private keys for the master/child servers(services) can
comunicate with each other over the specified encrypted ports/tunnels.
However, it occurs to me that if one of the master/child servers is
hacked, then the person doing the hacking could get into the connected
server via the SSH key/process.
Comments/thoughts on options that can be considered viable/secure for
the process of remotely accessing machines, that would allow for
auto/programatic connection/xfer of data?
On Thu, Dec 19, 2013 at 1:04 PM, Steven Stern
<subscribed-lists at sterndata.com> wrote:
> On 12/18/2013 11:05 AM, bruce wrote:
>> Hey guys. - subject says it all!!
>> For a basic centos/fedora install. Need to have
>> pointers/docs/suggestions/solid steps to actually harden/secure a
>> I've looked at a bunch of different articles/sites, so I'm also turning here.
>> Also, are there any good (i know) security lists/resources (people) I
>> could talk to about remotely hiring for this process..
>> 'ppreciate it!!
> Take a look at OSSEC. I have it on all my internet-accessible servers.
> -- Steve
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
More information about the users