diff options
author | Richard Levitte <levitte@openssl.org> | 2019-07-25 12:21:33 +0200 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2019-07-25 18:58:35 +0200 |
commit | d333ebaf9c77332754a9d5e111e2f53e1de54fdd (patch) | |
tree | c3e6dedf493685f8944f024f9eafe1d5f1d887c1 /INSTALL.DJGPP | |
parent | 0bc650d58a58a8b4af97639b952eac3558bb982e (diff) |
Document issue with default installation paths on diverse Windows targets
For all config targets (except VMS, because it has a completely different
set of scripts), '/usr/local/ssl' is the default prefix for installation
of programs and libraries, as well as the path for OpenSSL run-time
configuration.
For programs built to run in a Windows environment, this default is
unsafe, and the user should set a different prefix. This has been hinted
at in some documentation but not all, and the danger of leaving the
default as is hasn't been documented at all.
This change documents the issue as a caveat lector, and all configuration
examples now include an example --prefix.
CVE-2019-1552
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9456)
Diffstat (limited to 'INSTALL.DJGPP')
-rw-r--r-- | INSTALL.DJGPP | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/INSTALL.DJGPP b/INSTALL.DJGPP index 1047ec90a5..ecbf4934e9 100644 --- a/INSTALL.DJGPP +++ b/INSTALL.DJGPP @@ -33,8 +33,18 @@ running in a DOS box under Windows. If so, just close the BASH shell, go back to Windows, and restart BASH. Then run "make" again. - RUN-TIME CAVEAT LECTOR - -------------- + CAVEAT LECTOR + ------------- + + ### Default install and config paths + + ./Configure defaults to '/usr/local/ssl' as installation top. This is + suitable for Unix, but not for Windows, where this usually is a world + writable directory and therefore accessible for change by untrusted users. + It is therefore recommended to set your own --prefix or --openssldir to + some location that is not world writeable (see the example above) + + ### Entropy Quoting FAQ: |