Looks like this issue was related to something that did not reach reached a released version. That being said what is described is now true all the time, but it's actually like this on purpose for security reasons so closing it as won't fix.