Tools Repo
-
The pfsense-tools repo was showing up for me on GitHub a few weeks back, but now it seems to be gone again?!
-
The pfsense-tools repo was showing up for me on GitHub a few weeks back, but now it seems to be gone again?!
It is still there for me, private repo and updated 7 hours ago, so it is not a general problem - I guess you are special :)
-
Yeah that would be nice to have. I unfortunately did not have my GitHub details in there at the time of the announcement but do now.
Unfortunately still don't have access though.You should have received a confirmation email from github to whatever email is in your github account settings.
-
The pfsense-tools repo was showing up for me on GitHub a few weeks back, but now it seems to be gone again?!
I see your github user in there, are you looking in the right spot?
-
You should have received a confirmation email from github to whatever email is in your github account settings.
Nope received nothing. Also double checked mail logs but no email from them.
-
-
A few weeks ago pfsense-tools appeared as a private repo on GitHub for me (and presumably for others that were already signed up). Can someone update the instructions here to say where the pfsense-tools repo will be found after you sign up?
We are going to make a wiki page with the updated information. I'll post here when it is done. thanks for pointing that out Phil.
-
I see your github user in there, are you looking in the right spot?
Hah, turns out I wasn't logged in, and for some reason Github unhelpfully reports a 404 error in that case. All good now.
-
Did you complete the ICLA/CCLA and LA part?
yeah awhile back already. My GH username wasnt there when the repo was moved to GitHub but prior to that I had access.
-
Did you complete the ICLA/CCLA and LA part?
yeah awhile back already. My GH username wasnt there when the repo was moved to GitHub but prior to that I had access.
Ah, they were set to expire after 1 year so you will have to fill them out again, all your info should be there so it should be quick. They expire manually now.
https://portal.pfsense.org/members/signup/ICLA
https://portal.pfsense.org/members/signup/CCLAhttps://portal.pfsense.org/members/signup/LA
Once you do that you should be set.
-
Ah, they were set to expire after 1 year so you will have to fill them out again, all your info should be there so it should be quick. They expire manually now.
https://portal.pfsense.org/members/signup/ICLA
https://portal.pfsense.org/members/signup/CCLAhttps://portal.pfsense.org/members/signup/LA
Once you do that you should be set.
Thanks - i did do the ICLA+CCLA ones a few weeks ago thinking that they might have expired but did not do the LA one. Which i have done now.
…and now sorted. Thank you.
-
Could anyone confirm that this is still working? I've accepted the ICLA + LA and still nothing, it just asks for a password. I've verified the public key is working on my end using github. Thanks.
-
Could anyone confirm that this is still working? I've accepted the ICLA + LA and still nothing, it just asks for a password. I've verified the public key is working on my end using github. Thanks.
I had the same issue,
Piba gave me the hint that i could clone from github.
git@github.com:pfsense/pfsense-tools.git
-
We need to update the documentation about moving back to github. And create a wiki document on it.
-
@S.:
Piba gave me the hint that i could clone from github.
git@github.com:pfsense/pfsense-tools.git
Arguably best practice now is to a personal access token on GitHub with minimal permissions - 'repo' and 'public_repo' should be enough. You then use https://<username>@github.com/pfsense/pfsense-tools.git as the repository URL once you have been added to the pfsense team and accepted the team membership.
You should dedicate this token to pfSense development use, as you can generate as many tokens as you have use for. If the token is compromised, generate a new one to replace it.
It saves frustration if you allow git to cache the token in memory for a period of time, e.g. for 300 seconds:
git config –global credential.helper 'cache --timeout 300'
You should seriously consider enabling two factor authentication and U2F on your GitHub account. If you are considering buying a Yubikey, I encourage you to skip the U2F only key and go for a Yubikey Neo, which supports Yubico OTP, U2F, OpenPGP, PIV (X.509 certificates) and OATH (the six or eight digit codes typically used with a phone app) all in one device.
If you do opt for hardware security like a Yubikey, make sure you have appropriate backups if the Yubikey fails, is lost or stolen!</username>
-
I am stuck here as well, I have accepted the agreements and added my key.
What is the specific steps to grab the tools, as it says permission denied (pubkey).
-
The tools repo is no longer used. Everything needed to build current versions is in the public repositories on github. There is a reason this thread has not had any activity in years. Locking.
