#Electrum is a popular #Bitcoin wallet, one of the recommended by bitcoin.org. An elementary and serious #security issue had been at first not treated seriously on IRC, then ignored for over a month on GitHub (currently over 200 watchers). Apparently Linus’s law is not always working.
“Pale Moon already set the granularity for the performance timers sufficiently course in Oct 2016 when it became clear that this could be used to perform hardware-timing based attacks and fingerprinting.
There will be more bugs like this.
Security professionals know this and have known for a long time. Thus my claim it was a standard best practice, albeit one that has costs not everyone could justify.
That math has shifted now, more people will justify the expense. Not all, but more.
Theo on the Intel Core 2 bugs ~10 years ago. #OpenBSD https://marc.info/?l=openbsd-misc&m=118296441702631&w=2
22:15 <@MoonchildPM|Away> KrzysiekJ: You may have to write an addendum to the article. They finally got back to me (potentially after having my post show up for them) and there is an extremely bad and fragile workaround possible to make SHA256 signing with their crypto hardware possible that I found out (no thanks to their terrible support and not something discoverable even for tech-minded devs).
Code signing of #Pale_Moon binaries on #Windows will come to an end because signing certificates are practically unavailable to individual developers. The only viable option (Certum, #Poland) uses #SHA1. Sadly, ignoring the fact that SHA1 has been broken seems to be common in Poland. The market of #SSL certificates seems to be highly regulated, yet still the regulation has not prevented this situation occuring.
Federated GitLab? Yes, please…
I run my own GitLab. You run your own GitLab. Your GitLab sends my GitLab a pull request.
How cool would that be?
If you’d like to see that, take a moment to upvote issue #4013: https://gitlab.com/gitlab-org/gitlab-ce/issues/4013
This is exactly why I try not to get involved in #FreeBSD's matters anymore: https://lists.freebsd.org/pipermail/freebsd-security/2017-December/009558.html
Dziś na Weekendzie Kapitalizmu przedstawiłem dwie krótkie prezentacje:
• o #proof_of_stake, czyli czym zastąpić pracę w kryptowalutach, oszczedząjąc energię i tym samym pieniądze;
• o zdecentralizowanych sieciach społecznościowych (wspomniałem oczywiście o Mastodonie).
Wystąpienie można obejrzeć pod adresem https://youtu.be/YRsSVayRmbs?t=1h19m55s (polecam też inne wystąpienia, m.in. drugie, o ochronie środowiska).
Coca-Cola jakiś czas temu postanowiła najwyraźniej ograniczyć sprzedaż #Sprite’a, bo zmniejszyła zawartość cukru (do 2g na 100 ml) i zaczęła dodawać #słodziki (#acesulfam K, #aspartam, #neohesperydyna DC).
W #7up i Trzech Cytrynach tymczasem wciąż węglowodany (odpowiednio 11,2 i 9,7 g na 100 ml).
#XDG Base Directory Specification defines $XDG_DATA_HOME, $XDG_CONFIG_HOME and $XDG_CACHE_HOME to store user-specific: data, config and cache, respectively. The sad reality is however that many #software packages abuse $XDG_CONFIG_HOME and store data and/or #cache inside that directory. Among them are:
That’s unfortunate especially for cache, as it introduces potential to flood #backups.
@KrzysiekJ I've been bugged by this for as long as I can remember. Standards are agreed upon, then discarded for the sake of convenience. Major browser being less strict is considered a "competitive advantage", as from the nontechnical user's viewpoint, they are the ones that "work" with those sites unlike others.
But there seems to be no adequate way to fight this behavior. Standards can't really be enforced by anyone other than browser creators.
Let’s say that I create a #Mastodon account on my own, private instance (only hypothetically, as I like my current one) and immediately post an introduction. Then:
• Nobody will see the introduction (as initially I will have no followers).
• If I use the search feature, I will see only posts from my own timeline.
How does the #federation model respond to these problems?
I read the warren v. district columbia decision a few days ago and I can't stop thinking about it
If we want to achieve compatibility between #web #browsers, it is important to implement #standards strictly, without non-standard error recovery. For example, someone mistyped backslashes into stylesheet URL on kobo.com. #Chrome and #Firefox convert backslashes into slashes, while #Pale_Moon displays website without any styles (correctly, I presume).
Wg gs.statcounter.com udział Facebooka w ruchu sieciowym generowanym przez sieci społecznościowe spadł w ciągu ostatniego roku o 8% (7 p.p.) na świecie, podczas gdy aż o 20% (16 p.p.) w Polsce. Efekt cenzorskiej polityki portalu?
(Statystyki zapewne nie uwzględniają niektórych portali społecznościowych, ale jednak mogą pokazywać pewien trend).