Password checking implementation: delay on unsuccessful attempts [duplicate]

This question already has an answer here:

  • Should I implement incorrect password delay in a website or a webservice? 4 answers

What would be wrong with the username/password checker where the response is instantaneous for valid attempts but a pre-built time delay (say 1 sec) is used for unsuccessful ones? It would not slow down legitimate users, but would obviate the need for key derivation functions, and thwart the timing attacks. Can someone critique please?

Can you delay action while unconscious?

Suppose my character in PF1 is unconscious and dying, and the party cleric’s turn is not until after mine in the initiative round. I would like to avoid wasting a turn by delaying until after the cleric’s turn. This way, the cleric can heal my character and he can get back up immediately if he heals above 0 HP. My understanding of the rules for dying is that I would still need to make my check to stabilize, but that is not what I am trying to avoid here, I’m only asking about whether I can delay at all.

Is it possible to save my action economy this way? I know that you can’t take any actions while you’re unconscious, but is delaying your turn considered an action or not? The entry seems to imply that it is not.

By choosing to delay, you take no action and then act normally on whatever initiative count you decide to act.

Is there a more definitive ruling on this anywhere?

Permissions revoke delay

I have a strange issue with permissions. We have a web application with custom claims provider (I do not know if this is connected with the issue). We have some site collections with many documents (all documents have broken permissions… I know it is not ok but it has to be that way). The issue is that when I assign a user to a group (this group exists ‘inside’ our custom claims provider) the user receives permissions immediately – he can open the document. But if I revoke permissions – user still can open the document for around 4 or 5 minutes. After that time the permissions are ‘truly’ revoked. What the…?

Why is there a delay when typing certain characters with xdotool in 18.04?

Using xdotool type or xdotool key to type certain characters makes Gnome Shell lock up while the text is being typed. For example typing a single slash with xdotool type / or xdotool key slash takes a second or two, but for 23 slashes it’s more than 20 seconds.

Of all the printable ASCII characters, only these cause the problem:

  • slash /
  • backslash \
  • bracketleft [
  • bracketright ]
  • braceleft {
  • braceright }

Why does this happen and how can I fix it?

More details

I never had this problem in Unity on 14.04.

There is a small delay when typing other characters – maybe a second, even for long strings.

Any timing I’ve done in the terminal has come back normal, like time xdotool type ... or t=$ SECONDS; xdotool ...; echo $ ((SECONDS-t)), so it seems to be a problem on Gnome Shell’s side.

I’ve confirmed $ XDG_SESSION_TYPE is x11.

For a UK rail delay, which train company do you claim compensation from?

For those who don’t know, the UK rail network was largely privatised in the 1990s. Whether or not rail privatisation is a good thing is still very much up for debate, but even most pro-privatisation people feel the way it was done wasn’t the right way! One upshot is that most non-trivial journeys will involve travel on trains operated by more than one train company.

Let’s consider a hypothetical journey, A to D with a change of trains at C. The A-C journey is to be operated by TrainCoA, C-D by TrainCoB. Unfortunately, the A-C train is cancelled, so you end up getting a later train A-B, another B-C, and then a later train than you’d planned C-D. Oh, and then the C-D train you eventually caught was very late too. Everything was bought on a single ticket.

In this situation, which train company do claim compensation from? TrainCoA, as their initial cancellation was your first delay? TrainCoB, as their C-D delay was the largest delay on your journey? TrainCoC, who ran the A-B journey that you got instead, as they were the first company who’s trains you managed to take? Or can you take advantage of the privatised nature of the system, review the compensation policies of all three train operating companies, and apply for compensation from whichever company has the most generous compensation for your sequence of delays? (Many of the companies have different minimum delays before compensation is due, and different exclusions on what their delay compensation covers….)

Bit times and propagation delay

Nodes A and B are accessing a shared medium using CSMA/CD, with propagation delay of 245 bit times between them (i.e., propagation delay equals to the amount of time to transmit 245 bits). Minimum frame size is 64 bytes. Suppose node 𝐵 begins transmitting a frame at 𝑡 = 0 bit time. Before A finishes, node B begins transmitting a frame. Assume no other nodes are active.

What is the latest time by which B can begin its transmission?

Attempt: Considering that t=512 bit times is the time at which A finishes transmission, shouldn’t the latest time by which B begins its transmission be at t=245 bit time? (At t=1, 1st bit is pushed on the link, and at t=245 bit time, this is the last “timing” that B can start transmitting before it senses that A is transmitting). However, the answer given is 244 bit time and I do not understand why.

Cannot enable User Input Delay performance counter on Windows Server 2016

As per; https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdsh-performance-counters

One should be able to enable the User Input Delay performance counters.

I have added to the registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]  "LagCounterInterval"=dword:00005000 

Rebooted the system, but such counter is not available.

On Windows 10 this works. But I can’t get it to work on Windows Server 2016. As the article hints it’s enable per default on Server 2019, one can conclude that Server 2016 is also supported.

Does anybody know more about this?