curben
/
urlhaus-filter
mirror of https://gitlab.com/malware-filter/urlhaus-filter
1
0
Fork 0
Code Issues Releases Wiki Activity

Update file links

curben 2018-10-17 17:12:36 +10:30
parent 7970060a20
commit a1f2af2f65
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ.md

@ -5,9 +5,11 @@
+ It doesn't show the status (online/offline) of a URL.
- Why don't you `wget top-1m.csv.zip` and output to stdout?
+ If wget fails, [top-1m.txt](src/top-1m.txt) will be empty. Output as file avoids that.
+ If wget fails, [top-1m.txt](https://gitlab.com/curben/urlhaus-filter/blob/master/src/top-1m.txt) will be empty. Output as file avoids that.
- Why do you need to clone the repo again in your CI? I thought CI already fetch the repo by default?
+ GitLab Runner clone/fetch the repo using HTTPS method by default ([log](https://gitlab.com/curben/urlhaus/-/jobs/105979394)). This method requires deploy *token* which is *read-only* (cannot push).
+ GitLab Runner clone/fetch the repo using HTTPS method by default ([log](https://gitlab.com/curben/urlhaus-filter/-/jobs/105979394)). This method requires deploy *token* which is *read-only* (cannot push).
+ Deploy *key* has write access but cannot be used with the HTTPS method, hence, the workaround to clone using SSH.
+ See issue [#20567](https://gitlab.com/gitlab-org/gitlab-ce/issues/20567) and [#20845](https://gitlab.com/gitlab-org/gitlab-ce/issues/20845).
+ Another approach is [personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) which seems HTTPS-compatible.
+ Deploy/SSH key is preferred because it can be [restricted](https://docs.gitlab.com/ce/ssh/README.html#per-repository-deploy-keys) to access one repo only, unlike personal access token which has [global](https://docs.gitlab.com/ce/ssh/README.html#global-shared-deploy-keys) access.
+ See issue [#18106](https://gitlab.com/gitlab-org/gitlab-ce/issues/18106), [#20567](https://gitlab.com/gitlab-org/gitlab-ce/issues/20567) and [#20845](https://gitlab.com/gitlab-org/gitlab-ce/issues/20845).