René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Github token is leaked when used as a part of remote URL","articleBody":"Github [allows](https://github.blog/2012-09-21-easier-builds-and-deployments-using-git-over-https-and-oauth/) usage of personal access tokens with remote URLs in the format:\r\n\r\n```\r\nhttps://\u003ctoken\u003e@github.com/owner/repo.git\r\n```\r\nor\r\n```\r\nhttps://\u003ctoken\u003e:x-oauth-basic@github.com/owner/repo.git\r\n```\r\n\r\nIf such URL is used with `Remote`, if some error related to the access happens, it (in the example below token is `foobar`) can be leaked via exception message, like the following:\r\n\r\n```\r\nTraceback (most recent call last):\r\n  File \"start.py\", line 119, in \u003cmodule\u003e\r\n    sys.exit(run_main())\r\n    ...\r\ngit.exc.GitCommandError: Cmd('git') failed due to: exit code(128)\r\n  cmdline: git push --set-upstream --force ....\r\n  stderr: 'remote: some error.\r\nfatal: unable to access 'https://foobar:x-oauth-basic@github.com/FooBarCorp/some-repo/': The requested URL returned error: 403'\r\n```\r\n\r\nIt would be nice to have internal mechanism to prevent such leakage.","author":{"url":"https://github.com/0xnm","@type":"Person","name":"0xnm"},"datePublished":"2021-07-05T09:53:20.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/1284/GitPython/issues/1284"}