Red Hat

Hi,

Since everything is doable in Linux so far, what is the ability of changing a spicifc service name permanently. e.g. I want to change the network service name to connection, so I can use chkconfig command as follow:

Code:

chkconfig connection off --level 5

# for disabling network service in level 5..

and in the same time..

Code:

service connection restart

# that is for restarting network service.

Thanks

One wonders why, but I suppose you could rename /etc/init.d/network to /etc/init.d/connection initially. Then you would need to search down /etc/rc.d for S*network. I get these:-

Code:

$ cd /etc/rc.d
ls -l *|grep network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 K90network -> ../init.d/network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 K90network -> ../init.d/network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 S10network -> ../init.d/network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 S10network -> ../init.d/network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 S10network -> ../init.d/network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 S10network -> ../init.d/network
lrwxrwxrwx. 1 root root 17 Dec  2  2012 K90network -> ../init.d/network

You would then have to delete/overwrite all these links to point them to ../init.d/connection instead.

I'm not sure I would want to take the risk of this. There is a chance that upgrades may want to adjust the /etc/init.d/network script and you could miss them and leave yourself very confused as to what's happened.

Can you really justify the effort against the risk just for a name change?




Robin
Liverpool/Blackburn
UK

Creating a standard giving more secure to the servers. Picture this, if any hacker logged into my system and found all crazy names for the services, what will he gonna do!?
A lot of ideas in my mind, concerning secure the system working beside iptables and SELinux, I need to create a shield that can't be broken even by the people with high experience.

Hope I have been clear in this.

iptables and SELinux offer real security. Security by obscurity doesn't.

Understand this: If he has the power to start and stop services, the battle is already lost. He could ignore them and install his own, rootkit you, replace everything, do whatever he wanted.

Yes sir this is also under my consideration, I know it's kind of crazy, but let me try it. I want also to change the service command name, and the reboot command, and any other command could effect the system.

In other word, I want to keep the system as is, but in the same time I wanna give different names for the services and any command under /sbin directory.
I hope that everybody here understand my point, I do highly respect iptables and SELinux as a security systems for sure, but I want to add more security to the system, changing all the effective commands (and paths if available ).

On the other hand, what if I want to run a special service in a specific time in my system and I don't want anybody knows what this service do (like monitoring service for bad users or admins), and I want in the same time change this service name to a misleading name, no one can discover this service, and that's why I want am alternative service instead of crond (see my other topic in this forum), to schedule this service in the dark . This is for sure should be done with filtering any log files that made by this.
The thing that I do believe with, is Linux doable, and can do it. Any suggestions and criticizes are most welcomed.

The point here is that you're not adding any security whatsoever by renaming services because a service's name has nothing whatsoever to do with security, and anyone who's already got unauthorised entry into your system is way ahead of you, and won't be there to look at your services!

SELinux has to do with protecting your system against attacks via services. Did you consider what impact your changes might have on that?

And if you rename reboot are you also going to rename halt and shutdown? No problem, I can still change runlevels using init. Or do you plan to rename that, too?

It seems to me that you're not focussing on security at all, but just on changing things because you can, and the cost of that is that you're probably making your system less secure as a result.