Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update: add --submodule-init-config option
This option is necessary in some edge cases (including west's own test suite) to work around new git behavior discussed in: https://github.blog/2022-10-18-git-security-vulnerabilities-announced/#cve-2022-39253 Since 'west update' uses 'git submodule update --init --recursive' to clone submodules, users may run into problems in (likely rare) situations where they are updating a submodule from a "remote" repository which is actually a file on the local host with symlinks under .git. In this case, the 'west update' will fail because the file protocol is disallowed at the 'git submodule update' step. We don't want to force users (including our own test suite...) to allow this protocol globally, since upstream git is telling us that is a security problem. But we do want to allow that protocol to be enabled on a case-by-case basis within west when the repository is known not to be malicious. This option allows us to do exactly that by running: west update --submodule-init-config protocol.file.allow=always ... Fixes: #619 Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
- Loading branch information