Geek asks and answers

How do DVCS (Github, BitBucket, etc.) ensure project code integrity?

How do DVCS (Github, BitBucket, etc.) ensure project code integrity?

Of course, companies do not claim intellectual rights when uploading your code to their online repositories, but how is the project secured so that in fact people with write / commit access to such repositories can view the data?

What happens if you decide, for example, to move your project to a private server or to another host? Will your project be “deleted” or “deleted” from the public index?

How can you be sure that the CEO of the company in which you place your project will not be able to view your data?

Do these companies conduct any kind of regular certification? Or is the whole deal based on trust and understanding?

+3
source share
3 answers

Unless these providers explicitly offer to offer encrypted repositories (which Assembla link to here , but this can only be referred to as https encryption), we don’t have a 100% guarantee.

The only way to add this level of security is to provide end- to -end encryption under user control using the git smudge / clean filter :

smudge clean filter driver

See Transparent git Encryption :

, , :
, , . / .
, git , .

+5

VonC, , , .

, . , , , , . , , , , , , , . , , .

, , , / Mercurial Git. , , , GitHub Bitbucket.

  • .
  • tarball
  • .

- , , . Kallithea, Git, Mercurial.

+2

As far as I know, the whole transaction is based on trust, understanding and the desire not to sue them to death.

0
source

More articles:


All Articles