Still, I feel like distro packages are really secured compared to stuff you install via pip/npm/... as I don't believe they do anything beyond protecting downloads with TLS.
294 karma · joined December 7, 2020
[Verifying my OpenPGP key: openpgp4fpr:BBDE032EAAFBFC627FB7E635B1F4055D8460CE34]
Still, I feel like distro packages are really secured compared to stuff you install via pip/npm/... as I don't believe they do anything beyond protecting downloads with TLS.
> MNAO analyzed some of the code and determined that the code provides functionality same as what is currently in Apple App Store and Google Play App Store.
Is this really legal? Because in my mind, providing the same functionality does not violate copyright, since the actual intellectual material is new. And I don't think Mazda has a patent on the ability to control your vehicle over an API.
Given the popularity of the library I'd imagine it's quite well tested. I also fail to understand why he attempts to port libshine from C to Go when he could just port the header files from LAME as FFI bindings instead. That should also ensure comparability with windows, as I'm sure such a library us also buildable on windows, given that ffmpeg uses it and ffmpeg works on windows.
Running nginx might be marginally faster than PHP, but I believe the latency to your server will be far greater than the time it takes the server "to spin up the php interpreter" (doesn't even happen anymore when using FastCGI).
And I also could imagine that tools that allow setting arbitrary env vars might filter common troublemakers like PATH, but almost certainly not niche env vars that change the bahviour of ld-linux.
I'm always impressed on how simple it is to use an object I defined in c within python.
It wasn't nearly as fast the advertised speeds mentioned in the article.
Because that actually looked like a decently private central-ish digital currency.
[0]: https://www.freedesktop.org/software/appstream/docs/chap-Met...
That is one of the things that rustc is severely lacking.
I have never seen any 18-year-old type like this. Is this actually common in the US or just a thing of older folk imaging how an 18 -year-old might type?
a bit further down he actually proclaims being born 11/11/2004, making him just 17. No idea why he has 18 y/o in his user description, not that it'd make a difference tho.
But on Linux we also don't have to fight with a 15 year old bash or "compromising" a system when installing something into /bin. It feels lile OS X genuinely doesn't sound like a good UNIX to administer.
Electron applications are a prime example of this, since there is a whole webbrowser underneath and HTML doing HTML things is expected behavior for the browser, but not the application above. One can probably attribute the whole log4j debacle to the same fault, in that the "common" developer is unable to understand all complexity and quirks their software ships with (difference being, that a browser engine is far more complex than a logger)
I remember a time where "Scrach" wasn't a Electron application, but a native (I think?) Linux application. Obv. there can be bugs in dependencies too (rsvg, libpng, etc.) but they different and tend to not be as easily exploitable as these kind of Electron/HTML->V8 bugs are.
The only other potential cryptographically secure alternative might be a TPM chip, if a machine has this. However since a TPM stores secrets system wide, keyrings for each user seam unfeasible and it's likely less secure since you could just boot into single user mode and get the TPM secrets.
Additionally I tend to not trust the TPM (esp. on Linux), because if one firmware update somehow fails to apply properly, I'll have a far more nastier time (since all secrets are gone) than GNOME Shell promoting me to insert my old password.
Language bindings for any GObject powered are usually automatically generated from their introspection data (.gir) generated from g-ir-scanner.
So that wouldn't be the issue.
why exactly? a GtkBox is would do just fine, looks better and it's easier to handle programmatically than the grid.
[0]: https://f-droid.org/packages/de.seemoo.at_tracking_detection
> China has no freedom of speech
whoever wrote that into "illegalwords.zh-CN.en.txt" must have been aware of the irony...
no, the things I listed are how I sync my linux machines with my mobile phone.
I wasn't talking about computer to computer sync, but the methods I listed (maybe except kdeconnect, which is built for computer to phone sync) apply to workstation to laptop sync aswell.
you can,
- kdeconnect can do clipboard & messages sync
- nextcloud (or anything else that does webdav & webcard) does calendar & contact sync
- Firefox (and chrome probably too) can sync browser history and share webpages feom one device to another
i'm not aware of anything that can remotely unlock another device, but that seems like a security risk to me (also quite hard to implement as pam is synchronous :/).
but you certainly don't need a closed ecosystem, building your own out of free components is very much possible.
For the demo it's unfeasible to use a preexisting currency, because they can't give out free money :-). So the obv. solution was taken to configure their server for a imaginary currency (KUDOS & TESTKUDOS) 100 if which are created out of thin air after you register.
To get started, I'd recommend downloading the wallet (extension or mobile[0]) and registering an account with their demo bank. With the creation of that account, you should receive 100KUDOS tokens of which you can withdraw to your mobile phone / extension. Do so and you'll get a QR code to scan with the amount of KUDOS selected on the web interface. With that "money" you can now go to their demo shop and "buy" excerpts from rms's Free Software, Free Society, or "donate" to a few projects (try donating 5 kudos to simulate a malicious merchant), by again, scanning a QR-Code.
If you want to know the details, I'd recommend the paper "How to issue a central bank digital currency[1]" which is very much like Taler.
[0]: https://f-droid.org/packages/net.taler.wallet.fdroid
[1]: https://www.snb.ch/en/mmr/papers/id/working_paper_2021_03