Jul 19

Compiling and installing MariaDB on Raspberry PI

For reports on my timeseries data I really needed Windowing functions like LAG(), LEAD(), ROW_NUMBER() etc. The speed and flexibility you gain using Windowing functions is incredible compared to imitating LAG() using “self-join” tricks. But these function are supported as of MySQL 8 and as of MariaDB 10.2.

For numerous of reasons I prefer to use MariaDB which is compatible drop-in replacement for MySQL.

Unfortunately there are no ready to install packages for ARM so you need to compile and install newer versions by hand.

I’ve came across many articles regarding compilation of MariaDB but these did not match my installation and were missing some important steps. So decided to share my solutions.

So let’s start!

Continue reading

Jul 15

Could not locate bootia32.efi while trying to install Windows 10

Recently a Prestigio smartbook had to be reinstalled with latest Windows 10 1803. This laptop came with 32 bit Windows but had 64bit CPU. So I [wrongly] assumed 64-bit Windows would work. That was not the case!

I’d made 64-bit Windows 10 installation USB stick using Rufus (MBR:UEFI). But when booting I’ve received an error:

[FAIL] Could not locate '/efi/boot/bootia32.efi': [14] Not Found

The reason for that seems to be the cheaper hardware – the CPU was 64-bit, but the UEFI implementation was 32-bit…

Unlike in Linux, for Windows OS there’s one very simple solution: just make 32-bit Windows installation USB stick. Works like a charm!

Jul 15

High Performance power plan is missing in newer builds of Windows 10

You may have noticed that High Performance power plan is missing some versions of Windows 10 especially when running on laptops. Only the Balanced plan is shown.

This is somehow connected to the Modern Standby. I couldn’t find any official statement from Microsoft about removing High Performance power plan.

Continue reading

Mar 16

A critical vulnerability in CredSSP was found that affects RDP and WinRM in all Windows versions

A remote code execution vulnerability in CredSSP provider have been found recently (CVE-2018-0886). It affects RDP and WinRM on all supported Windows versions. An attacker who successfully exploits this vulnerability could relay user credentials to execute code on the target system. Any application that depends on CredSSP for authentication may be vulnerable to this type of attack.You can find more information here:Security Advisory: Critical Vulnerability in CredSSP Allows Remote Code Execution on Servers Through MS-RDP (Video).

It requires the attacker to have access to your network first. But take it seriously – patch your systems.

The fix does not have its own but instead it was included in various KBs:

CVE-2018-0886 | CredSSP Remote Code Execution Vulnerability

The patch was included in March’s patch Tuesday so many Windows Update ready computers should be safe now.

Microsoft plans to make graceful transition from vulnerable to mitigated state of the protocol so clients have time to update and check compatibility/stability. They will release three updates to mitigate the issue:

1) First patch will fix the issueby correcting how CredSSPvalidates requests during the authentication process. The update will introduce a new registry key (and a group policy option Encryption Oracle Remediation) that will change the behavior of CredSSP clients and servers. It was already released on March 13, 2018

Administrators are encouraged toapply the policy and set it to “Force updated clients” or “Mitigated” on client and server computers as soon as possible. These changes will require a reboot of the affected systems

2) On April 17, 2018 Microsoft will release an update to RDP Client (MSTSC) that will enhance the error message that is presented when an updated client fails to connect to a server that has not been updated

3) On May 8, 2018 an update will be released to change the default setting from Vulnerable to Mitigated

The Patch Lady explains everything in details.

Go, patch and configure your systems guys 🙂

Mar 14

Your devices may not receive any Windows security updates as of January 2018

UPDATE: March patches relax antivirus restrictions.

If you’ve not been offered any security updates since January there’s a reason. It appears that some Antivirus programs make unsupported API calls to Windows kernel memory that interfere with January’s updates (especially Meltdown and Spectre patches) and may lead to BSoDs (Blue Screen of Death). To protect customers Microsoft have stopped offering security updates to devices with unsupported AVs.

While waiting for a fix from AV vendors (and if you’re absolutely sure you know what you’re doing) you can temporarily disable the compatibility check. The fix is just a registry key:

According to Microsoft as of March 13-th most of the AV vendors have fixed their products so the compatibility check will be removed soon.

You can find more information here:https://support.microsoft.com/en-us/help/4072699/windows-security-updates-and-antivirus-software

Mar 13

Error: Unable to find resource while trying to upgrade to Windows 10 1709 Enterprise through WSUS

While upgrading to Windows 10 1709 Enterprise via WSUS your clients may report the following error:

(Unable to find resource):ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1709, en-us

This may happen to other versions too

Continue reading

Feb 12

PowerShell™ Notes for Professionals & other books

Stack Overflow used to run an interesting project – Stack Overflow Documentation. It is currently shut down, but thanks to it we now have interesting free books like “PowerShell™ Notes for Professionals book“:

Please keep in mind it was created by SO content that may not be very accurate, like what I’d recently discovered:Are the cmdlets in a pipeline executing in parallel?

Anyway I’d recommend it since it contains an essentials compilation of PowerShell common tasks and language specifics.Good reading indeed!

There are also other books that may catch your interest:http://books.goalkicker.com/