A keylogger records when a key is pressed, when it is released, and whether any shift or special keys have been pressed. It is also recorded if, for example, a password is entered even if it is not displayed on the screen. There is no evidence that this keylogger has been intentionally implemented. Obviously, it is a negligence of the developers - which makes the software no less harmful. If the developer would just disable all logging, using debug-logs only in the development environment, there wouldn’t be problems with the confidentiality of the data of any user.

I quickly pressed Windows Key + q to open the Search box and typed in: turn windows features on or off Turn windows features on or off I scanned a few options but one in particular was salient: Hyper-V was enabled. So I installed the 64-bit version of Docker for Windows after configuring a shiny new VirtualBox CentOS 7 guest. The latter’d ran just fine previously, but was now causing a BSOD, and I wasn’t even able to create new 64-bit guests.

Fixing this issue is pretty straightforward and involves a few simple steps. Load up task manager (right click taskbar and select Task Manager) Go to the Processes Tab Select rdpclip.exe Click End Process Go to the Application Tab Click New Process Type rdpclip Click Ok References https://techtalk.gfi.com/copy-paste-working-remote-desktop-connection-whats-wrong/

Today, I was trying out the new release, and then I ran into a wall: logging in to mysql didn’t work, even though I was sure that I’d configured it correctly; i.e. root with an empty password. I’d done this hundreds of times already, so I was sure it’d work, but then again, it just didn’t. So I tried to reset the root password by killing mysql and then starting mysql_safe with a new password.

Spent too much time configuring port forwarding (RDP) on my (Microtik) RouterBoard 751G-2HnD. The solution, as usual, was buried in a May 2014 forum post. There needs to be TWO (2) NAT rules enabled; i.e. to forward traffic to/fro the router/server. In this case, 192.0.78.13 and 10.0.0.254 refers to the router’s WAN and LAN IPs respectively, and 10.0.0.243 is the intended recipient of my RDP traffic. [admin@751g2hnd] > /ip firewall nat print 1 chain=dstnat action=dst-nat to-addresses=10.

Yesterday I updated the date column of an entire table meant for its subset only. The solution to this mistake was to recover from daily mysqldump, and filling in the gaps that were, thankfully, able to be filled in. Writing in 2010, the author of the answer said: When something goes wrong, the only restoration option available is to reconstruct the data from a backup (providing one exists). Here are two answers that I found useful; i.