Marcus Tang--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/8e275508-f346-4453-b13f-8d1cf4a87f87n%40googlegroups.com.
On 10 Aug 2020, at 22:59, Nasser Grainawi <nas...@codeaurora.org> wrote:
On Aug 9, 2020, at 9:21 PM, 唐木村 <tmc...@gmail.com> wrote:Dear Gerrit maintainerwe often need provide external user to browse gerrit website, and config ACL for this external userand ACL problem is that if the external user “get“ internal user account username and password, the the external also get internal permissioni know it is NOT gerrit problem, it is common account leak problemBUT whether gerrit can support iplist bind account ??? because generally external user also by allow iplist to access gerrit, the ip is constraint conditionALSO, any other method can restrict login account by iplist ???for example, gitlab can support ipI don’t know of any way to restrict access by IP in Gerrit’s ACLs. I would guess there are others interested in such a feature though. Create an issue? https://www.gerritcodereview.com/issues.html
Marcus Tang--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/8e275508-f346-4453-b13f-8d1cf4a87f87n%40googlegroups.com.--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/ECE365C0-80CE-4D1E-8642-2CB0BA8BF609%40codeaurora.org.
On Aug 10, 2020, at 4:03 PM, Luca Milanesio <luca.mi...@gmail.com> wrote:On 10 Aug 2020, at 22:59, Nasser Grainawi <nas...@codeaurora.org> wrote:
On Aug 9, 2020, at 9:21 PM, 唐木村 <tmc...@gmail.com> wrote:Dear Gerrit maintainerwe often need provide external user to browse gerrit website, and config ACL for this external userand ACL problem is that if the external user “get“ internal user account username and password, the the external also get internal permissioni know it is NOT gerrit problem, it is common account leak problemBUT whether gerrit can support iplist bind account ??? because generally external user also by allow iplist to access gerrit, the ip is constraint conditionALSO, any other method can restrict login account by iplist ???for example, gitlab can support ipI don’t know of any way to restrict access by IP in Gerrit’s ACLs. I would guess there are others interested in such a feature though. Create an issue? https://www.gerritcodereview.com/issues.htmlI did something similar by implementing a permission backend and using the incoming request HTTP headers to restrict the visibility.I believe it could be done by using the source-ip also.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/8F4DB6F9-5AE2-4CCB-ABC9-FBE9E39D3040%40gmail.com.
On 10 Aug 2020, at 23:07, Nasser Grainawi <nas...@codeaurora.org> wrote:
On Aug 10, 2020, at 4:03 PM, Luca Milanesio <luca.mi...@gmail.com> wrote:On 10 Aug 2020, at 22:59, Nasser Grainawi <nas...@codeaurora.org> wrote:
On Aug 9, 2020, at 9:21 PM, 唐木村 <tmc...@gmail.com> wrote:Dear Gerrit maintainerwe often need provide external user to browse gerrit website, and config ACL for this external userand ACL problem is that if the external user “get“ internal user account username and password, the the external also get internal permissioni know it is NOT gerrit problem, it is common account leak problemBUT whether gerrit can support iplist bind account ??? because generally external user also by allow iplist to access gerrit, the ip is constraint conditionALSO, any other method can restrict login account by iplist ???for example, gitlab can support ipI don’t know of any way to restrict access by IP in Gerrit’s ACLs. I would guess there are others interested in such a feature though. Create an issue? https://www.gerritcodereview.com/issues.htmlI did something similar by implementing a permission backend and using the incoming request HTTP headers to restrict the visibility.I believe it could be done by using the source-ip also.That probably only works for HTTP(S) access though, correct?
Could it be made to work for SSH too?