selsta
selsta
Quite hard is an understatement. See https://en.wikipedia.org/wiki/Trusted_execution_environment, which is required for L1 (HD) content. One security researcher managed to crack L3, but that’s not released publicly. https://www.zdnet.com/article/security-researcher-cracks-googles-widevine-drm-l3-only/
@3o33emalle you either have to be in the same directory as the hlsdl binary or you have to install it in a directory that is inside your PATH. What exactly...
What you posted only compiles the program, but it does not install it. If you do `make install` after `make` it will install it into `/usr/local/bin`.
As far as I know https://github.com/monero-project/monero/pull/8113 fixes Wagner/Drijvers attack. @UkoeHB could you confirm?
But there is no "public node list". Currently the daemon is used for a p2p node scanner, but I want to remove that because it removes the dependency on the...
There are two things to consider: - Passive spy nodes (setup by blockchain analysis companies) - Actively malicious nodes I would like to avoid both. Yes, it's possible for trusted...
An application should never result in a hard system lockup. That's definitely a driver bug. Is this still an issue with AMD?
30d before hardfork is when we want to release binaries, ideally 60 days before a freeze.
I would like to add https://github.com/monero-project/monero/pull/7760 to the list, it fixes a lot of the daemon issues and is well tested, bit it isn't fully reviewed yet.