repo.gc - potentially insecure hash functions not allowed
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
#### Version information:
0.4.14
#### Type:
Bug
#### Description:
Low priority but I can't gc if I have a "insecure" hash:
```
$ ipfs repo gc
Error: "potentially insecure hash functions not allowed"
Please run 'ipfs pin verify' to list insecure hashes. If you want to read them, please downgrade your go-ipfs to 0.4.13
; garbage collection aborted: could not retrieve some links
```
```
$ ipfs pin verify
zDvnoLvmiom broken
zDvnoLvmiom: potentially insecure hash functions not allowed
```
Contributor guide
Research direction
Start by reproducing `ipfs repo gc` on the insecure hash shown by `ipfs pin verify`, using the reported version information as context. Trace how garbage collection retrieves links and handles the "potentially insecure hash functions not allowed" error; done should mean the intended garbage-collection behavior is verified by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100