Ded7xSEoPKYNsDd

> You can't re-arrange sub-windows with the mouse (drag).

Just a nit-pick:

You can configure that with tmux (and possibly screen, I don't know). It has the downside that the user needs to know to press shift while clicking when they want to route mouse actions to the terminal emulator (e.g. to select text) instead of tmux or the applications running inside of it.

No, there is no such paragraph. The German constitution guarantees freedom of opinion - not speech.

So you can’t get prosecuted for disliking someone (and saying so) but you can for saying insulting or untrue (e.g. holocaust denial) things - those are not opinions.

Here in Germany early college math classes were mostly a rehash of everything from school, but with much more rigor and sometimes more detail.

So I'd recommend some college textbooks. If you live near a college, their library should have a ton of them to browse through and lend. You should also be able to find accompanying lectures on YouTube or college web sites.

This bug is a year old, and Firefox Preview / Fenix has in the meantime gained support for uBlock. Considering that's mentioned as motivation for native support, I'm not sure this is still planned?

The standard python linters can do it:

    $ flake8 foo.py
    foo.py:6:14: F821 undefined name 'q'

    $ mypy --check-untyped-defs foo.py
    foo.py:6: error: Name 'q' is not defined

(They also have some other complaints about your code that you'd either have to disable or adjust to.)

openssl can also do it. no dirlisting though.

    openssl req -x509 -newkey rsa:4096 -keyout /tmp/key.pem -out /tmp/cert.pem -nodes && openssl s_server -WWW -port 8443 -cert /tmp/cert.pem -key /tmp/key.pem

As someone who regularly needs to report security vulnerabilities to projects hosted on Github, I find it incredibly annoying that I can't create one of these 'maintainer advisories' (or just a regular issue that's non-public) as an outsider.

These 'security.md' files would work for me just as well to define a security contact, but I've never come across one of these in the wild... so I end up wasting my time hunting down maintainers and their email addresses, when everyone involved would have a much easier time if it were all handled through Github by allowing everyone to create a (draft) 'maintainer advisory'.

No 'background checks' by private investigators in Germany. Some employers ask for a police certificate of conduct. There's a law saying which kind of convictions are listed there (nothing below a certain amount of days) and how long (to allow re-socialization).

I've seen a lot of criticism of this approach - hiding vulnerabilities, instead of actually fixing them. Other mitigations actually prevent exploits (e.g. the combination of NX and ASLR raises the bar for getting code execution: suddenly interactivity and an address leak are required in addition to a stack-based overflow) whereas your mitigation (?) just sweeps bugs under the rug.

From my own skimming of the paper, the discussion of 'why?' boils down roughly to 'exploits are sometimes used for bad things'.

Do you believe your approach will actually improve the security of any systems, or will it just allow lazy vendors to hide their shallow bugs - leaving them to the most motivated (e.g. nation-state) adversaries?

My understanding is that in your 2nd scenario (contractor), the tax/social security authorities might at some point decide that this is Scheinselbständigkeit, and therefore it's actually been scenario 1 all along. What I'm unclear about is whether they'll try to collect from the worker in DE or the company in the US.

Airlines made a business of that, too: with 'priority boarding' you get into the plane first, when the overhead compartments still have enough space. And some airlines (Ryanair) only allow so small bags in the cabin with a standard ticket that the overhead compartments don't get full nearly as often.

They aren't really comparable. While IDA has some debugging features, it's all about static analysis. It has features for browsing and annotating code - you can view the code as a control flow graph, add your own names and comments to functions and variables once you've made sense of them, define structures and their members so you don't have to memorize what each offset to a common type means, jump around in the call graph, find other usages of global variables...

Tea! It's literally water with taste.

If you don't like hot beverages, make it iced. If you don't want to make some all the time, use a bigger kettle.