- pacsat-dev - mailman.amsat.org

Pacsat dev meeting 3-2-2023
by Bill 02 Mar '23

02 Mar '23

Pacsat dev meeting 3-2-2023 Thu, Mar 2, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/131084093 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3112 - One-touch: tel:+15713173112,,131084093# Access Code: 131-084-093 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Writing to the PacSatx git repository
by Chris Thompson 01 Mar '23

01 Mar '23

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 < pacsat-dev(a)amsat.org> 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 < > pacsat-dev(a)amsat.org> 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/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQ…> > > 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 < > pacsat-dev(a)amsat.org> 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_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5…> >> >> 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-kp…>$PROJECT_TOKEN(a)my.gitlab.host/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 -- pacsat-dev(a)amsat.org >> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> >> -- >> Jonathan Brandenburg >> Radio Amateur Satellite Corporation >> 1-214-213-1066 >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org >> <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > 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 -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Writing to the PacSatx git repository
by Jonathan Brandenburg 01 Mar '23

01 Mar '23

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 >> <pacsat-dev(a)amsat.org> 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/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQ…> >> >> 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 >> <pacsat-dev(a)amsat.org> 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_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5…> >>> >>> >>> 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-kp…>$PROJECT_TOKEN(a)my.gitlab.host/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 --pacsat-dev(a)amsat.org >>> View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >>> To unsubscribe send an email topacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> >> -- >> Jonathan Brandenburg >> Radio Amateur Satellite Corporation >> 1-214-213-1066 >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org >> <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

Re: Writing to the PacSatx git repository
by Bob Stricklin 01 Mar '23

01 Mar '23

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 <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> 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/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQ…> 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 <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> 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_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5…> 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-kp…>$PROJECT_TOKEN(a)my.gitlab.host/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 -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066 ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Writing to the PacSatx git repository
by Burns Fisher (AMSAT) 01 Mar '23

01 Mar '23

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 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 < pacsat-dev(a)amsat.org> 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://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> > > 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:$PROJECT_TOKEN@my.gitlab.host/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 -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > 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 -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Writing to the PacSatx git repository
by Corey Minyard 01 Mar '23

01 Mar '23

On Wed, Mar 01, 2023 at 02:51:54AM +0000, 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://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> > > 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:$PROJECT_TOKEN@my.gitlab.host/my-group/my-project.git" There's probably an easier way to do this, especially if you are running on Linux. You need to create an ssh key and upload it. On Linux you should already have one in ~/.ssh/id_xxx.pub, where xxx is the key type. If that's not there, then run ssh-keygen. I'd recommend using an ed25519 key, but rsa is fine. (Run ssh-keygen -t ed25519). Don't use dsa. I don't know how to do that on Windows. Then you need to upload it to github. That's in "settings" -> SSH and GPG keys. Then click on "New SSH key". Then paste in the contents of the public key file (ends in .pub, as above). Once you have that, clone it with ssh. In the repository view on github, you click on "Code" then shoose Local then SSH. Clone what is says there, like "git clone git@github.com:AMSAT-NA/pacsat.git". I've never tries the otken access because it's fairly inconvenient. -corey > > 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 -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Writing to the PacSatx git repository
by Jonathan Brandenburg 01 Mar '23

01 Mar '23

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://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> > > > 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://my-project:>$PROJECT_TOKEN(a)my.gitlab.host/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 --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

Writing to the PacSatx git repository
by Bob Stricklin 28 Feb '23

28 Feb '23

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://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> 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:$PROJECT_TOKEN@my.gitlab.host/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

1 0

QEMU emulation not feasibly doable
by Corey Minyard 24 Feb '23

24 Feb '23

I was studying the design of the serial port and the N2HET device on the TMS570, and emulating that in QEMU is not really an option. Since that's how the debug serial port is done and perhaps how some I2C devices are accessed, it doesn't make sense to do the QEMU emulator. Just for details on this, the N2HET is a separate coprocessor, and would require writing an instruct set front end to work properly, or writing an emulator of some kind. That's a pretty big job in QEMU, but it could be done. However, even if you got one of these working, it still wouldn't work for our purposes. The way the N2HET is used, it's bit-banging (sending and receiving a bit at a time) in and out serial and I2C data. That's extremely timing dependent for serial (not so much for I2C), and an emulator is not going to be able to do that easily. Again, it could be done, but the code required to take the outputs of the N2HET and covert it back to bytes would be hard. It would be more feasible to emulate what the N2HET does in our configuration, but that's not going to be accepted into QEMU, so maintenance for this would fall on us. Sorry for the bad news. It would have been nice to have this. Looks like I'm going to need a board. Note, as an aside, this kind of thing uses a lot of power. The SCI and I2C devices on the TMS570 are likely to use a lot less power. Not all TMS570 SOCs have an I2C, though. -corey

1 0

PACSAT Weekly Engineering Meeting 2023-02-23
by Jonathan Brandenburg 22 Feb '23

22 Feb '23

Here's the info for tomorrow's meeting: *PACSAT Weekly Engineering Meeting 2022-02-23* Feb 23, 2023, 7:00 – 8:00 PM (America/Chicago) *Please join my meeting from your computer, tablet or smartphone.* https://meet.goto.com/742034085 *You can also dial in using your phone.* Access Code: 742-034-085 United States: +1 (872) 240-3412 <tel:+18722403412,,742034085> *Get the app now and be ready when your first meeting starts:* https://meet.goto.com/install -- jbrandenburg(a)amsat.org

1 0