Skip to main content
added 430 characters in body
Source Link
Dave
  • 127
  • 2

It mightYour program may be a ideasubject to hacking etc. One way to protect yourself from this type of activity is to create a copy of your current machine envronment and run any child processyour program using a system called chroot.

From viewpoint of your program its executing in a normal envronment, from a security aspect, if somebody breaks your program it only has access to the elements you provided when you made the copy.

Such a setup is called a chroot jail for more details see chroot jail chroot jail to resolve some of the security aspects.

Its normally used for setting up publicly accessible servers etc.

It might be a idea to run any child process in a chroot jail chroot jail to resolve some of the security aspects.

Your program may be subject to hacking etc. One way to protect yourself from this type of activity is to create a copy of your current machine envronment and run your program using a system called chroot.

From viewpoint of your program its executing in a normal envronment, from a security aspect, if somebody breaks your program it only has access to the elements you provided when you made the copy.

Such a setup is called a chroot jail for more details see chroot jail.

Its normally used for setting up publicly accessible servers etc.

Source Link
Dave
  • 127
  • 2

It might be a idea to run any child process in a chroot jail chroot jail to resolve some of the security aspects.