A Guide for Hackers Who Want to Have Write Permission on a Git Based ProjectThis article describes how to be a programmer with all kinds of go oriented workflows to send content to all kinds of forge (software repository platform) related to content creation.Set SSH KeysPlease read the following links: * https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding -it-to-the-ssh-agent * https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent * Configuring the https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-accountGPG Key * https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key * After creating the GPG Key then please execute the following command: gpg --list-secret-keys --keyid-format =long* Then execute this command but replace 3AA5C34371567BD2 with your GPG Key ID: gpg --output secret.key --export-secret-keys 3AA5C34371567BD2 * Then execute this command for Cancellation Certificate but replace 3AA5C34371567BD2 with your GPG Key ID: gpg --output revoke.asc --gen-revoke 3AA5C34371567BD2 * Then execute your public key with this command d import but replace 3AA5C34371567BD2 with your GPG Key ID: gpg --armor --export 3AA5C34371567BD2 > 3AA5C34371567BD2.asc * Publish to PGP Global Directory, import key, trust and sign with Thunderbird Email Client or another client * After that, back up your secret.key and revoke.asc files to an external disk and keep them safe. * Then open your public key with a text editor and all text copy and add your Public Key to GitHub as described here: https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-accountTo sign the contents you have written with your GPG Key, please read the following links: * https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits * https://docs.github.com/en/authentication/managing-com mit-sign-verification/telling-git-about-your-signing-keyFor control:chmod +x git-sign-check.sh./git-sign-check.shConfigure User Email and Username for commits * https://docs.github.com/en/get-started/getting-started-with-git/setting-your-username-in-git * https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-addressSo nuç * We created the SSH Key and added our public SSH Key to our GitHub account. * In this example, we created the GPG Key, sent our public key to a server, and then moved our secret.key and revoke.asc to an external drive. We then added our GPG public key to your GitHub account. * We configured our git account to sign the content we wrote.happy hacks (wish you success and success) Where do we store these documents? * https://source.masscollabs.xyz/masscollaborationlabs/hacker-how-to * https://github.com/hwpplayer1/hacker-how-to * https://gitlab.com/masscollabs/masscollaborationlabs/hacker-how-to * https://git.sr.ht/~mertgor/hacker-how-to * https://gi t.disroot.org/hwpplayer1/hacker-how-to* https://codeberg.org/hwpplayer1/hacker-how-toLisansCCBY-SA 4.0 or later
A Guide for Hackers Who Want to Have Write Permission on a Git Based Project
SSH, PGP/GnuPG, Git, and GitHub training
Yorumlar
0 yorum