GitHub PushEvent at 2014-09-05 15:24:41
Repository: cargo
Actor: bors
Payload: {"shas":[["219f9902c9fa8016934b2617506e66f671277534","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Implement git authentication\n\nThis commit updates git2-rs to get the implementation of the authentication\ncallback in libgit2. Additionally this specifies the callback for whenever we're\ncloning into the database or updating submodules.\n\nCurrently cargo will *not* ask for user input, but rather require you to have\nauthentication configured in git through some other means. There are currently\ntwo primary methods of doing so:\n\n1. Any SSH key in the local ssh-agent will be used for authentication with SSH\n   repositories.\n2. The `credential.helper` interface (as specified by gitcredential(7)) has been\n   implemented in git2-rs to allow for picking up of storage of passwords in the\n   local git cache or keychain.\n\nIf these two methods fail, then there will likely be an authentication failure.\nInteractive prompts for authentication have not been implemented as there is no\nmethod to currently enter your password into the terminal silently.\n\nA consequence of this commit is that cargo now depends on libssh2. A package was\ncreated to create a static copy of libssh2, and this is now linked into cargo by\ndefault.\n\nIt turned out that just building libssh2 was quite a beast in and of itself on\nwindows. The primary stickler point is that on the current release, 1.4.3,\nlibssh2 requires openssl on windows. At this time I don't want to pick up a\ndependency on openssl for windows, and it turned out that the unreleased 1.4.4\nversion has a new backend for windows not based on openssl, but rather windows's\ncryptography API.\n\nThe current bundled version of libssh2 is 1.4.4 with some light modifications to\nactually build on windows (wow that was hard). All in all, we're now statically\nlinking to libssh 1.4.4 (not a runtime dependency).\n\nCloses #493","Alex Crichton",true],["76f19a64d7120d85f15d3939ac13f200b12f48fb","3a2c29237f73c7cf88424b80e427b1884f346b35@rust-lang.org","auto merge of #503 : alexcrichton/cargo/issue-493, r=brson\n\nThis commit updates git2-rs to get the implementation of the authentication\r\ncallback in libgit2. Additionally this specifies the callback for whenever we're\r\ncloning into the database or updating submodules.\r\n\r\nCurrently cargo will *not* ask for user input, but rather require you to have\r\nauthentication configured in git through some other means. There are currently\r\ntwo primary methods of doing so:\r\n\r\n1. Any SSH key in the local ssh-agent will be used for authentication with SSH\r\n   repositories.\r\n2. The `credential.helper` interface (as specified by gitcredential(7)) has been\r\n   implemented in git2-rs to allow for picking up of storage of passwords in the\r\n   local git cache or keychain.\r\n\r\nIf these two methods fail, then there will likely be an authentication failure.\r\nInteractive prompts for authentication have not been implemented as there is no\r\nmethod to currently enter your password into the terminal silently.\r\n\r\nA consequence of this commit is that cargo now depends on libssh2. A package was\r\ncreated to create a static copy of libssh2, and this is now linked into cargo by\r\ndefault.\r\n\r\nIt turned out that just building libssh2 was quite a beast in and of itself on\r\nwindows. The primary stickler point is that on the current release, 1.4.3,\r\nlibssh2 requires openssl on windows. At this time I don't want to pick up a\r\ndependency on openssl for windows, and it turned out that the unreleased 1.4.4\r\nversion has a new backend for windows not based on openssl, but rather windows's\r\ncryptography API.\r\n\r\nThe current bundled version of libssh2 is 1.4.4 with some light modifications to\r\nactually build on windows (wow that was hard). All in all, we're now statically\r\nlinking to libssh 1.4.4 (not a runtime dependency).\r\n\r\nCloses #493","bors",true]],"size":2,"ref":"refs/heads/auto-cargo","head":"76f19a64d7120d85f15d3939ac13f200b12f48fb"}