Netgate SG-1000 microFirewall

Author Topic: Tools Repo  (Read 16999 times)

0 Members and 1 Guest are viewing this topic.

Offline S. Kirschner

  • Jr. Member
  • **
  • Posts: 35
  • Karma: +0/-0
    • View Profile
Re: Tools Repo
« Reply #45 on: September 24, 2015, 03:41:29 am »
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

Offline jporter

  • pfSense/Netgate Operations
  • Jr. Member
  • **
  • Posts: 30
  • Karma: +12/-0
  • NSSLabs Devops
    • View Profile
    • Freeside
Re: Tools Repo
« Reply #46 on: October 03, 2015, 03:11:38 pm »
We need to update the documentation about moving back to github.  And create a wiki document on it.
Jessica Porter

Offline David_W

  • Sr. Member
  • ****
  • Posts: 386
  • Karma: +74/-0
    • View Profile
Re: Tools Repo
« Reply #47 on: October 11, 2015, 10:29:13 am »
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!

Offline chrcoluk

  • Sr. Member
  • ****
  • Posts: 387
  • Karma: +20/-50
    • View Profile
Re: Tools Repo
« Reply #48 on: June 08, 2017, 10:09:31 am »
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).
pfSense 2.4
Qotom Q355G4 or Braswell N3150 with Jetway mini pcie 2x intel i350 lan - 4 gig Kingston 1333 C11 DDR3L
 - 60 gig kingston ssdnow ssd - ISP Sky UK

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21397
  • Karma: +1432/-26
    • View Profile
Re: Tools Repo
« Reply #49 on: June 12, 2017, 10:37:06 am »
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.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!