Git – My Shitty Code

Git LFS: “Certificate Signed by Unknown Authority” Error

Shitty Author — Mon, 20 May 2024 14:01:16 +0000

Problem

Your organization enforces zero-trust network access (ex: Zscaler or equivalent).

Based on the ZScaler’s documentation, you made a copy of the Zscaler certificate and added it to Git.

git config --global http.sslcainfo ~/ca_certs/zscaler.pem

The Git’s core commands work successfully. However, when using Git LFS to manage large binary files, it failed with the following errors.

$ git push
Uploading LFS objects:   0% (0/3), 0 B | 0 B/s, done.                                                                                
LFS: Put "https://github-cloud.s3.amazonaws.com/alambic/media/703534560/85/85/858586aa357aa9e8c78f64d76a5d6a866ff4f06160508ac5af50175b604b0c77?actor_id=6835135&key_id=0&repo_id=779032228": tls: failed to verify certificate: x509: certificate signed by unknown authority
LFS: Put "https://github-cloud.s3.amazonaws.com/alambic/media/703534560/5c/47/5c4796e25fcb54726bd605f825d3f53c0804164186ee989af5649164d5026a10?actor_id=6835135&key_id=0&repo_id=779032228": tls: failed to verify certificate: x509: certificate signed by unknown authority
LFS: Put "https://github-cloud.s3.amazonaws.com/alambic/media/703534560/9c/76/9c766b0bf3e91eed522df3c5e508ce33a6c781a4891c8395154149eb60b537e0?actor_id=6835135&key_id=0&repo_id=779032228": tls: failed to verify certificate: x509: certificate signed by unknown authority
error: failed to push some refs to 'github.com:xxxxxxx/my-repo.git'

Solution

Instead of explicitly pointing to a ZScaler certificate, configure Git to rely on the device’s global trust store, where your security team should have already added the ZScaler certificate.

git config --global http.sslBackend openssl
git config --global --unset http.sslcainfo

Now, Git LFS commands will work successfully.

$ git push
Uploading LFS objects: 100% (3/3), 194 MB | 26 MB/s, done.
Enumerating objects: 1292, done.
Counting objects: 100% (1292/1292), done.
Delta compression using up to 11 threads
Compressing objects: 100% (1280/1280), done.
Writing objects: 100% (1280/1280), 83.42 MiB | 6.93 MiB/s, done.
Total 1280 (delta 751), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (751/751), completed with 6 local objects.
To github.com:xxxxxxx/my-repo.git
4075ed3..ce4a0e7 main -> main
sh-3.2$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

The post Git LFS: “Certificate Signed by Unknown Authority” Error appeared first on My Shitty Code.

Git: Querying Tags Without Cloning the Repository

Shitty Author — Fri, 02 Oct 2020 16:40:37 +0000

PROBLEM

A typical way to get a list of tags from a repository is to clone it before running git tag:-

git clone git@ssh.dev.azure.com:v3/test/my-shitty-repo
cd my-shitty-repo
git -c 'versionsort.suffix=-' tag --sort='v:refname'

# output
1.0.0-b20200317174203
1.0.0
1.0.1-b20200318174753
1.0.1-b20200318174841
1.0.1-b20200407185909
1.0.1
1.0.2-b20200413205910
1.0.2

versionsort.suffix=- ensures 1.0.0-XXXXXX comes after 1.0.0.

To retrieve the latest tag:-

git clone git@ssh.dev.azure.com:v3/test/my-shitty-repo
cd my-shitty-repo
git -c 'versionsort.suffix=-' tag --sort='v:refname' |
tail -n1

# output
1.0.2

While it works, it requires us to clone the repository first, and if we want to retrieve tags from multiple repositories, we are quickly filling our hard drive space.

SOLUTION

Git has a way to perform a remote query through git ls-remote.

To perform the same task without cloning the repository, we can run this:-

git -c 'versionsort.suffix=-' ls-remote \
--tags \
--sort='v:refname' \
git@ssh.dev.azure.com:v3/test/my-shitty-repo

# output
b90df3d12413db22d051db1f7c7286cdd2f00b66	refs/tags/1.0.0-b20200317174203
e355a58829a2d2895ab2d7610fad1ab26dc0c1e7	refs/tags/1.0.0
345153c39a588a6ab2782772ee9dcf9f9123efa9	refs/tags/1.0.1-b20200318174753
efc40f0bd68bb8c7920be7700cab81db0e6bdf83	refs/tags/1.0.1-b20200318174841
efc40f0bd68bb8c7920be7700cab81db0e6bdf83	refs/tags/1.0.1-b20200407185909
c5ed5fe30cba621f40daa542c0613fa2c1c1a47d	refs/tags/1.0.1
7205ada5d8bd4318f82e58e8752ba651211f9d82	refs/tags/1.0.2-b20200413205910
6ba62a0f06f831812cbb13a6d1e83602ffe9e8d3	refs/tags/1.0.2

To retrieve the latest tag:-

git -c 'versionsort.suffix=-' ls-remote \
--tags \
--sort='v:refname' \
git@ssh.dev.azure.com:v3/test/my-shitty-repo |
tail -n1 |
sed -E 's|.*refs/tags/(.+)|\1|'

# output
1.0.2

The post Git: Querying Tags Without Cloning the Repository appeared first on My Shitty Code.

Git: Configuring Different Git User Info Depending on Projects

Shitty Author — Wed, 18 Dec 2019 09:29:42 +0000

PROBLEM

Given, the following global config stored under ~/.gitconfig…

[user]
    name = Shitty Developer
    email = shittydeveloper@work.com

When committing any code, the above user info will always be used.

However, there are times you want to use a different user info depending on projects (ex: work projects, GitHub projects, etc)

SOLUTION

This is one of many ways to solve this problem.

Let’s assume shittydeveloper@work.com configured in ~/.gitconfig is reserved for work-related projects.

To set up a different user email for GitHub projects, modify ~/.gitconfig with the following configuration:-

[user]
    name = Shitty Developer
    email = shittydeveloper@work.com

[includeIf "gitdir:~/github/"]
    path = ~/github/.gitconfig

Under ~/github/.gitconfig, add your GitHub user account’s email:-

[user]
    email = shittydeveloper@personal.com

If the checked out project resides under ~/github/ directory, any committed code will now use shittydeveloper@personal.com instead of shittydeveloper@work.com.

The post Git: Configuring Different Git User Info Depending on Projects appeared first on My Shitty Code.

Git + Linux: (gnome-ssh-askpass:24871): Gtk-WARNING **: cannot open display:

Shitty Author — Mon, 12 Sep 2016 16:11:10 +0000

PROBLEM

When running git clone on Linux, the following error appears:-

-bash-4.1$ git clone http://user@tfs:8080/tfs/my-institution/my-domain/_git/my-project
Initialized empty Git repository in /people/my-group/user/my-project/.git/

(gnome-ssh-askpass:24871): Gtk-WARNING **: cannot open display:

SOLUTION

To fix this, run the following command to disable gnome-ssh-askpass:-

-bash-4.1$ unset SSH_ASKPASS

Now, git clone will work just fine:-

-bash-4.1$ git clone http://user@tfs:8080/tfs/my-institution/my-domain/_git/my-project
Initialized empty Git repository in /people/my-group/user/my-project/.git/
Password:
remote:
remote:                    fTfs
remote:                  fSSSSSSSs
remote:                fSSSSSSSSSS
remote: TSSf         fSSSSSSSSSSSS
remote: SSSSSF     fSSSSSSST SSSSS
remote: SSfSSSSSsfSSSSSSSt   SSSSS
remote: SS  tSSSSSSSSSs      SSSSS
remote: SS   fSSSSSSST       SSSSS
remote: SS fSSSSSFSSSSSSf    SSSSS
remote: SSSSSST    FSSSSSSFt SSSSS
remote: SSSSt        FSSSSSSSSSSSS
remote:                FSSSSSSSSSS
remote:                  FSSSSSSs
remote:                    FSFs    (TM)
remote:
remote:  Microsoft (R) Visual Studio (R) Team Foundation Server
remote:
Receiving objects: 100% (504/504), 1.05 MiB, done.
Resolving deltas: 100% (138/138), done.

To prevent this from happening again, add unset SSH_ASKPASS command to .bashrc file.

The post Git + Linux: (gnome-ssh-askpass:24871): Gtk-WARNING **: cannot open display: appeared first on My Shitty Code.

Git – My Shitty Code

Git LFS: “Certificate Signed by Unknown Authority” Error

Table of Contents

Problem

Solution

Git: Querying Tags Without Cloning the Repository

PROBLEM

SOLUTION

Git: Configuring Different Git User Info Depending on Projects

PROBLEM

SOLUTION

Git + Linux: (gnome-ssh-askpass:24871): Gtk-WARNING **: cannot open display:

PROBLEM

SOLUTION