Permissions of challenge token cause problems about getssl

[xrat]

mkdir -p "$(dirname "$to")" might also create directories with insufficient permissions.

the token is chmod 755 to ensure it's readable from the web - you are correct though, it doesn't need to be executable ( as it's a plain text file ) so 644 would work fine.

the umask is set at that to preserve the security of the keys. which specific file is it causing issues with ? and what's the ownership ?

[xrat]

The current use of umask in the script covers the keys which is good, but the directory for the challenge token and the token file itself are not covered. So, in an environment where eg umask=0077 directory and token file will be 0700 (of 0600 if you change 755 to 644).

As a quick workaround I added chmod 755 and chmod 644.

just checking my understanding - the only issue is with the generation of the token directory and the token file itself - correct ?

[xrat]

Yes, exactly. At least this was my problem.

I've updated and tested a version that worked on my systems. please check and let me know if you see any issues still.

[xrat]

Sorry for my late answer. I used getssl ver. 1.36 today on the same server, same setup, and it worked perfectly. Thanks for the fix!