2011-10-15 21:47:03 +00:00
|
|
|
{- git-annex uuids
|
|
|
|
-
|
|
|
|
- Each git repository used by git-annex has an annex.uuid setting that
|
|
|
|
- uniquely identifies that repository.
|
|
|
|
-
|
|
|
|
- UUIDs of remotes are cached in git config, using keys named
|
|
|
|
- remote.<name>.annex-uuid
|
|
|
|
-
|
instantiate remotes that are behind a proxy remote
Untested, but this should be close to working. The proxied remotes have
the same url but a different uuid. When talking to current
git-annex-shell, it will fail due to a uuid mismatch. Once it supports
proxies, it will know that the presented uuid is for a remote that it
proxies for.
The check for any git config settings for a remote with the same name as
the proxied remote is there for several reasons. One is security:
Writing a name to the proxy log should not cause changes to
how an existing, configured git remote operates in a different clone of
the repo.
It's possible that the user has been using a proxied remote, and decides
to set a git config for it. We can't tell the difference between that
scenario and an evil remote trying to eg, intercept a file upload
by replacing their remote with a proxied remote.
Also, if the user sets some git config, does it override the config
inherited from the proxy remote? Seems a difficult question. Luckily,
the above means we don't need to think through it.
This does mean though, that in order for a user to change the config of
a proxy remote, they have to manually set its annex-uuid and url, as
well as the config they want to change. They may also have to set any of
the inherited configs that they were relying on.
2024-06-06 21:15:32 +00:00
|
|
|
- Copyright 2010-2024 Joey Hess <id@joeyh.name>
|
2011-10-15 21:47:03 +00:00
|
|
|
-
|
2019-03-13 19:48:14 +00:00
|
|
|
- Licensed under the GNU AGPL version 3 or higher.
|
2011-10-15 21:47:03 +00:00
|
|
|
-}
|
|
|
|
|
2019-11-27 20:54:11 +00:00
|
|
|
{-# LANGUAGE OverloadedStrings #-}
|
|
|
|
|
2011-10-15 21:47:03 +00:00
|
|
|
module Annex.UUID (
|
2019-12-02 14:57:09 +00:00
|
|
|
configkeyUUID,
|
instantiate remotes that are behind a proxy remote
Untested, but this should be close to working. The proxied remotes have
the same url but a different uuid. When talking to current
git-annex-shell, it will fail due to a uuid mismatch. Once it supports
proxies, it will know that the presented uuid is for a remote that it
proxies for.
The check for any git config settings for a remote with the same name as
the proxied remote is there for several reasons. One is security:
Writing a name to the proxy log should not cause changes to
how an existing, configured git remote operates in a different clone of
the repo.
It's possible that the user has been using a proxied remote, and decides
to set a git config for it. We can't tell the difference between that
scenario and an evil remote trying to eg, intercept a file upload
by replacing their remote with a proxied remote.
Also, if the user sets some git config, does it override the config
inherited from the proxy remote? Seems a difficult question. Luckily,
the above means we don't need to think through it.
This does mean though, that in order for a user to change the config of
a proxy remote, they have to manually set its annex-uuid and url, as
well as the config they want to change. They may also have to set any of
the inherited configs that they were relying on.
2024-06-06 21:15:32 +00:00
|
|
|
configRepoUUID,
|
2011-10-15 21:47:03 +00:00
|
|
|
getUUID,
|
|
|
|
getRepoUUID,
|
|
|
|
getUncachedUUID,
|
2015-10-15 19:28:29 +00:00
|
|
|
isUUIDConfigured,
|
2011-10-15 21:47:03 +00:00
|
|
|
prepUUID,
|
2012-04-27 16:21:38 +00:00
|
|
|
genUUID,
|
2013-09-05 20:02:39 +00:00
|
|
|
genUUIDInNameSpace,
|
|
|
|
gCryptNameSpace,
|
2012-04-27 16:21:38 +00:00
|
|
|
removeRepoUUID,
|
2012-11-05 21:43:17 +00:00
|
|
|
storeUUID,
|
2014-04-16 00:13:35 +00:00
|
|
|
storeUUIDIn,
|
2013-09-05 20:02:39 +00:00
|
|
|
setUUID,
|
2014-12-17 17:57:52 +00:00
|
|
|
webUUID,
|
|
|
|
bitTorrentUUID,
|
2011-10-15 21:47:03 +00:00
|
|
|
) where
|
|
|
|
|
2016-01-20 20:36:33 +00:00
|
|
|
import Annex.Common
|
2016-01-20 20:55:06 +00:00
|
|
|
import qualified Annex
|
2011-10-15 21:47:03 +00:00
|
|
|
import qualified Git
|
2011-12-13 19:05:07 +00:00
|
|
|
import qualified Git.Config
|
2019-12-02 14:57:09 +00:00
|
|
|
import Git.Types
|
2011-10-15 21:47:03 +00:00
|
|
|
import Config
|
|
|
|
|
2013-02-10 18:52:54 +00:00
|
|
|
import qualified Data.UUID as U
|
2016-07-27 11:38:11 +00:00
|
|
|
import qualified Data.UUID.V4 as U4
|
2013-09-05 20:02:39 +00:00
|
|
|
import qualified Data.UUID.V5 as U5
|
2023-10-26 17:12:57 +00:00
|
|
|
import qualified Data.ByteString as S
|
2019-01-01 17:49:19 +00:00
|
|
|
import Data.String
|
2013-02-10 18:52:54 +00:00
|
|
|
|
2019-12-02 14:57:09 +00:00
|
|
|
configkeyUUID :: ConfigKey
|
|
|
|
configkeyUUID = annexConfig "uuid"
|
2011-10-15 21:47:03 +00:00
|
|
|
|
instantiate remotes that are behind a proxy remote
Untested, but this should be close to working. The proxied remotes have
the same url but a different uuid. When talking to current
git-annex-shell, it will fail due to a uuid mismatch. Once it supports
proxies, it will know that the presented uuid is for a remote that it
proxies for.
The check for any git config settings for a remote with the same name as
the proxied remote is there for several reasons. One is security:
Writing a name to the proxy log should not cause changes to
how an existing, configured git remote operates in a different clone of
the repo.
It's possible that the user has been using a proxied remote, and decides
to set a git config for it. We can't tell the difference between that
scenario and an evil remote trying to eg, intercept a file upload
by replacing their remote with a proxied remote.
Also, if the user sets some git config, does it override the config
inherited from the proxy remote? Seems a difficult question. Luckily,
the above means we don't need to think through it.
This does mean though, that in order for a user to change the config of
a proxy remote, they have to manually set its annex-uuid and url, as
well as the config they want to change. They may also have to set any of
the inherited configs that they were relying on.
2024-06-06 21:15:32 +00:00
|
|
|
configRepoUUID :: Git.Repo -> ConfigKey
|
|
|
|
configRepoUUID r = remoteAnnexConfig r "uuid"
|
|
|
|
|
2013-02-10 18:52:54 +00:00
|
|
|
{- Generates a random UUID, that does not include the MAC address. -}
|
2011-10-15 21:47:03 +00:00
|
|
|
genUUID :: IO UUID
|
2019-01-01 17:49:19 +00:00
|
|
|
genUUID = toUUID <$> U4.nextRandom
|
2011-10-15 21:47:03 +00:00
|
|
|
|
2013-09-05 20:02:39 +00:00
|
|
|
{- Generates a UUID from a given string, using a namespace.
|
|
|
|
- Given the same namespace, the same string will always result
|
|
|
|
- in the same UUID. -}
|
2023-10-26 17:12:57 +00:00
|
|
|
genUUIDInNameSpace :: U.UUID -> S.ByteString -> UUID
|
|
|
|
genUUIDInNameSpace namespace = toUUID . U5.generateNamed namespace . S.unpack
|
2013-09-05 20:02:39 +00:00
|
|
|
|
|
|
|
{- Namespace used for UUIDs derived from git-remote-gcrypt ids. -}
|
|
|
|
gCryptNameSpace :: U.UUID
|
|
|
|
gCryptNameSpace = U5.generateNamed U5.namespaceURL $
|
2023-10-26 17:12:57 +00:00
|
|
|
S.unpack "http://git-annex.branchable.com/design/gcrypt/"
|
2013-09-05 20:02:39 +00:00
|
|
|
|
2011-11-19 19:40:40 +00:00
|
|
|
{- Get current repository's UUID. -}
|
2011-10-15 21:47:03 +00:00
|
|
|
getUUID :: Annex UUID
|
2016-01-20 20:55:06 +00:00
|
|
|
getUUID = annexUUID <$> Annex.getGitConfig
|
2011-10-15 21:47:03 +00:00
|
|
|
|
2016-01-20 20:55:06 +00:00
|
|
|
{- Looks up a remote repo's UUID, caching it in .git/config if
|
|
|
|
- it's not already. -}
|
2011-10-15 21:47:03 +00:00
|
|
|
getRepoUUID :: Git.Repo -> Annex UUID
|
|
|
|
getRepoUUID r = do
|
2012-03-22 04:23:15 +00:00
|
|
|
c <- toUUID <$> getConfig cachekey ""
|
2011-10-15 21:47:03 +00:00
|
|
|
let u = getUncachedUUID r
|
|
|
|
|
2011-11-07 18:46:01 +00:00
|
|
|
if c /= u && u /= NoUUID
|
2011-10-15 21:47:03 +00:00
|
|
|
then do
|
2011-11-08 19:34:10 +00:00
|
|
|
updatecache u
|
2011-10-15 21:47:03 +00:00
|
|
|
return u
|
|
|
|
else return c
|
2012-12-13 04:24:19 +00:00
|
|
|
where
|
|
|
|
updatecache u = do
|
|
|
|
g <- gitRepo
|
2014-04-16 00:13:35 +00:00
|
|
|
when (g /= r) $ storeUUIDIn cachekey u
|
instantiate remotes that are behind a proxy remote
Untested, but this should be close to working. The proxied remotes have
the same url but a different uuid. When talking to current
git-annex-shell, it will fail due to a uuid mismatch. Once it supports
proxies, it will know that the presented uuid is for a remote that it
proxies for.
The check for any git config settings for a remote with the same name as
the proxied remote is there for several reasons. One is security:
Writing a name to the proxy log should not cause changes to
how an existing, configured git remote operates in a different clone of
the repo.
It's possible that the user has been using a proxied remote, and decides
to set a git config for it. We can't tell the difference between that
scenario and an evil remote trying to eg, intercept a file upload
by replacing their remote with a proxied remote.
Also, if the user sets some git config, does it override the config
inherited from the proxy remote? Seems a difficult question. Luckily,
the above means we don't need to think through it.
This does mean though, that in order for a user to change the config of
a proxy remote, they have to manually set its annex-uuid and url, as
well as the config they want to change. They may also have to set any of
the inherited configs that they were relying on.
2024-06-06 21:15:32 +00:00
|
|
|
cachekey = configRepoUUID r
|
2011-10-15 21:47:03 +00:00
|
|
|
|
2012-04-27 16:21:38 +00:00
|
|
|
removeRepoUUID :: Annex ()
|
2016-01-20 20:55:06 +00:00
|
|
|
removeRepoUUID = do
|
2019-12-02 14:57:09 +00:00
|
|
|
unsetConfig configkeyUUID
|
2016-01-20 20:55:06 +00:00
|
|
|
storeUUID NoUUID
|
2012-04-27 16:21:38 +00:00
|
|
|
|
2011-10-15 21:47:03 +00:00
|
|
|
getUncachedUUID :: Git.Repo -> UUID
|
2019-12-02 14:57:09 +00:00
|
|
|
getUncachedUUID = toUUID . Git.Config.get configkeyUUID ""
|
2011-10-15 21:47:03 +00:00
|
|
|
|
2015-10-15 19:28:29 +00:00
|
|
|
-- Does the repo's config have a key for the UUID?
|
|
|
|
-- True even when the key has no value.
|
|
|
|
isUUIDConfigured :: Git.Repo -> Bool
|
2019-12-02 14:57:09 +00:00
|
|
|
isUUIDConfigured = isJust . Git.Config.getMaybe configkeyUUID
|
2015-10-15 19:28:29 +00:00
|
|
|
|
2011-10-15 21:47:03 +00:00
|
|
|
{- Make sure that the repo has an annex.uuid setting. -}
|
|
|
|
prepUUID :: Annex ()
|
2011-11-07 18:46:01 +00:00
|
|
|
prepUUID = whenM ((==) NoUUID <$> getUUID) $
|
2014-04-16 00:13:35 +00:00
|
|
|
storeUUID =<< liftIO genUUID
|
2011-11-07 18:46:01 +00:00
|
|
|
|
2014-04-16 00:13:35 +00:00
|
|
|
storeUUID :: UUID -> Annex ()
|
rename changeGitConfig to overrideGitConfig and avoid unncessary calls
It's important that it be clear that it overrides a config, such that
reloading the git config won't change it, and in particular, setConfig
won't change it.
Most of the calls to changeGitConfig were actually after setConfig,
which was redundant and unncessary. So removed those.
The only remaining one, besides --debug, is in the handling of
repository-global config values. That one's ok, because the
way mergeGitConfig is implemented, it does not override any value that
is set in git config. If a value with a repo-global setting was passed
to setConfig, it would set it in the git config, reload the git config,
re-apply mergeGitConfig, and use the newly set value, which is the right
thing.
2020-02-27 05:06:35 +00:00
|
|
|
storeUUID = storeUUIDIn configkeyUUID
|
2014-04-16 00:13:35 +00:00
|
|
|
|
|
|
|
storeUUIDIn :: ConfigKey -> UUID -> Annex ()
|
|
|
|
storeUUIDIn configfield = setConfig configfield . fromUUID
|
2013-09-05 20:02:39 +00:00
|
|
|
|
|
|
|
{- Only sets the configkey in the Repo; does not change .git/config -}
|
|
|
|
setUUID :: Git.Repo -> UUID -> IO Git.Repo
|
|
|
|
setUUID r u = do
|
2021-08-11 00:45:02 +00:00
|
|
|
let s = encodeBS $ show configkeyUUID ++ "=" ++ fromUUID u
|
2020-04-13 17:05:41 +00:00
|
|
|
Git.Config.store s Git.Config.ConfigList r
|
2014-12-17 17:57:52 +00:00
|
|
|
|
|
|
|
-- Dummy uuid for the whole web. Do not alter.
|
|
|
|
webUUID :: UUID
|
2019-01-01 17:49:19 +00:00
|
|
|
webUUID = UUID (fromString "00000000-0000-0000-0000-000000000001")
|
2014-12-17 17:57:52 +00:00
|
|
|
|
|
|
|
-- Dummy uuid for bittorrent. Do not alter.
|
|
|
|
bitTorrentUUID :: UUID
|
2019-01-01 17:49:19 +00:00
|
|
|
bitTorrentUUID = UUID (fromString "00000000-0000-0000-0000-000000000002")
|