TF Protection against cyber threats #225
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue as described here:
https://github.com/threefoldtech/tf_security_reports/issues/3
Solution being worked on here:
https://docs.google.com/document/d/1iZCUQK3ZiGwH0H-Ua6xR7ozyQ9TNE2iLfU4Nx0k6mgM/edit#heading=h.442ls16eaduo
Will communicate something asap and create something clearer early next week.
Passing this around for feedback:
As pioneers in helping to create a decentralized cloud and Internet, our commitment to ensuring the safety and integrity of our network is paramount.
In response to reports from some farmers about potentially suspicious traffic originating from workloads on their ThreeFold nodes, we are actively working to implement additional measures to keep farmers and users safe. To be clear, we have found no evidence of a security breach of any ThreeFold systems, including Zero OS.
Our goal is build the most secure and capable decentralized cloud on the planet. Keeping all participants safe is an essential part of that goal, and so we are and will be taking steps to enhance our ability to prevent and address any misuse of the network.
Authenticity and the ability to respond to events constructively are crucially important to our team – and we'll share more details soon. Thanks for your support in growing and developing the ThreeFold network and for your understanding and cooperation as we undertake these steps. Together, we will continue to build a resilient, secure, and decentralized future.
Has been well-received but there was an exception with one line, so need Scott to re-write.
And the plan still needs to be worked on / agreed upon ...
Waiting on a meeting between Thabet and Jan for more information.
Communicated on the community call yesterday evening.
This is to be discussed amongst the development stakeholders next week.
@scott @mik-tf please push for some resolution to this discussion and update the team so it can be communicated. 🙏
Update
@mik-tf Got it. How long before it is fixed? Any idea?
@scott @mik-tf Do you feel we need to go into this topic at a deeper level than was described in the 3.15 update?
I think we can write a forum post once the 3.15 is released. To explain what was done. I.e. I wouldn't focus too much on communicating the security issues before they are fixed.
Let's please update this issue – title and description and current state of things. 🙏
@gosam this issur has the latest info:
#291
Closing this issue and removing from the sprint as issue 291 has been referenced to be updated with the latest.