Windows un-escaped characters (bug) in scripts to create self-signed certs

[dwk2]

Issue description

• The /scripts/proxy/ssl-certs/Local.sh and /scripts/proxy/ssl-certs/Demo.sh files both fail in Windows. Windows chokes on un-escaped characters. So the certs fail to be generated.
• Additionally, Powershell cannot run the chmod command, and cannot execute a shell script. Git for Windows is needed for its Git Bash command line.
• Also, for Windows, Git for Windows is needed as it installs openssl.exe, which the Local.sh will utilize to generate the openSSL certs.

For an issue, describe steps to reproduce the issue

Windows 10.

Steps:

$ ./local.sh
Generating a RSA private key
...................................................+++++
.........................................................+++++
writing new private key to '../../../config/proxy/ssl-certs/unbound.localdomain.key'
-----
name is expected to be in the format /type0=value0/type1=value1/type2=... where characters may be escaped by \. This name is not in that format: 'C:/Program Files/Git/C=US/O=Islandora Collaboration Group/OU=Domain Control Validated/CN=unbound.localdomain'
problems making Certificate Request

What's the expected result?

• Two certs should be generated.

What's the actual result?

• See error message above.

Additional details / screenshots

[dwk2]

This issue has been completed with the merging of PR https://github.com/Islandora-Collaboration-Group/ISLE/pull/313.