Re: Writing to the PacSatx git repository
![](https://secure.gravatar.com/avatar/f9c46d7daace2ed712d35f89c05e6a4c.jpg?s=120&d=mm&r=g)
I am using ssh keys from the Linux command line (and windows). That works for me. You are authenticating to your own GitHub account of course, so the public key is stored in security preferences for your account. If you can push to one of your own repos with ssh then you should be able to push to the Pacsat repos. At least that was my experience.
73 Chris
On Wed, Mar 1, 2023, 10:44 Jonathan Brandenburg via pacsat-dev < [email protected]> wrote:
I'm happiest with Linux command line, too. I'll use one of my other GitHub accounts that doesn't have special privileges in an attempt to reproduce the behavior.
In the meantime, as you say, SSH keys can be a good option. I'll also use that in this environment. I'm been using 2FA with my account so this hasn't popped up.
Jonathan On 3/1/23 09:37, Bob Stricklin via pacsat-dev wrote:
Thanks to all for feedback…
I can use any of the systems and methods you described Jonathan. My preferred method is fro the command line on Linux but if I get that working I can use MAC too. Windows would be my last choice.
I have used SSH keys. Let me look into that idea. That would be a good solution if it works.
Never had any trouble with cloning a repository. The issue is writing and deleting and creating on a repository. I have done all this on my own repository. Burns, since you created PacSatx you are the owner and I would not expect you to have a problem.
Bob
On Mar 1, 2023, at 8:28 AM, Burns Fisher (AMSAT) via pacsat-dev < [email protected]> wrote:
I've never had to use a token to clone a repo. I just did this yesterday with the loader repo that Heimir created. I just looked in "Code" for the URL to clone. So for pacsatx, it should be
git clone https://github.com/AMSAT-NA/PacSatx.git https://url.emailprotection.link/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQqKd4-_qp1P6J2hyvx5HYIn46psONW2RmErQVVoec7it1zA~~
Checking something in is a different ball of wax. However, by "normal" personal access token, created in my own account about the time that github stopped allowing the normal password for checkins, seems to work fine. There is also the public key method, but I think you have to mess around with your local git to make that work. Or something. It works for the repos in my own area, but not for the AMSAT-NA repos.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev < [email protected]> wrote:
I am happy to have a look at it. Can you remind me of your environment, please?
Are you Windows, Mac or Linux?
Are you using command line, web interface, or a Git client (like TortoiseGit)?
Is your personal access token one of the fine-grained tokens? (There are a little tricky to use interactively but it can be configured. They must be given access to each individual API call as they are designed for automatic scripts.) Or is this a "classic" personal access token? (I know those are discouraged because of the ability for "lateral movement" between repositories in an organization.) Or, are you using 2FA? (I believe 2FA is the preferred mechanism for interactive human access).
Thank you!
Jonathan On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote:
All,
I continue to have an issue writing to the PacSatx repository. Jonathan has adjusted permissions to give me write access. Apparently there is more to it in this case. My use of git has mostly been with a repository I setup or one a company had. In this case it seems several here have owner rights in this repository.
I have tried with one of my personal access Tokens, but I have seen this from GIT:
Each token can only access resources owned by a single user or organization. Each token can only access specific repositories. Each token is granted specific permissions, which offer more control than the scopes granted to personal access tokens (classic). Each token must have an expiration date. Creating a personal access token - GitHub Docs https://url.emailprotection.link/?b_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5NiNcheXSPi5ad6lpoiLYS_7EoHdBqPgBqcBmrYGl9TCEOmzdOAGdOHrSj2rNJ0c43m52tUxFfreAFoQbgnnVKr0NY_y4tvYfiUTGlwNJwByMR7VOuwk3vHavT_VU_8vym90CWHaOtBQOf-0YUBHAWCq6rg_JedoP4R20NrmbReQio3MTJtMWVNs79RXJFXtuy_nMd0Z1Xw5ctyR45u44LHTy
I have also read it may be possible to access a GIT if you have a project Token and create access with that using:
git clone "https://my-project: https://url.emailprotection.link/?bUGyKvxiy3XARL1hpyUkkd27ECbOJxe-qS3Nqu-kpkT9_xhPy1QwQzVbMF8kinUGtVMexFXmYjFDiYMXY9oCCCw~~[email protected]/my-group/my-project.git"
Would anyone that knows the process on how to do this please help with the steps or send me the needed Token so i can gain access?
Thanks,
Bob
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aqxOQfa9Eqh8kfGK8xAPNkaYeV4y3Z5HVIEvNBaAimp_ZfFMwcw8QT0XZxGj2iXsHa3mcBRxu810JiHLaLtHS4Ej_7 To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gik24jnwI-Byk6ZVn92BYiD7Bxz61XZBoNoJE1TKqdfKnwFw~~
-- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aqxOQfa9Eqh8kfGK8xAPNkaYeV4y3Z5HVIEvNBaAimp_ZfFMwcw8QT0XZxGj2iXsHa3mcBRxu810JiHLaLtHS4Ej_7 To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gik24jnwI-Byk6ZVn92BYiD7Bxz61XZBoNoJE1TKqdfKnwFw~~
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
participants (1)
-
Chris Thompson