Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practices for setting up & securing a BitBucket Mercurial repo Edited

What are the best practices for setting up and for securing all aspects of a BitBucket Mercurial repo (hosted on bitbucket.org), including access, ensuring simplified commit histories and branch heads, etc.?

For pushes, can I:

  1. Forbid creating more than one head per branch
  2. Forbid commits from users whose user name does not exactly match a BitBucket account, either matching by email address alone, or also including the full name?  Can I restrict the email address (& possibly full name) to that of the approved BitBucket account at the time when that account was authorized  (i.e., the BitBucket account email address and full name cannot have changed)
  3. Require that all commits are digitally signed, either via the Commitsigs extension, or via some other mechanism
  4. Require that all pushed heads build successfully, pass all tests, and conform to formatting / linting standards
  5. Use the ACL extension to allow / deny access to particular users for particular files
  6. Require that no files that match any .hginore patterns are ever committed

Obviously there are other components of setup & security.  It would be great to compile a comprehensive guide.  Other potential practices include:

  1. requiring two-factor authentication
  2. requiring ed25519 ssh keys
  3. enabling ssh compression
  4. assigning repos to projects within teams

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

815 views 15 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you