I would check the term.log/history.log files in the /var/log/apt folder to see if there's another process installing those updates.

I mean it was not too long ago there was a bug which could lead to an unauthenticated RCE against Bluetooth on Android.

https://nvd.nist.gov/vuln/detail/CVE-2022-20345

So yea, reducing surface area of attack when a feature is not needed is kinda important.

Found some documentation listing the two middle switches as the rounding switch (up fraction down) and the decimal switch (auto? 0 to 6 then hex?). No idea on the other two.

http://www.calcuseum.com/SCRAPBOOK/BONUS/32853/1.htm

Decimal switch: [A-0-2-3-4-6-F], Round switch: [(ArrowUp)-5/4-(ArrowDown)], Miscellaneous switch: [(Blank)-K .-(Sigma)],

The creator's clear check doesn't count towards the level being cleared, so these levels are uncleared. I think if the creator plays it on the uploader account it wouldn't count either.

The -k argument on my openssl accepts a passphrase, not a file. You likely encrypted with the filename as the secret, not it's contents. Perhaps you should use -kfile instead.

$ openssl aes-256-cbc -help
Usage: aes-256-cbc [options]

General options:
 -help               Display this summary
 -list               List ciphers
 -ciphers            Alias for -list
 -e                  Encrypt
 -d                  Decrypt
 -p                  Print the iv/key
 -P                  Print the iv/key and exit
 -engine val         Use engine, possibly a hardware device

Input options:
 -in infile          Input file
** -k val              Passphrase**
 -kfile infile       Read passphrase from file

Only if you define it.

const that = this

Oh yea, I knew I forgot to cancel something after switching my gaming pc to Linux.

The amount of Windows bashing in this thread is hilarious, for what amounts to Enterprise grade DNS-over-TLS with additional whitelisting. Doesn't help the home user, but likely won't break home users internet access either.

IMO as a developer this is a sane change. There's no telling when the format of the first-party api key will change. They may switch from reference tokens to JWT tokens tomorrow. The validation should be using the token and seeing if it works.

You can, sure, but you probably shouldn't. Encrypting and decrypting consume additional cpu time, and you won't gain much in terms of security.

Best news I've heard all day.

Most distros use a generic kernel that contains drivers neeeded for basic operation. These kernels are larger than ones specially made for your hardware. Some specialized drivers like graphics may not be included but will run in a more simplified graphics mode that works for all cards.

It's a product of the format being parsed twice. Each line should be 80 characters with an = at the end, then a carriage return+newline(lf) to continue the line. Somewhere the cr+lf got converted to just an lf and then when reparsed it removed the lf plus the next character, making it still conain the equals but not the next letter of the message.

Here's a better technical explanation if you care: https://youtu.be/SVVnkNZWJhk

If only they had done this with .local ages ago. Still, it's a nice change, but I doubt my company will adopt.

There are 4 pinned posts at the top, should be more posts below that.

NoSQL is best used as a key-value storage, where the value can be non-tabular or mixed data. As an example, imaging you have a session cookie value identifying a user. That user might have many different groups, roles, claims, etc. If you wanted to store that data in a RDBMS you would likely need a table for every 1-to-many data point (Session -> SessionRole, Session -> SessionGroup, etc). In NoSQL this would be represented as a single key with a json object that could looks quite different from other Session json objects. If you then need to delete that session it's a single key delete, where in the RDBMS you would have to make sure that delete chained to the downstream tables.

This type of key-value lookups are often very fast and used as a caching layer for complex data calculations as well.

The big downside to this is indexing and querying the data not by the primary key. It would be hard to find all users in a specific group as you would need to scan each key-value. It looks like NoSQL has some indexing capabilities now but when I first used it it did not.

Clearly the Linux user just broke their prompt by updating. Classic.

Perhaps they should ask Copilot how their templating system works.

In the US they are usually governed as real estate legally. You can resell it, but most people aren't interested in paying the maintenance fees. You'll find all sorts of timeshares out there being resold for 1$ because they just don't want to pay the maintenance fee anymore.

I think NetworkChuck has a good set of tutorial videos about self hosting. For the most part you can search for what you want to find info on and he probably had a video on it. E.g. Nginx: https://m.youtube.com/@NetworkChuck/search?query=Nginx