JDK-8285445 'cannot open file "NUL:"' Windows issue and Potential Respin
Andrew Hughes
gnu.andrew at redhat.com
Thu Apr 28 16:02:15 UTC 2022
Hi all,
8u332 introduced a regression via one of the security fixes which
leads to "NUL:" no longer being usable as a filename on Windows
platforms.
There are already workarounds in place for this; "NUL" will work as
will passing -Djdk.io.File.enableADS=true
There is a fix already in trunk and several Oracle trees which turns
enableADS on by default, so that the current failing behaviour is only
seen when -Djdk.io.File.enableADS=false
Now that the security updates have been merged to 8u-dev [0], we will
be integrating this fix. It will thus appear in the 8u342 release in
July.
What I'm wondering is if people see this as a critical enough issue
to do an 8u335 respin now with this change, rather than waiting for
July? Have you encountered this problem? Are you already having
to patch it locally in your builds?
Note that this only affects the Windows platform, so an 8u335 release
on other platforms would be identical to 8u332 and so there is no
need to rebuild there.
[0] https://github.com/openjdk/jdk8u-dev/commit/65c4a5d42e05135754774406389b903e2146758c
Thanks,
--
Andrew :)
Pronouns: he / him or they / them
Senior Free Java Software Engineer
OpenJDK Package Owner
Red Hat, Inc. (http://www.redhat.com)
PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222
More information about the jdk8u-dev
mailing list