summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| | * poll vote (My phone (or MP3 player))Gravatar 14.203.223.702015-12-16
| |/
| * Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-12-15
| |\
| * | bring back some deleted functions that git-repair usesGravatar Joey Hess2015-12-15
| | |
| * | improve temp dir securityGravatar Joey Hess2015-12-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://bugs.debian.org/807341 * Fix insecure temporary permissions when git-annex repair is used in in a corrupted git repository. Other calls to withTmpDir didn't leak any potentially private data, but repair clones the git repository to a temp directory which is made using the user's umask. Thus, it might expose a git repo that is otherwise locked down. * Fix potential denial of service attack when creating temp dirs. Since withTmpDir used easily predictable temporary directory names, an attacker could create foo.0, foo.1, etc and as long as it managed to keep ahead of it, could prevent it from ever returning. I'd rate this as a low utility DOS attack. Most attackers in a position to do this could just fill up the disk /tmp is on to prevent anything from writing temp files. And few parts of git-annex use withTmpDir anyway, so DOS potential is quite low. Examined all callers of withTmpDir and satisfied myself that switching to mkdtmp and so getting a mode 700 temp dir wouldn't break any of them. Note that withTmpDirIn continues to not force temp dir to 700. But it's only used for temp directories inside .git/annex/wherever/ so that is not a problem. Also re-audited all other uses of temp files and dirs in git-annex.
* | | starting to work on test suite for v6Gravatar Joey Hess2015-12-15
| | |
* | | Use git-annex init --version=6 to get v6 for nowGravatar Joey Hess2015-12-15
| | | | | | | | | | | | | | | Not ready to make it default because of the direct mode upgrade needing to all happen at once.
* | | in v6 mode, unannex does not interact badly with pre-commit hookGravatar Joey Hess2015-12-15
| | | | | | | | | | | | So can be used in a tree with staged changes, no problems. Much nicer.
* | | recent fsck changes caused ugly message when object was not presentGravatar Joey Hess2015-12-15
| | |
* | | update todo listGravatar Joey Hess2015-12-15
| | |
* | | implemented upgrade of direct mode repo to v6Gravatar Joey Hess2015-12-15
| | |
* | | reorgGravatar Joey Hess2015-12-15
| | |
* | | changes for v6 broke fsck in direct modeGravatar Joey Hess2015-12-15
| | |
* | | clarifyGravatar Joey Hess2015-12-15
| | |
* | | doc updateGravatar Joey Hess2015-12-15
| | |
* | | add: In v6 mode, acts on modified files.Gravatar Joey Hess2015-12-15
| | | | | | | | | | | | | | | Same as was done in direct mode, except in v6 mode add always adds files locked, so
* | | fix incorrect doc changeGravatar Joey Hess2015-12-15
| | |
* | | avoid pre-commit check having to do with v5 unlocked files when in v6 modeGravatar Joey Hess2015-12-15
| | |
* | | rename stuff for v5 unlocked files to indicate it's oldGravatar Joey Hess2015-12-15
| | |
* | | update doc for v6Gravatar Joey Hess2015-12-15
| | |
* | | add: no need to make pass for old unlocked files in v6Gravatar Joey Hess2015-12-15
| | |
* | | have clean filter check if the filename was already in use by an old keyGravatar Joey Hess2015-12-15
| | | | | | | | | | | | | | | | | | | | | | | | The annex object for it may have been modified due to hard link, and that should be cleaned up when the new version is added. If another associated file has the old key's content, that's linked into the annex object. Otherwise, update location log to reflect that content has been lost.
* | | add getAssociatedKeyGravatar Joey Hess2015-12-15
| | | | | | | | | | | | | | | I guess this is just as efficient as the getAssociatedFiles query, but I have not tried to optimise the database yet.
* | | update inode cache to cover file even when nothing needs to be done to linkAnnexGravatar Joey Hess2015-12-15
| | | | | | | | | | | | | | | | | | This covers the case where multiple files have the same content and are added with git add. Previously only the one that was linked to the annex got its inode cached; now both are.
* | | todoGravatar Joey Hess2015-12-15
| | |
* | | Merge branch 'master' into smudgeGravatar Joey Hess2015-12-15
|\| |
| | * removedGravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-12-14
| | |
| | * Added a commentGravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-12-14
| | |
| | * Added a commentGravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-12-14
| | |
| | * Added a comment: It workedGravatar https://me.yahoo.com/a/ZF7p46cPmpWtb9zvA8iTitPmiQ--#eb0142015-12-14
| | |
| | * Added a comment: I'm also having this issueGravatar https://me.yahoo.com/a/ZF7p46cPmpWtb9zvA8iTitPmiQ--#eb0142015-12-14
| | |
| | * Added a commentGravatar yminus2015-12-13
| | |
| | * Added a comment: IndeedGravatar scorchgeek2015-12-13
| | |
| | * Added a commentGravatar basak2015-12-13
| | |
| | * Added a comment: Repairing ignores disk space issues tooGravatar joakim.hovlandsvag@ad788ffa13d1ccbf03f2c485653900f8baa339502015-12-13
| | |
| | * (no commit message)Gravatar joakim.hovlandsvag@ad788ffa13d1ccbf03f2c485653900f8baa339502015-12-13
| | |
| | * create pageGravatar scorchgeek2015-12-12
| | |
| * | Debian: Build depend on concurrent-output.Gravatar Joey Hess2015-12-12
| | | | | | | | | | | | In unstable now.
| | * Added a commentGravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-12-12
| | |
| | * Added a commentGravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-12-12
| | |
| | * Added a commentGravatar https://openid.stackexchange.com/user/27ceb3c5-0762-42b8-8f8a-ed21c284748f2015-12-11
| |/
* | avoid smudge filter returning invalid contentGravatar Joey Hess2015-12-11
| | | | | | | | | | | | | | | | | | | | | | | | 1. git add file 2. git commit 3. modify file 4. git commit 5. git reset HEAD^ Before this fix, that resulted in git saying the file was modified. And indeed, it didn't have the content it should in the just checked out ref, because step 3 modified the object file for the old key.
| * 2 more data -> 2 more daysGravatar http://www.ryantm.com/2015-12-11
| |
| * devblogGravatar Joey Hess2015-12-11
| |
* | updateGravatar Joey Hess2015-12-11
| |
* | checked getKeysPresent; it's ok for v6 unlocked filesGravatar Joey Hess2015-12-11
| | | | | | | | | | | | When a v6 unlocked files is removed from the work tree, unused doesn't show it. When it gets removed from the index, unused does show it. This is the same as a locked file.
* | fsck for v6 unlocked filesGravatar Joey Hess2015-12-11
| | | | | | | | | | | | | | | | This only adds 1 stat to each file fscked for locked files, so added overhead is minimal. For unlocked files it has to access the database to see if a file is modified.
* | finish v6 git-annex lockGravatar Joey Hess2015-12-11
| | | | | | | | This was a doozy!
* | only make 1 hardlink max between pointer file and annex objectGravatar Joey Hess2015-12-11
| | | | | | | | | | | | | | If multiple files point to the same annex object, the user may want to modify them independently, so don't use a hard link. Also, check diskreserve when copying.
* | Merge branch 'master' into smudgeGravatar Joey Hess2015-12-11
|\|
| * fsck: Failed to honor annex.diskreserve when checking a remote.Gravatar Joey Hess2015-12-11
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-28 23:14:30 +0000