The concern with Esc is that if you hit more than 3 times the user will be stuck on the page. The first 3 presses would trigger the redirect, the 4th press would be intercepted by the browser and stop the page load.
> Ctrl+W or middle click on tab isn't that far off
The point of shift x3 is that it's consistent across keyboard layouts including laptops. I have a laptop where the location of the ctrl key is moved inward to make room for the function key. I frequently hit Fn instead of Ctrl and don't realize what's happening until I look at my keyboard. And that's not when I'm in distress.
Same goes for middle click. It's not a consistent interaction. On some laptops you can left click and right click to get a middle click. On my laptop, it's a three finger tap.
> Never mind that computers and internet access is ubiquitous enough these days that "using the family computer" for this sort of thing isn't really needed in the first place.
In a normal situation, this is true, but this is UI design for people in extraordinary situations. Their abuser may have taken their cellphone or other devices and may not have a choice in what computer they use or when they have access to it.
Nothing about this prevents private windows or Ctrl+W (assuming they have another window open so it doesn't look suspicious that they're staring at a blank desktop), it just gives victims a quick action they can take to prevent immediate retaliation.
> I frequently hit Fn instead of Ctrl and don't realize what's happening until I look at my keyboard. And that's not when I'm in distress. Same goes for middle click. It's not a consistent interaction.
Triple Shift that you can only on a single website is worse since you're even less likely to be able to use it in distress
Besides, as a site you can try to add typo-similar combinations for your "hide" action (like alt+w or win+w) instead of creating a totally different one
I think how Steam handles game rankings is a good example of this. They separate out "All Reviews" from "Recent Reviews". Helps identify current reception of a game which may have had a buggy release.
Apparently, Verizon's outage page doesn't actually say if there's an outage. You have to log in to see if there's an outage. Too bad logins are failing after ~10 minutes for me.
The two halves of the mold are put back together and the concrete is poured into the bottom. Once it's set, the mold is removed and the result is once piece.
Here's a good video from Tested on the process (not with concrete) https://www.youtube.com/watch?v=DEVi0mEaJJQ
According to the first article, the code was hosted with a custom version of Gitlab, with the register link still functioning. Once an account was created all the repos were public. If that's true, then it's a public site being accessed through features of the site.
I'm sure it also depends on if the site was intended to be accessed "publicly" or not. Let's say, visually, all registration links were removed, but (as someone with internal knowledge of GitLab here did) could "breach" into the registration page.
It works independently of transmission method since the mouse clicks are simply translated into "keyboard presses", i.e. encoded to stdin as escape sequences. It's a single stream.
Of course, the terminal emulator must play nice with the windowing environment and translate mouse events correctly.
It works through PuTTY, and moreover it's the default config in Debian 9, which I find sort of annoying because I'm used to using the mouse in PuTTY for copy/paste. But it does work smoothly (including through a screen session and through ssh to other machines).
Most of the time, that will give you a detailed description of what's going wrong and tell you the command to fix it. Completely changed my opinion on selinux when I learned it. Also, the SELinux For Mere Mortals[1] talk is a great introduction.
It's nice... but the suggestions are often terrible when they could be fixed properly with a bool or changing the context of a directory.
I sat the RHCE course/exam recently and the Red Hat trainer dealt with this in... amusing... ways.
Unfortunately, fixing things properly requires knowledge, if only of where to find the information. Thinking solely about file contexts, it's not easy to for example search them. e.g. "show me all contexts related to samba" so you can find the share rw label. (One of the RHEL 7.0 man pages suggests the nfs rw label which doesn't work, had to make a point of remembering that for the exam!) Everything's spread across selinux's man pages, service's man pages... ugh.
I personally feel like the included man pages on RH distros for selinux discussion on specific topics are quite good. You can see the full list of these by searching your man database with: man -k _selinux
In this specific case, you're looking for samba_selinux. It's not perfectly written, but it should at least cover all the relevant information: (https://linux.die.net/man/8/samba_selinux). You mentioned looking for the read/write share label, and that's specifically discussed, and described with examples.
You can also use sesearch to query your selinux policy for more information about anything mentioned in that man page. For example, to understand the implications of setting samba_enable_home_dirs you can run `sesearch -A -b samba_enable_home_dirs`. You can run similar queries for file types, process types, port types, etc. If you really want a list of every type relevant to samba, you can run: `sesearch -A -s smbd_t`. If you wanted to use sesearch to find everything smbd_t can write to, as an alternate method of discovering public_content_rw_t, you can filter that, like: `sesearch -A -s smbd_t -p write -d -c file -C`. This will also show you that the public_content_rw_t rule is conditional on the smbd_anon_write boolean.
I used to teach RHCE courses and exams; I'm curious about the amusing ways of dealing with selinux you encountered.
That "show me all contexts related to samba" is something I'm really missing. I worked one weekend on getting NextCloud to play nicely with SELinux and Apache on Fedora 25 without any dirty tricks, and one thing that would really have come in handy was an accurate list of all the labels related to Apache. The only comprehensive lists I could find online were out-of-date, and the only things that were up to date were single examples.