Lester Work Space

patch-edid.rb

A script to fix EDID problems on external monitors in macOS.

Instructions

Connect only the problem display.
Create this directory structure (if it doesn’t already exist):
```
sudo mkdir -p /Library/Displays/Contents/Resources/Overrides
```

Download this ruby script in that directory:

cd /Library/Displays/Contents/Resources/Overrides
sudo curl -O https://gist.githubusercontent.com/ejdyksen/8302862/raw/patch-edid.rb

Note: You may want to use adaugherity’s version of the script instead.

Run the script we just downloaded (as root again). This creates a new display override plist file.
```
cd /Library/Displays/Contents/Resources/Overrides
sudo ruby patch-edid.rb
```
Unplug and replug in the problem display.

Additional reading/acknowledgements

The original forum thread
An improved version of the script by adaugherity
An explaination of the problem from Atomic Object’s blog
Thanks so much to @stackrainbow for pointing out that this can be done without disabling SIP.
This version appears to work in Catalina and Big Sur. See earlier revisions for what worked (with disabling SIP) in earlier versions of macOS, which require the override plist to be in a different directory.

GPG signing –

Here is a short guide that will help you setup your environment to create signed commits or signed tags with Git locally. This has been extensively tested on Windows with Git and the Github Desktop application: I use it every day for my professional development projects.

I you face any issue, feel free to leave a comment below.

Sign `commits` or `tags`

Generate a GPG key and add it to Github: https://help.github.com/articles/generating-a-new-gpg-key
(if you don’t want to type a passphrase on every commit, you need to press “Enter” when the console will prompt you to type a passphrase)
Open the .gitconfig configuration file by typing git config --global --edit in a terminal (since this file can exists in different places depending on your operating system, the command line will prompt git binary and open your default editor)
Configure Git by replacing GITHUB_EMAIL, SIGNING_KEY and GPG_BINARY_PATH with your own data:

[user]
  name = Xavier Foucrier
  email = GITHUB_EMAIL
  signingkey = SIGNING_KEY
[gpg]
  program = GPG_BINARY_PATH
[commit]
  gpgsign = true
[tag]
  gpgsign = true

GITHUB_EMAIL: the email address used to login on Github
SIGNING_KEY: the GPG key identifier used to sign commits (should follow the GPG key ID convention, like this example: https://help.github.com/articles/telling-git-about-your-signing-key/#telling-git-about-your-gpg-key-1)
GPG_BINARY_PATH: the GPG binary file path depending on your Git install and your operating system:
- Windows: gpg, gpg.exe or C:\\Program Files\\Git\\usr\\bin\\gpg.exe
  (can be found using where gpg in a terminal)
  
  Some system may contain multiple gpg binaries, in this case you can execute the following command line with PowerShell to use the more appropriate one: git config --global gpg.program $(Resolve-Path (Get-Command gpg | Select-Object -Expand Source) | Select-Object -Expand Path)
- Mac or Linux: gpg or /usr/local/bin/gpg
  (can be found using which gpg in a terminal)

Enjoy signed commits with your favorite code editor, Github Desktop application, and even command line using git commit -S -m "Commit message" 🎉

Key passphrase

In order for GPG to automatically store your key passphrase (even empty), so you don’t have to enter it every time you sign a commit, Github recommend using the following tools:

Windows: GPG 4 Win
Mac: GPG Suite

This is necessary to let GPG launch the gpg-agent as a system daemon when signing commits.

Disable signatures

If you want to temporarily pause GPG signatures for your commits or tags, just set gpgsign = false in your .gitconfig configuration file with git config --global commit.gpgsign false (for commits) or git config --global tag.gpgsign false (for tags).

Renew a GPG key

If the key you have defined in the .gitconfig configuration file has expired, you can’t sign commits anymore. You can easily renew it by following these steps:

list the secrets keys with gpg --list-secret-keys
edit the key you want to renew with gpg --edit-key SIGNING_KEY
(the GPG key used to sign commits, as defined in your .gitconfig configuration file)
gpg prompt is ready: you should see gpg>
type expire to select a new expiration delay and confirm
type trust to trust the selected key as “ultimate”
(this step is not needed if your current key is already trusted as an “ultimate” key)
type quit and confirm you wish to save changes
enjoy a fresh renewed GPG key!

Thanks everyone for reading! 👀

	#!/usr/bin/ruby
	# Create display override file to force Mac OS X to use RGB mode for Display
	# see http://embdev.net/topic/284710
	#
	# Update 2013-06-24: added -w0 option to prevent truncated lines

	require 'base64'

	data=`ioreg -l -w0 -d0 -r -c AppleDisplay`

	edid_hex=data.match(/IODisplayEDID.*?<([a-z0-9]+)>/i)[1]
	vendorid=data.match(/DisplayVendorID.*?([0-9]+)/i)[1].to_i
	productid=data.match(/DisplayProductID.*?([0-9]+)/i)[1].to_i

	puts "found display: vendorid #{vendorid}, productid #{productid}, EDID:\n#{edid_hex}"

	bytes=edid_hex.scan(/../).map{\|x\|Integer("0x#{x}")}.flatten

	puts "Setting color support to RGB 4:4:4 only"
	bytes[24] &= ~(0b11000)

	puts "Number of extension blocks: #{bytes[126]}"
	puts "removing extension block"
	bytes = bytes[0..127]
	bytes[126] = 0

	bytes[127] = (0x100-(bytes[0..126].reduce(:+) % 256)) % 256
	puts
	puts "Recalculated checksum: 0x%x" % bytes[127]
	puts "new EDID:\n#{bytes.map{\|b\|"%02X"%b}.join}"

	Dir.mkdir("DisplayVendorID-%x" % vendorid) rescue nil
	f = File.open("DisplayVendorID-%x/DisplayProductID-%x" % [vendorid, productid], 'w')
	f.write '<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">'
	f.write "
	<dict>
	<key>DisplayProductName</key>
	<string>Display with forced RGB mode (EDID override)</string>
	<key>IODisplayEDID</key>
	<data>#{Base64.encode64(bytes.pack('C*'))}</data>
	<key>DisplayVendorID</key>
	<integer>#{vendorid}</integer>
	<key>DisplayProductID</key>
	<integer>#{productid}</integer>
	</dict>
	</plist>"
	f.close

Field	Value
Key type	RSA (1)
Key length	4096
Expire Date	0
Real Name	Your Name in .gitconfig
Email	Your Email in .gitconfig & GitHub verified email
Comment	github

	For troubleshooting, two things to first try:

	run `git config –global gpg.program gpg2`, to make sure git uses gpg2 and not gpg
	run `echo "test" \| gpg2 –clearsign`, to make sure gpg2 itself is working
	If that all looks all right, one next thing to try:

	run `brew install pinentry` to ensure you have a good tool installed for passphrase entry
	If after that install and you re-try git commit and still get the "failed to sign the data" error:

	run `gpgconf –kill gpg-agent` to kill any running agent that might be hung
	If that says gpgconf isn’t installed or doesn’t have a `–kill` option, you might try this:

	`cp ~/.gnupg ~/.gnupg-GOOD` to save a copy of your `~/.gnupg` to revert to later if needed
	`brew install gnupg21` to install `GnuPG 2.1`
	The reason for saving a copy of your `~/.gnupg` dir is that GnuPG 2.1 potentially creates/changes some key data in way that isn’t backward-compatible with GnuPG 2.0 and earlier, so if you want to go back later, you can do `mv ~/.gnupg ~/.gnupg21 && mv ~/.gnupg-GOOD ~/.gnupg`.

	Otherwise there are some basic steps to run to check you’ve got a working GnuPG environment:

	run `gpg2 -K –keyid-format SHORT`, to check that you have at least one key pair
	If the output of that shows you have no secret key for GnuPG to use, then you need to create one:

	run `gpg2 –gen-key`, to have GnuPG walk you through the steps for creating a key pair

	source: https://stackoverflow.com/a/41054093/4902448

Latest Event Updates

Installation

Introduction

Solution

Introduction

Procedure

Reference

patch-edid.rb

Instructions

Additional reading/acknowledgements

Introduction

Method

Reference:

Introduction

Reference

Reference

Reference:

Introduction

Methods

1. Disable the audio idle mode

2. Create a dummy sound generator

Reference

JVM

Java 14 (OpenJDK 14)

Java13 (openjdk 13)

Java 11 (openjdk 11)

Java 8 (Launcher Built-In version)

Introduction

Procedure

1. Create GPG key

2. Check your GPG key information

3. Export the Public key to

4. Edit your .gitconfig

5. Setting on your shell

Useful command

Edit the existing GPG key

Test you GPG key

Reference

GPG signing –

Summary

Sign commits or tags

Key passphrase

Disable signatures

Renew a GPG key

Sign `commits` or `tags`