git checkout --orphan future-master
git add -A # Add all files and commit them
git commit
git branch -D master # Deletes the master branch
git branch -m master # Rename the current branch to master
git push -f origin master # Force push master branch to github
git gc --aggressive --prune=all # remove the old files
| # Run this as a Computer Startup script to allow installing fonts from C:\InstallFont\ | |
| # Based on http://www.edugeek.net/forums/windows-7/123187-installation-fonts-without-admin-rights-2.html | |
| # Run this as a Computer Startup Script in Group Policy | |
| # Full details on my website - https://mediarealm.com.au/articles/windows-font-install-no-password-powershell/ | |
| $SourceDir = "C:\InstallFont\" | |
| $Source = "C:\InstallFont\*" | |
| $Destination = (New-Object -ComObject Shell.Application).Namespace(0x14) | |
| $TempFolder = "C:\Windows\Temp\Fonts" |
| :: Windows 10 Hardening Script | |
| :: This is based mostly on my own personal research and testing. My objective is to secure/harden Windows 10 as much as possible while not impacting usability at all. (Think being able to run on this computer's of family members so secure them but not increase the chances of them having to call you to troubleshoot something related to it later on). References for virtually all settings can be found at the bottom. Just before the references section, you will always find several security settings commented out as they could lead to compatibility issues in common consumer setups but they're worth considering. | |
| :: Obligatory 'views are my own'. :) | |
| :: Thank you @jaredhaight for the Win Firewall config recommendations! | |
| :: Thank you @ricardojba for the DLL Safe Order Search reg key! | |
| :: Thank you @jessicaknotts for the help on testing Exploit Guard configs and checking privacy settings! | |
| :: Best script I've found for Debloating Windows 10: https://github.com/Sycnex/Windows10Debloater | |
| : |
| #!/bin/bash | |
| # This replicates xclip functionality used by pass in Cygwin/MSYS2 | |
| # Original author: https://tylor.io/2015/07/13/password-manager/ | |
| while [[ $# > 0 ]] | |
| do | |
| key="$1" | |
| case $key in | |
| -o|-out) |
Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.
And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.
If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
| # List all possible power config GUIDs in Windows | |
| # Run: this-script.ps1 | Out-File powercfg.ps1 | |
| # Then edit and run powercfg.ps1 | |
| # (c) Pekka "raspi" Järvinen 2017 | |
| $powerSettingTable = Get-WmiObject -Namespace root\cimv2\power -Class Win32_PowerSetting | |
| $powerSettingInSubgroubTable = Get-WmiObject -Namespace root\cimv2\power -Class Win32_PowerSettingInSubgroup | |
| Get-WmiObject -Namespace root\cimv2\power -Class Win32_PowerSettingCapabilities | ForEach-Object { | |
| $tmp = $_.ManagedElement |
| package main | |
| import ( | |
| "syscall" | |
| "unsafe" | |
| "fmt" | |
| "os" | |
| "os/exec" | |
| "path/filepath" | |
| ) |
| 000000 Officially Xerox | |
| 000001 SuperLAN-2U | |
| 000002 BBN (was internal usage only, no longer used) | |
| 000003 XEROX CORPORATION | |
| 000004 XEROX CORPORATION | |
| 000005 XEROX CORPORATION | |
| 000006 XEROX CORPORATION | |
| 000007 XEROX CORPORATION | |
| 000008 XEROX CORPORATION | |
| 000009 powerpipes? |
| package exportstats | |
| import ( | |
| "expvar" | |
| "fmt" | |
| "runtime" | |
| ) | |
| var stats *expvar.Map |
This is how to connect to another host with your docker client, without modifying your local Docker installation or when you don't have a local Docker installation.
First be sure to enable the Docker Remote API on the remote host.
This can easily be done with a container.
For HTTP connection use jarkt/docker-remote-api.