The following warnings occurred:
Warning [2] "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? - Line: 613 - File: inc/plugins/myadvertisements.php PHP 7.3.33 (Linux)
File Line Function
/inc/class_plugins.php 38 errorHandler->error
/inc/class_plugins.php 38 require_once
/inc/init.php 239 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once
Warning [2] "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? - Line: 654 - File: inc/plugins/myadvertisements.php PHP 7.3.33 (Linux)
File Line Function
/inc/class_plugins.php 38 errorHandler->error
/inc/class_plugins.php 38 require_once
/inc/init.php 239 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once
Warning [2] "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? - Line: 701 - File: inc/plugins/myadvertisements.php PHP 7.3.33 (Linux)
File Line Function
/inc/class_plugins.php 38 errorHandler->error
/inc/class_plugins.php 38 require_once
/inc/init.php 239 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once
Warning [2] "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? - Line: 749 - File: inc/plugins/myadvertisements.php PHP 7.3.33 (Linux)
File Line Function
/inc/class_plugins.php 38 errorHandler->error
/inc/class_plugins.php 38 require_once
/inc/init.php 239 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once
Warning [2] "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? - Line: 801 - File: inc/plugins/myadvertisements.php PHP 7.3.33 (Linux)
File Line Function
/inc/class_plugins.php 38 errorHandler->error
/inc/class_plugins.php 38 require_once
/inc/init.php 239 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What are the possible risks of enabling Shell Access for Shared Hosting clients ?
#1
Hi Guys,

I have heard a lot that "do not enable shell access for shared hosting customers". I never understand why that should not be given to customers  by default .  What should be a proper procedure for some one who wish to get shell access

Can some one shed some light on this ?
Reply
#2
In My opinion, You can give Jail Shell / Chrooted Shell Access for sure but Giving bash Shell access should be restricted fully. Main issue is mostly of those who comes in the hosting field do not have any idea about the importance of strong password and thus gets hacked / compromised easily. Think a password which is like password or passw0rd or the cpanel / linux username itself like testuser / testuser. In my expereience I have seen this a lot in my career.

So In my opinion, this should be restricted and only given when they really need it and then should ne disabled back by the suppor team.
Reply
#3
Yes , Edward is right and I guess we should not give shell access unless asking the purpose and for shared hosting and reseller hosting this should be strictly followed. One of my old hosting company was following a method like, customers will have to open tickets for enabling the same and then we will ask the purpose and will disable back once the purpose is completed . We normally add a followup in Kayako Helpdesk so that we will get a reminder to turn off the same.
#####
Linux Server Administrator 
More than 10 years of experience in Linux server and Hosting Outsourced support
ServerTechnicians.com
Reply
#4
Thanks a lot guys.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)