https://i.imgur.com/bgoHpok.png

Why does ACEMD3 log all of my folders at savepoints and print them clear?
Any reasonable explanation?

It's the BOINC wrapper. It's compiled in debug mode so it prints out a bit of the strings (a few chars from the path names, mostly "programdata" or translations) which are still allocated at the wrapper exit. You should be able to hide your PCs and workunits with preferences.

You should be able to hide your PCs and workunits with preferences.

Can't see anything related to that. Would you point me where to look?

You should be able to hide your PCs and workunits with preferences.

Can't see anything related to that. Would you point me where to look?

https://www.gpugrid.net/prefs.php?subset=project

Should GPUGRID show your computers on its web site? yes

Well, it could show my computers, not the damn folder tree.
And jeez why on earth it shall show my folders, out of the boinc tree?

Well, it could show my computers, not the damn folder tree.
And jeez why on earth it shall show my folders, out of the boinc tree?

I don't understand what it is you are seeing.
All I see on ANY BOINC project are my Computers page which only shows the Details of the host hardware and the Tasks assigned to it.

It also shows the current host RAC and host Totals. Nothing more. No other information about the host is leaked.

You must have some sort of weird operating system environment.

Well, it could show my computers, not the damn folder tree.
And jeez why on earth it shall show my folders, out of the boinc tree?

Put the blame on Windows.

I don't see any of that in Linux.

Stderr output
<core_client_version>7.17.0</core_client_version>
<![CDATA[
<stderr_txt>
13:58:20 (491): wrapper (7.7.26016): starting
13:58:20 (491): wrapper (7.7.26016): starting
13:58:20 (491): wrapper: running acemd3 (--boinc input --device 2)
14:37:08 (491): acemd3 exited; CPU time 2325.436945
14:37:08 (491): called boinc_finish(0)

</stderr_txt>
]]>

Well, it could show my computers, not the damn folder tree.
And jeez why on earth it shall show my folders, out of the boinc tree?

Your partial folder tree that it displays is a standard BOINC installation tree.

It is a partial tree and nothing there uniquely identifies you, nor poses a security risk.

As Keith mentioned, if security is high on your list, you can hide your computers, as you have done.

Well, it could show my computers, not the damn folder tree.
And jeez why on earth it shall show my folders, out of the boinc tree?

I don't understand what it is you are seeing.

Look at the image I linked in the first message.
It logs folders set in search path.

Well, it could show my computers, not the damn folder tree.
And jeez why on earth it shall show my folders, out of the boinc tree?

I don't understand what it is you are seeing.

Look at the image I linked in the first message.
It logs folders set in search path.

You made the ascii text unreadable with that red mark, but the funny thing is that the hex numbers after the unreadable text encode the same information. So now I know that your given host has an environmental setting of TMP=D:\ProgramDa... The only information which is leaked that your host has a D: drive (as every Windows has a hidden system folder called ProgramData, usually in the root of the C: drive).
Being such an ingenious hacker as I am, I still don't know how on Earth could I use it for my nefarious purposes.

And still no one knows why it does that. Still a security issue IMHO

And still no one knows why it does that.

We do.
As it is stated by Toni right after your question: it's not the GPUGrid app, but the BOINC wrapper does it because it was compiled in "debug" mode so it prints out some app and system related strings to help debug the connection between the app and the BOINC wrapper.
The BOINC wrapper is not GPUGrid's "product".

Still a security issue IMHO

I don't agree with you.

And still no one knows why it does that.

We do.
As it is stated by Toni right after your question: it's not the GPUGrid app, but the BOINC wrapper does it because it was compiled in "debug" mode so it prints out some app and system related strings to help debug the connection between the app and the BOINC wrapper.
The BOINC wrapper is not GPUGrid's "product".

Still a security issue IMHO

I don't agree with you.

Correct. You have a problem with the BOINC Wrapper app and you should vent your paranoia at the BOINC developers which wrote the application.

Target would be David Anderson.
davea@berkeley.edu and you should post this issue to the BOINC developer website
https://github.com/BOINC/boinc

Anyway, collaborating with BOINC projects is an altruist and voluntary action.
If somebody feels unsafe or uncomfortable at GPUGrid, there is always the chance to look for alternatives at other (better?) projects.

it's not the GPUGrid app, but the BOINC wrapper does it because it was compiled in "debug" mode so it prints out some app and system related strings to help debug the connection between the app and the BOINC wrapper.
The BOINC wrapper is not GPUGrid's "product".

It is shown on your website as result log of your application. It is not shown on anyone else's project debug logs.
I'm participating on other projects, and only GPUGRID shows such info.
You're wrong.

You're wrong.

Just because this project uses a different feature to your other projects does not make him wrong.

So perhaps you'd like to get off your high horse and complain to the correct department?

it's not the GPUGrid app, but the BOINC wrapper does it because it was compiled in "debug" mode so it prints out some app and system related strings to help debug the connection between the app and the BOINC wrapper.
The BOINC wrapper is not GPUGrid's "product".

It is shown on your website as result log of your application. It is not shown on anyone else's project debug logs.
I'm participating on other projects, and only GPUGRID shows such info.
You're wrong.

as has been said, it's the BOINC wrapper.

your computers are hidden anyway. no one can see what you're talking about outside of your screenshot that you posted yourself, so any perceived security concern is kind of moot anyway.
you need to address your concerns on the BOINC forum: Questions and Problems

---