LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Security (https://www.linuxquestions.org/questions/linux-security-4/)
-   -   todays requirements regarding security (not limited to linux security) (https://www.linuxquestions.org/questions/linux-security-4/todays-requirements-regarding-security-not-limited-to-linux-security-174060/)

markus1982 04-24-2004 12:12 PM

todays requirements regarding security (not limited to linux security)
 
I'd like to hear your requirements for today's security. This should not be limited to linux security, network security and physical security.

Everybody is welcomed to post his/her comments.

klausi 04-24-2004 12:20 PM

Weel, after iīve asked my english book, what about Gamerserverīs in Chrootīs ?

Is there much work to do to chroot e.g. an Steam Cstrike 1.6 Server ?

markus1982 04-24-2004 12:27 PM

Quote:

Originally posted by klausi
Weel, after iīve asked my english book, what about Gamerserverīs in Chrootīs ?

Is there much work to do to chroot e.g. an Steam Cstrike 1.6 Server ?

Personally I consider chroots - if implemented correctly of course - as an additional layer of security. The amount of work required to chroot differs greatly from application to application. Think of statically linked binaries (MySQL for instance as a popular example) and of non-statically linked ones.

klausi 04-24-2004 12:28 PM

Cstrike issnt using sql i guess ;-)
I think, if i chroot a user and install cstrike with this, its chrooted by default..

markus1982 04-24-2004 12:31 PM

Quote:

Originally posted by klausi
Cstrike issnt using sql i guess ;-)
I think, if i chroot a user and install cstrike with this, its chrooted by default..

I never meant that CS uses SQL, more the way libraries are linked to binaries: statically or non-statically. Non-statically linked libs need to be copied to the chroot in order for the binary (daemon) to work...

unSpawn 04-24-2004 07:59 PM

I'd like to hear your requirements for today's security. This should not be limited to linux security, network security and physical security.
Maybe you could break open the discussion by voicing your own opinion on things? Maybe focus on some aspects and ask less broad questions?

chort 04-24-2004 11:01 PM

Today's requirements for security are no different than yesterday's, or last year's, or 1970's... The only thing that changes is the technology available, but the principles never change.

Given the glut of articles, guides, policies, etc written on this very same subject I'm not sure how an informal discussion adds anything (although you're certainly welcome to gather input).

unSpawn 04-25-2004 04:40 PM

I'm not sure how an informal discussion adds anything
Well, FWIW, I favour discussion, so lets get something on the table to discuss, shall we?

witeshark 04-25-2004 11:58 PM

Quote:

Originally posted by chort
Today's requirements for security are no different than yesterday's, or last year's, or 1970's... The only thing that changes is the technology available, but the principles never change.

Given the glut of articles, guides, policies, etc written on this very same subject I'm not sure how an informal discussion adds anything (although you're certainly welcome to gather input).

This is of course a very good point. Now to make this progress, I suggest discussion on the varied ways firewalls can be implemented. Hardware (router) firewall as opposed to software (iptables and rules). In both cases, the simple fact remains that if a known open port is accessed and permissions can be acquired, there is an obvious risk. To admin any system with that in mind should narrow down security rather well, I think


All times are GMT -5. The time now is 03:02 PM.