Slackware: 2020-105-01: git Security Update

    Date 14 Apr 2020
    188
    Posted By LinuxSecurity Advisories
    New git packages are available for Slackware 14.0, 14.1, 14.2, and -current to fix security issues.
    
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    
    [slackware-security]  git (SSA:2020-105-01)
    
    New git packages are available for Slackware 14.0, 14.1, 14.2, and -current to
    fix security issues.
    
    
    Here are the details from the Slackware 14.2 ChangeLog:
    +--------------------------+
    patches/packages/git-2.17.4-i586-1_slack14.2.txz:  Upgraded.
      This update fixes a security issue:
      With a crafted URL that contains a newline in it, the credential helper
      machinery can be fooled to give credential information for a wrong host.
      The attack has been made impossible by forbidding a newline character in
      any value passed via the credential protocol. Credit for finding the
      vulnerability goes to Felix Wilhelm of Google Project Zero.
      For more information, see:
        https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5260
      (* Security fix *)
    +--------------------------+
    
    
    Where to find the new packages:
    +-----------------------------+
    
    Thanks to the friendly folks at the OSU Open Source Lab
    (https://osuosl.org) for donating FTP and rsync hosting
    to the Slackware project!  :-)
    
    Also see the "Get Slack" section on https://slackware.com for
    additional mirror sites near you.
    
    Updated package for Slackware 14.0:
    ftp://ftp.slackware.com/pub/slackware/slackware-14.0/patches/packages/git-2.17.4-i486-1_slack14.0.txz
    
    Updated package for Slackware x86_64 14.0:
    ftp://ftp.slackware.com/pub/slackware/slackware64-14.0/patches/packages/git-2.17.4-x86_64-1_slack14.0.txz
    
    Updated package for Slackware 14.1:
    ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/git-2.17.4-i486-1_slack14.1.txz
    
    Updated package for Slackware x86_64 14.1:
    ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/git-2.17.4-x86_64-1_slack14.1.txz
    
    Updated package for Slackware 14.2:
    ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/git-2.17.4-i586-1_slack14.2.txz
    
    Updated package for Slackware x86_64 14.2:
    ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/git-2.17.4-x86_64-1_slack14.2.txz
    
    Updated package for Slackware -current:
    ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/d/git-2.26.1-i586-1.txz
    
    Updated package for Slackware x86_64 -current:
    ftp://ftp.slackware.com/pub/slackware/slackware64-current/slackware64/d/git-2.26.1-x86_64-1.txz
    
    
    MD5 signatures:
    +-------------+
    
    Slackware 14.0 package:
    d4df6c5651885a0c54c9060b809f7933  git-2.17.4-i486-1_slack14.0.txz
    
    Slackware x86_64 14.0 package:
    153d1609e59015641a77e872bc6bf192  git-2.17.4-x86_64-1_slack14.0.txz
    
    Slackware 14.1 package:
    c446d4c48b7c2184bb923496f135a53b  git-2.17.4-i486-1_slack14.1.txz
    
    Slackware x86_64 14.1 package:
    22d67ae1bcb09089799d02bf08106d5b  git-2.17.4-x86_64-1_slack14.1.txz
    
    Slackware 14.2 package:
    5eb04182f95e73ff27bdef3d2aa29afb  git-2.17.4-i586-1_slack14.2.txz
    
    Slackware x86_64 14.2 package:
    44dffc40138f48c49f6e1c7dc07eb3cf  git-2.17.4-x86_64-1_slack14.2.txz
    
    Slackware -current package:
    32c297677f194cfe5ee513ba4618a661  d/git-2.26.1-i586-1.txz
    
    Slackware x86_64 -current package:
    d911b45dfe08bc8ff139d4c10ee1618e  d/git-2.26.1-x86_64-1.txz
    
    
    Installation instructions:
    +------------------------+
    
    Upgrade the package as root:
    # upgradepkg git-2.17.4-i586-1_slack14.2.txz
    
    
    +-----+
    

    LinuxSecurity Poll

    How do you feel about the elimination of the terms 'blacklist' and 'slave' from the Linux kernel?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    /main-polls/32-how-do-you-feel-about-the-elimination-of-the-terms-blacklist-and-slave-from-the-linux-kernel?task=poll.vote&format=json
    32
    radio
    [{"id":"112","title":"I strongly support this change - racially charged language should not be used in the code and documentation of the kernel and other open-source projects.","votes":"3","type":"x","order":"1","pct":42.86,"resources":[]},{"id":"113","title":"I'm indifferent - this small change will not affect broader issues of racial insensitivity and white privilege.","votes":"2","type":"x","order":"2","pct":28.57,"resources":[]},{"id":"114","title":"I'm opposed to this change - there is no need to change language that has been used for years. It doesn't make sense for people to take offense to terminology used in community projects.","votes":"2","type":"x","order":"3","pct":28.57,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.