The same way every website and every body on this earth do with cpanel serversI think not so good idea how to deal with updates/changes then?
What if only one ip / technician has gone or has become bad, most of the time they don't let others know about such things if someone left or fired!The same way every website and every body on this earth do with cpanel servers
ofcourse we need to whitelist ips of technicians , I have been doing it for the last 15 years or so with cpanel
what makes it different with directadmin?
You will receive a unique public SSH key for each server for which you submit information. You will also receive a list of cPanel Support-sanctioned IP addresses:
You did not understand my point at all.What if only one ip / technician has gone or has become bad, most of the time they don't let others know about such things if someone left or fired!
So only pointing out my opinion about probable insecure / less secure behavour!
If not automated update after breach or update / change it is not so good idea ?
This is more then only ips' at cpanel ?!?
this at their site documentation.cpanel.net/display/CKB/How+to+Authenticate+your+Server+for+cPanel+Technical+SupportLOL what are you talking about?#$#%#
They use VPN so hardly ips change All my servers are restricted to my ip too.this at their site documentation.cpanel.net/display/CKB/How+to+Authenticate+your+Server+for+cPanel+Technical+Support
IP 's themselves are changing much faster an more frequently then 15 years ago also IPV6 ???
BOXES with only IPv4 are way to old , not modern enough for some years now. ( IF for public webaccess )
so per ticket or support moment you see what they need, normally not that much support needed, so on a support event base to have white list ip/s/ and authentication is much much more safer.