Hi, a late answer: I don’t think that you configure additional parameters for the git command(s) that Qt Creator uses, but since -c just (temporarily) sets a git configuration, you could configure that in either your project’s .git/config with "git config http.sslVerify false", or your user's ~/.git/config with "git config --global http.sslVerify false"
Br, Eike > Am 25/07/2022 um 23:17 schrieb Petric Frank <pfr...@gmx.de>: > > Hello, > > Am Montag, 25. Juli 2022, 13:30:24 CEST schrieb Orgad Shaneh: >> On Mon, Jul 25, 2022 at 2:25 PM Konstantin Tokarev <annu...@yandex.ru> >> >> wrote: >>>> Try to configure:git config http.sslVerify false >>> >>> This undermines whole point of using HTTPS (besides buzzword >>> compatibility). >>> Use http.sslCAInfo to verify server certificate, or use different protocol >>> like ssh or plain http. >> >> This is a server in an internal network, so MITM is very unlikely. >> >> I did not suggest to configure it globally, but only for this repository. > > The option > -c http.sslVerify=false > > passed to the git command seems to disable the check. > > But how to configure that in qtcreator ? > > regards > Petric > > > _______________________________________________ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator