summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAge
* removedGravatar xloem2017-03-03
|
* Added a comment: Non-conforming blobsGravatar xloem2017-03-03
|
* Added a comment: Non-conforming blobsGravatar xloem2017-03-03
|
* Added a commentGravatar mbroadhead2017-03-02
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-03-02
|\
* | Linux standalone builds put the bundled ssh last in PATH, so any system ssh ↵Gravatar Joey Hess2017-03-02
| | | | | | | | | | | | will be preferred over it. This commit was sponsored by Denis Dzyubenko on Patreon.
| * (no commit message)Gravatar kevang2017-03-02
|/
* commentGravatar Joey Hess2017-03-02
|
* show how this is not specific to git-annex at allGravatar Joey Hess2017-03-02
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-03-02
|\
* | updateGravatar Joey Hess2017-03-02
| |
| * (no commit message)Gravatar mbroadhead2017-03-02
|/
* status: Propigate nonzero exit code from git status.Gravatar Joey Hess2017-03-02
|
* commentGravatar Joey Hess2017-03-02
|
* followupGravatar Joey Hess2017-03-02
|
* fix formatGravatar Joey Hess2017-03-02
|
* clarificationGravatar Joey Hess2017-03-02
|
* commentGravatar Joey Hess2017-03-02
|
* titleGravatar Joey Hess2017-03-02
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-03-02
|\
* | commentGravatar Joey Hess2017-03-02
| |
| * Added a commentGravatar git-annex@31849d241f10c295b30a9707352ae5c7d743adb72017-03-02
| |
| * removedGravatar git-annex@31849d241f10c295b30a9707352ae5c7d743adb72017-03-02
| |
| * Added a commentGravatar git-annex@31849d241f10c295b30a9707352ae5c7d743adb72017-03-02
| |
| * (no commit message)Gravatar Michel2017-03-02
|/
* github mirror has been removed due to their horrible new anti-free-software TOSGravatar Joey Hess2017-03-01
|
* add news item for git-annex 6.20170301.1Gravatar Joey Hess2017-03-01
|
* add news item for git-annex 6.20170301Gravatar Joey Hess2017-03-01
|
* initial whiningGravatar yarikoptic2017-03-01
|
* Added a comment: Security of P2P repo is unclearGravatar dvicory2017-02-28
|
* add news item for git-annex 6.20170228Gravatar Joey Hess2017-02-28
|
* Added a comment: RE: choosing remotes and annex-cost-commandGravatar zpeters2017-02-28
|
* better headingsGravatar Joey Hess2017-02-27
|
* larger headingsGravatar Joey Hess2017-02-27
|
* devblogGravatar Joey Hess2017-02-27
|
* inheritable annex.securehashesonlyGravatar Joey Hess2017-02-27
| | | | | | | | | | | | | | | * init: When annex.securehashesonly has been set with git-annex config, copy that value to the annex.securehashesonly git config. * config --set: As well as setting value in git-annex branch, set local gitconfig. This is needed especially for annex.securehashesonly, which is read only from local gitconfig and not the git-annex branch. doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn has the rationalle for doing it this way. There's no perfect solution; this seems to be the least-bad one. This commit was supported by the NSF-funded DataLad project.
* updateGravatar Joey Hess2017-02-27
|
* securehash matchingGravatar Joey Hess2017-02-27
| | | | | | | Added --securehash option to match files using a secure hash function, and corresponding securehash preferred content expression. This commit was sponsored by Ethan Aubin.
* make fsck check annex.securehashesonly, and new tip for working around SHA1 ↵Gravatar Joey Hess2017-02-27
| | | | | | collisions with git-annex This commit was sponsored by andrea rota.
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-02-26
|\
| * Added a commentGravatar michalrus2017-02-26
| |
| * Added a commentGravatar openmedi2017-02-25
| |
* | move thoughtsGravatar Joey Hess2017-02-25
| |
| * (no commit message)Gravatar michalrus2017-02-25
| |
* | more thoughtsGravatar Joey Hess2017-02-25
| |
| * Added a commentGravatar michalrus2017-02-25
|/
* further thoughtsGravatar Joey Hess2017-02-25
|
* devblogGravatar Joey Hess2017-02-24
|
* SHA1 collisions in key names was more exploitable than I thoughtGravatar Joey Hess2017-02-24
| | | | | | | | | | | | Yesterday's SHA1 collision attack could be used to generate eg: SHA256-sfoo--whatever.good SHA256-sfoo--whatever.bad Such that they collide. A repository with the good one could have the bad one swapped in and signed commits would still verify. I've already mitigated this.
* updateGravatar Joey Hess2017-02-24
|