For security I would add one additional caution. When executing a command
wherever possible use the full pathname. To prevent running a malicious file
hidden in your PATH.
Example: “/bin/ls” and not “ls”
Darryl Baker (he/him/his)
Sr. System Administrator
Distributed Application Platform
, "SurfShop" <contactat...@surfshopcart.com> wrote:
> On Jan 25, 2018, at 10:43 AM, Darryl Philip Baker
<darryl.ba...@northwestern.edu> wrote:
>
> If you do not know TLS 1.0 and TLS 1.1 have a vulnerability in the design
of the protocol and they are being dep
If you do not know TLS 1.0 and TLS 1.1 have a vulnerability in the design of
the protocol and they are being deprecated. Currently only TLS 1.2 now and TLS
1.3 when finalized are considered safe. TLS 1.2 was defined in August of 2008
so if you are using anything developed in the last five years
I don't have the time to put everything around this to do the syntax test but
what happens with this:
If ( ! chdir
"/big/dom/x$server/data/students/$progress_hash{student_id}/" ) {
$message = "Can't change directory to $progress_hash{student_id}:
$!";
I settled for an set of stacked if statements, saving the previous line if
needed etc...
Thanks for the help.
Darryl Baker
PMOET -DAPS
X76674
On Thu, Jul 14, 2016 at 10:50 AM, Darryl Philip Baker
<darryl.ba...@northwestern.edu> wrote:
While not truly a beginner it feels that way after not doing anything
substantial in Perl in many years.
I currently need a program to take Apache HTTPD configuration files in HTTPD
2.2 synta
While not truly a beginner it feels that way after not doing anything
substantial in Perl in many years.
I currently need a program to take Apache HTTPD configuration files in HTTPD
2.2 syntax used in current production and convert them to HTTPD 2.4 syntax in
future production. I will need to
