Cool.Stiwi hat geschrieben: ↑24.11.2020 22:39FAH gibts nun auch auf 64Bit ARM:
https://foldingathome.org/2020/11/24/ne ... m-support/
Lange nichts mehr von Dir gehört.

Michael.
Cool.Stiwi hat geschrieben: ↑24.11.2020 22:39FAH gibts nun auch auf 64Bit ARM:
https://foldingathome.org/2020/11/24/ne ... m-support/
Link in das FAH Forum, Meldung vom 23.10., mit dem changelog der letzten Versionen :Hello Folders! We’ve been made aware of a potential issue for users who are using certain advanced manual configuration options for remote client management using fah-control. We actively recommend against this sort of remote management, so the issue affects less than 1% of our user base, and only under very specific conditions. Even so, in the interest of being transparent and not alarming our users, we are making this blog post to prevent confusion.
The issue is limited to the small subset of users that manually configured the client and their network to allow remote client management, and are using fah-control to connect over an untrusted network to a remotely accessible client port.
In those specific circumstances, if an attacker on the untrusted network could perform a PITM (person-in-the-middle) attack and actively manipulate network traffic, they would be able to remotely execute code in the context of the user running the fah-control GUI. The actual Folding@home client on the remote machine would not be affected, but the system running the fah-control GUI itself could be affected.
If you currently perform the manual steps described and may be affected, we recommend you update to client version v7.6.20 or later. These versions have the fix applied and are no longer affected.
It is also important to point out that manually configuring fah-control to manage remote clients is not recommended when used over an untrusted network. If you need to do this remotely over the public internet, we recommend using a VPN or similar method of extending a trusted network between two locations.
(...)