Required Original Power supply Specification

An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mysql.com/apt/ubuntu focal InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
Solution
sudo apt-key adv –keyserver keyserver.ubuntu.com –recv-keys 467B942D3A79BD29
If “467B942D3A79BD29” is different – just change it for value from error message.
Quite interesting story, we have website running WordPress with two noticed problems:
Trying this malformed CURL command reveal hidden from naked eye problem.
curl -d "auth=something" -X POST https://somewebsite.com/index.php\?rest_route\=/plugin/route/test --trace-ascii --
In front of JSON data there is UTF-8 BOM code (\ufeff) (it’s being ignored by most of application but not all, it should never be present in JSON response since encoding is send in HTTP header – some code is ignoring it, some will fail on decode JSON and thread it as invalid syntax.
When we know what to look for, we need scan all PHP files on server and locate ( 0xEF, 0xBB, 0xBF ) string in root website directory using following command:
grep -rlI $’\xEF\xBB\xBF’ .
From result ignore anything that is not .PHP since those files can have BOM and not directly parsed via PHP interpreter.
Download those PHP file and examine with “HexEditor” reveal BOM before PHP code that is being send along ANY content served from PHP.
Cleaning file from “BOM” mark (on MAC):
sed $’1s/\xef\xbb\xbf//’ < in8sync-customization.php > clean-in8sync-customization.php
Compare two files together to make sure only BOM is removed.
Upload cleaned file in original location and repeat process if there is more than one. Be happy fixing unusual issue!!
Here is dump of ROM (in case You have broken unit, You can reprogram this ROM using generic IC)
Generic universal driver for all pendrives / flash storage devices.
Tested on Windows 98 SE
Recently I have interesting issue of not being able to access my network shares on AirPort Time Capsule from Windows 10.
Pinging Time Capsule was successfull but trying access in file explorer (\\ip-address\untitled\share) cause unknown error.
Problem was caused by disabled SMB 1.0/CIFS File Sharing Support by default in Windows 10 that make it unable to connect. Reason of SMB being disabled is obsolete and have security issues but in my opinion this is not problem in trusted home network where all devices are our’s.
To enable support for SMB 1.0/CIFS File Sharing You need to open PowerShell with elevated permissions (run as administrator) and execute following command:
Enable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol" -All
Afrer restart You will be able to access Your Time Capsule shares.
This device is quite obsolete and I have lot trouble finding correct working drivers. (on Win 10 drivers need to be installed from device manager – navigating to program files newly created directory.
Recently I have interesting problem with Valet using wrong PHP version on my Laravel application, trying to switch it from terminal not fix issue and stating it’s already done even including force relink.
valet use php@7.4 –force
Unlinking current version: php@7.4
Linking new version: php@7.4
Updating PHP configuration…
Restarting php@7.4…
Restarting nginx…
Valet is now using php@7.4.
Solution for this problem was using following command
rm ~/.config/valet/valet.sock
valet use php@7.4 –force
After that Valet use correct PHP version in my application.
Solution – regenerate view cache (clear existing one):
php artisan view:clear