Would be nice to enable network sharing of the external drive too. I tried to figure it out myself with brcly's suggestion but had no luck
non the less this is still great !! Thank you sir.
This is awesome @Victor_Sabba
Thank you, for looking into it !!! 🧡
Hopefully we can just write a script to automate these changes without having to manually edit these files or any future ways this feature is blocked again. 🧵
https://t.co/e9Vwe5UJTW
Thank you @rot13maxi and @RomanCCLVI for your feedback.
I have implemented a new Vault use case where a withdrawal can be cancelled during a “Challenge Period”.
A huge feature for keeping your bag safe.
And a Home Screen button to see the progress of #ActivateOP_CAT
⚠️⚠️⚠️⚠️⚠️
Fractal Bitcoin security issues.
Be careful if you are running a @fractal_bitcoin node using the official docker release, the RPC credentials are hardcoded, not configurable via environment variables, and RPC server is exposed publicly and vulnerable to attacks.
So many bad security practices in this bitcoin conf file..
rpcallowip=0.0.0.0/0: This is the most concerning setting. It allows RPC connections from any IP address, which is very dangerous if exposed to the internet. It effectively opens your node to potential attacks from anywhere.
zmqpubhashblock=tcp://0.0.0.0:8330 and zmqpubrawtx=tcp://0.0.0.0:8331 These settings allow ZeroMQ connections from any IP, which could be a security risk if exposed.
maxconnections=0 This removes the limit on the number of connections, which could potentially lead to resource exhaustion.
To be honest I even thought that I was looking at a scam Github repo from a wrong organisation.
So I checked your website, and again this is bad because it's not trivial to find your Github organisation. It opens the door to a lot of potential scams. After navigating I finally found the Github org, and it happened that I was (unfortunately) looking at the right repository. The Github org does not even have a link to your website, or at least your logo...
You are exposing node runners to dangerous attacks.
This is not serious.
Today we disclose Dark Skippy - a powerful new method for a malicious signing device to leak secret keys.
With a modified signing function, a device can efficiently and covertly exfiltrate a master secret seed by embedding it within transaction signatures.
@arablebtc@lopp coincidence?
word on the street is they aren't selling, they are just moving it to a custodian for safe keeping. I don't know what is true.
A new milestone has been reached in our STARK over Bitcoin cooking 🧑🍳
The Stwo Verifier is now live on OP_CAT-enabled Bitcoin Signet 🤯
https://t.co/JqTLsDzzVT
A small step for Bitcoin and a giant leap for STARK-kind! Tremendous collaboration with @weikengchen and @l2iterative.
Note: OP_CAT is not available yet on Bitcoin (BIP-347)
PS: yes we know about our meme 🤓