You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Full link command and output with -v appended:
N/A
When using --pre-js and friends, emcc is injecting lines into the output in the form:
// include: /path/to/input/file.js
// end include: /path/to/input/file.js
To the best of my recollection it did not always do this (i'm noticing it for the first time, in any case).
Example:
$ grep ' include:' jswasm/sqlite3-node.mjs | grep lite
// include: /home/stephan/f/s/lite/ext/wasm/bld/pre-js.sqlite3-node.js
// end include: /home/stephan/f/s/lite/ext/wasm/bld/pre-js.sqlite3-node.js
// include: /home/stephan/f/s/lite/ext/wasm/bld/post-js.sqlite3-node.js
// end include: /home/stephan/f/s/lite/ext/wasm/bld/post-js.sqlite3-node.js
The utility of having those lines in there is clear, but they're potentially security-relevant, leaking info about the build system which end users have no need to know. Every bit of leaked info about a system is a clue for potential attackers. In the case of my local system this is a non-issue, but there are plenty of sysadmins out there who are understandably more paranoid.
Edit: an example of how this is potentially security-relevant is that the paths above expose my login name to anyone reading the code. Not that that's a secret in my case, but it may well be in some users' cases.
The text was updated successfully, but these errors were encountered:
See previous discussion in #21084 . To summarize, that is only present in debug builds, and debug builds can have a lot of other local information embedded in them anyhow.
Unless you are seeing this in a release build somehow? That would be a very different matter.
Version of emscripten/emsdk:
Failing command line in full:
N/A
Full link command and output with
-v
appended:N/A
When using --pre-js and friends, emcc is injecting lines into the output in the form:
To the best of my recollection it did not always do this (i'm noticing it for the first time, in any case).
Example:
The utility of having those lines in there is clear, but they're potentially security-relevant, leaking info about the build system which end users have no need to know. Every bit of leaked info about a system is a clue for potential attackers. In the case of my local system this is a non-issue, but there are plenty of sysadmins out there who are understandably more paranoid.
Edit: an example of how this is potentially security-relevant is that the paths above expose my login name to anyone reading the code. Not that that's a secret in my case, but it may well be in some users' cases.
The text was updated successfully, but these errors were encountered: