2019 14:02
An: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
Betreff: Re: AW: [cmake-developers] Pushing to gitlab.kitware.org from behind a
ssl proxy
On 3/29/19 8:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> - pushing to kitware without 2FA fails
> - pushing to kitware with 2FA fails
On 3/29/19 8:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> - pushing to kitware without 2FA fails
> - pushing to kitware with 2FA fails
Try using gitlab's own deployment on "gitlab.com". If that works
then we can investigate differences.
-Brad
--
Powered by www.kitware.com
Please keep mess
nstag, 19. März 2019 13:42
An: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
Betreff: Re: [cmake-developers] Pushing to gitlab.kitware.org from behind a ssl
proxy
On 3/19/19 2:21 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> remote: HTTP Basic: Access denied
> fatal: Authentication failed fo
On 3/19/19 2:21 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> remote: HTTP Basic: Access denied
> fatal: Authentication failed for
> 'https://gitlab.kitware.com//cmake.git/'
Try creating a personal access token to use during auth instead:
* https://gitlab.kitware.com/help/user/profile/personal_acc
Hello CMake developers,
It's been some time now and I have tried everything that came into my mind (and
I found on google), but I found no way to push any changes on my CMake fork.
My situation: I am behind a corporate firewall which proxies/breaks all ssl
connections and ssh is blocked complet
