Why updating from behind a proxy results in hash sum mismatch error while direct WiFi has no issues?












0














This has started from Ubuntu's 14.04 LTS version.



I work on Ubuntu at my office where internet works from behind a proxy server.



Earlier, I could just give the usual update commands from the terminal and they just worked.



But 14.04 LTS onwards, it has become exceedingly difficult to carry out even such a mundane task as updating my system.



Every time I try to update the system from behind the proxy, I get errors of 'Hash sum Mismatch'.



But interestingly (and to my utter dismay) when I connect to internet directly using my mobile phone's wifi, the update works absolutely normally.



I have tried all the workarounds suggested to alleviate the Hash Sum Mismatch errors. None has worked.



I suspect something is wrong with the way our proxy is configured. If not, I would really appreciate a good hand here.
Thanks.










share|improve this question



























    0














    This has started from Ubuntu's 14.04 LTS version.



    I work on Ubuntu at my office where internet works from behind a proxy server.



    Earlier, I could just give the usual update commands from the terminal and they just worked.



    But 14.04 LTS onwards, it has become exceedingly difficult to carry out even such a mundane task as updating my system.



    Every time I try to update the system from behind the proxy, I get errors of 'Hash sum Mismatch'.



    But interestingly (and to my utter dismay) when I connect to internet directly using my mobile phone's wifi, the update works absolutely normally.



    I have tried all the workarounds suggested to alleviate the Hash Sum Mismatch errors. None has worked.



    I suspect something is wrong with the way our proxy is configured. If not, I would really appreciate a good hand here.
    Thanks.










    share|improve this question

























      0












      0








      0







      This has started from Ubuntu's 14.04 LTS version.



      I work on Ubuntu at my office where internet works from behind a proxy server.



      Earlier, I could just give the usual update commands from the terminal and they just worked.



      But 14.04 LTS onwards, it has become exceedingly difficult to carry out even such a mundane task as updating my system.



      Every time I try to update the system from behind the proxy, I get errors of 'Hash sum Mismatch'.



      But interestingly (and to my utter dismay) when I connect to internet directly using my mobile phone's wifi, the update works absolutely normally.



      I have tried all the workarounds suggested to alleviate the Hash Sum Mismatch errors. None has worked.



      I suspect something is wrong with the way our proxy is configured. If not, I would really appreciate a good hand here.
      Thanks.










      share|improve this question













      This has started from Ubuntu's 14.04 LTS version.



      I work on Ubuntu at my office where internet works from behind a proxy server.



      Earlier, I could just give the usual update commands from the terminal and they just worked.



      But 14.04 LTS onwards, it has become exceedingly difficult to carry out even such a mundane task as updating my system.



      Every time I try to update the system from behind the proxy, I get errors of 'Hash sum Mismatch'.



      But interestingly (and to my utter dismay) when I connect to internet directly using my mobile phone's wifi, the update works absolutely normally.



      I have tried all the workarounds suggested to alleviate the Hash Sum Mismatch errors. None has worked.



      I suspect something is wrong with the way our proxy is configured. If not, I would really appreciate a good hand here.
      Thanks.







      apt updates proxy






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 21 '18 at 8:25









      Sachin Borkar

      406




      406






















          2 Answers
          2






          active

          oldest

          votes


















          0














          When running the update Debian/Ubuntu will download a list of all the meta-data about a package first, from this URL:



          http://us.archive.ubuntu.com/ubuntu/dists/bionic/main/binary-amd64/Packages.gz



          It will contain something like this for every package:



          Package: aodh-common
          Architecture: all
          Version: 6.0.0-0ubuntu1
          Priority: optional
          Section: web
          Source: aodh
          Origin: Ubuntu
          Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
          Original-Maintainer: PKG OpenStack <openstack-devel@lists.alioth.debian.org>
          Bugs: https://bugs.launchpad.net/ubuntu/+filebug
          Installed-Size: 97
          Depends: adduser, dpkg-dev, python-aodh (= 6.0.0-0ubuntu1), python:any
          Filename: pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb
          Size: 17760
          MD5sum: 8f0c651bcc7369034fea6c28653f51b9
          SHA1: 7fc8dd248a5139f0f7dd3be5a49614c1b9af7186
          SHA256: 98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e
          Homepage: https://github.com/openstack/aodh
          Description: OpenStack Telemetry (Ceilometer) Alarming - common files
          Description-md5: 4d4a9638c22eafe95e8cdbfdae651022


          For this package it will then download this URL:



          http://us.archive.ubuntu.com/ubuntu/pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb



          It will then check the SHA256 hash of this similar to doing this:



          $ sha256sum aodh-common_6.0.0-0ubuntu1_all.deb 
          98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e aodh-common_6.0.0-0ubuntu1_all.deb


          Your proxy is modifying the data which breaks the integrity hash check, because the contents have been changed. You should step through the process of running these commands manually, such as downloading the file via your browser and running sha256sum on the command line to see the hashes don't match.



          Next you should see what is actually different between the files and why. It's possible your proxy is able to determine that the .deb file is an "archive" that uses gzip compression and is re-packing the contents, even if that seems rather stupid in this context it could be used for a virus/malware scanning utility.



          Let's assume you have two .deb files, one downloaded via the broken proxy and one downloaded via a proper working connection. You can compare the two by unpacking them and running diff on the two directories to see which files (if any) are different. If the diff outputs no differences, then it's likely the proxy is repacking. If the diff outputs something inspect what the differences are and why your proxy is making such changes as it's likely a security concern in addition to a usability problem.






          share|improve this answer

















          • 1




            That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
            – Sachin Borkar
            Dec 21 '18 at 9:04










          • OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
            – Sachin Borkar
            Dec 21 '18 at 11:29












          • There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
            – Kristopher Ives
            Dec 21 '18 at 15:24



















          -1














          Maybe check your source list



          sudo rm -rf /var/lib/apt/lists/*


          then:



          sudo apt-get update


          Do you get the same error without connecting with proxy? try closing may be configured incorrectly






          share|improve this answer

















          • 1




            Been there, done that. No use. Thanks for taking time to help though.
            – Sachin Borkar
            Dec 21 '18 at 8:40











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1103529%2fwhy-updating-from-behind-a-proxy-results-in-hash-sum-mismatch-error-while-direct%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          When running the update Debian/Ubuntu will download a list of all the meta-data about a package first, from this URL:



          http://us.archive.ubuntu.com/ubuntu/dists/bionic/main/binary-amd64/Packages.gz



          It will contain something like this for every package:



          Package: aodh-common
          Architecture: all
          Version: 6.0.0-0ubuntu1
          Priority: optional
          Section: web
          Source: aodh
          Origin: Ubuntu
          Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
          Original-Maintainer: PKG OpenStack <openstack-devel@lists.alioth.debian.org>
          Bugs: https://bugs.launchpad.net/ubuntu/+filebug
          Installed-Size: 97
          Depends: adduser, dpkg-dev, python-aodh (= 6.0.0-0ubuntu1), python:any
          Filename: pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb
          Size: 17760
          MD5sum: 8f0c651bcc7369034fea6c28653f51b9
          SHA1: 7fc8dd248a5139f0f7dd3be5a49614c1b9af7186
          SHA256: 98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e
          Homepage: https://github.com/openstack/aodh
          Description: OpenStack Telemetry (Ceilometer) Alarming - common files
          Description-md5: 4d4a9638c22eafe95e8cdbfdae651022


          For this package it will then download this URL:



          http://us.archive.ubuntu.com/ubuntu/pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb



          It will then check the SHA256 hash of this similar to doing this:



          $ sha256sum aodh-common_6.0.0-0ubuntu1_all.deb 
          98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e aodh-common_6.0.0-0ubuntu1_all.deb


          Your proxy is modifying the data which breaks the integrity hash check, because the contents have been changed. You should step through the process of running these commands manually, such as downloading the file via your browser and running sha256sum on the command line to see the hashes don't match.



          Next you should see what is actually different between the files and why. It's possible your proxy is able to determine that the .deb file is an "archive" that uses gzip compression and is re-packing the contents, even if that seems rather stupid in this context it could be used for a virus/malware scanning utility.



          Let's assume you have two .deb files, one downloaded via the broken proxy and one downloaded via a proper working connection. You can compare the two by unpacking them and running diff on the two directories to see which files (if any) are different. If the diff outputs no differences, then it's likely the proxy is repacking. If the diff outputs something inspect what the differences are and why your proxy is making such changes as it's likely a security concern in addition to a usability problem.






          share|improve this answer

















          • 1




            That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
            – Sachin Borkar
            Dec 21 '18 at 9:04










          • OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
            – Sachin Borkar
            Dec 21 '18 at 11:29












          • There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
            – Kristopher Ives
            Dec 21 '18 at 15:24
















          0














          When running the update Debian/Ubuntu will download a list of all the meta-data about a package first, from this URL:



          http://us.archive.ubuntu.com/ubuntu/dists/bionic/main/binary-amd64/Packages.gz



          It will contain something like this for every package:



          Package: aodh-common
          Architecture: all
          Version: 6.0.0-0ubuntu1
          Priority: optional
          Section: web
          Source: aodh
          Origin: Ubuntu
          Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
          Original-Maintainer: PKG OpenStack <openstack-devel@lists.alioth.debian.org>
          Bugs: https://bugs.launchpad.net/ubuntu/+filebug
          Installed-Size: 97
          Depends: adduser, dpkg-dev, python-aodh (= 6.0.0-0ubuntu1), python:any
          Filename: pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb
          Size: 17760
          MD5sum: 8f0c651bcc7369034fea6c28653f51b9
          SHA1: 7fc8dd248a5139f0f7dd3be5a49614c1b9af7186
          SHA256: 98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e
          Homepage: https://github.com/openstack/aodh
          Description: OpenStack Telemetry (Ceilometer) Alarming - common files
          Description-md5: 4d4a9638c22eafe95e8cdbfdae651022


          For this package it will then download this URL:



          http://us.archive.ubuntu.com/ubuntu/pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb



          It will then check the SHA256 hash of this similar to doing this:



          $ sha256sum aodh-common_6.0.0-0ubuntu1_all.deb 
          98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e aodh-common_6.0.0-0ubuntu1_all.deb


          Your proxy is modifying the data which breaks the integrity hash check, because the contents have been changed. You should step through the process of running these commands manually, such as downloading the file via your browser and running sha256sum on the command line to see the hashes don't match.



          Next you should see what is actually different between the files and why. It's possible your proxy is able to determine that the .deb file is an "archive" that uses gzip compression and is re-packing the contents, even if that seems rather stupid in this context it could be used for a virus/malware scanning utility.



          Let's assume you have two .deb files, one downloaded via the broken proxy and one downloaded via a proper working connection. You can compare the two by unpacking them and running diff on the two directories to see which files (if any) are different. If the diff outputs no differences, then it's likely the proxy is repacking. If the diff outputs something inspect what the differences are and why your proxy is making such changes as it's likely a security concern in addition to a usability problem.






          share|improve this answer

















          • 1




            That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
            – Sachin Borkar
            Dec 21 '18 at 9:04










          • OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
            – Sachin Borkar
            Dec 21 '18 at 11:29












          • There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
            – Kristopher Ives
            Dec 21 '18 at 15:24














          0












          0








          0






          When running the update Debian/Ubuntu will download a list of all the meta-data about a package first, from this URL:



          http://us.archive.ubuntu.com/ubuntu/dists/bionic/main/binary-amd64/Packages.gz



          It will contain something like this for every package:



          Package: aodh-common
          Architecture: all
          Version: 6.0.0-0ubuntu1
          Priority: optional
          Section: web
          Source: aodh
          Origin: Ubuntu
          Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
          Original-Maintainer: PKG OpenStack <openstack-devel@lists.alioth.debian.org>
          Bugs: https://bugs.launchpad.net/ubuntu/+filebug
          Installed-Size: 97
          Depends: adduser, dpkg-dev, python-aodh (= 6.0.0-0ubuntu1), python:any
          Filename: pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb
          Size: 17760
          MD5sum: 8f0c651bcc7369034fea6c28653f51b9
          SHA1: 7fc8dd248a5139f0f7dd3be5a49614c1b9af7186
          SHA256: 98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e
          Homepage: https://github.com/openstack/aodh
          Description: OpenStack Telemetry (Ceilometer) Alarming - common files
          Description-md5: 4d4a9638c22eafe95e8cdbfdae651022


          For this package it will then download this URL:



          http://us.archive.ubuntu.com/ubuntu/pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb



          It will then check the SHA256 hash of this similar to doing this:



          $ sha256sum aodh-common_6.0.0-0ubuntu1_all.deb 
          98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e aodh-common_6.0.0-0ubuntu1_all.deb


          Your proxy is modifying the data which breaks the integrity hash check, because the contents have been changed. You should step through the process of running these commands manually, such as downloading the file via your browser and running sha256sum on the command line to see the hashes don't match.



          Next you should see what is actually different between the files and why. It's possible your proxy is able to determine that the .deb file is an "archive" that uses gzip compression and is re-packing the contents, even if that seems rather stupid in this context it could be used for a virus/malware scanning utility.



          Let's assume you have two .deb files, one downloaded via the broken proxy and one downloaded via a proper working connection. You can compare the two by unpacking them and running diff on the two directories to see which files (if any) are different. If the diff outputs no differences, then it's likely the proxy is repacking. If the diff outputs something inspect what the differences are and why your proxy is making such changes as it's likely a security concern in addition to a usability problem.






          share|improve this answer












          When running the update Debian/Ubuntu will download a list of all the meta-data about a package first, from this URL:



          http://us.archive.ubuntu.com/ubuntu/dists/bionic/main/binary-amd64/Packages.gz



          It will contain something like this for every package:



          Package: aodh-common
          Architecture: all
          Version: 6.0.0-0ubuntu1
          Priority: optional
          Section: web
          Source: aodh
          Origin: Ubuntu
          Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
          Original-Maintainer: PKG OpenStack <openstack-devel@lists.alioth.debian.org>
          Bugs: https://bugs.launchpad.net/ubuntu/+filebug
          Installed-Size: 97
          Depends: adduser, dpkg-dev, python-aodh (= 6.0.0-0ubuntu1), python:any
          Filename: pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb
          Size: 17760
          MD5sum: 8f0c651bcc7369034fea6c28653f51b9
          SHA1: 7fc8dd248a5139f0f7dd3be5a49614c1b9af7186
          SHA256: 98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e
          Homepage: https://github.com/openstack/aodh
          Description: OpenStack Telemetry (Ceilometer) Alarming - common files
          Description-md5: 4d4a9638c22eafe95e8cdbfdae651022


          For this package it will then download this URL:



          http://us.archive.ubuntu.com/ubuntu/pool/main/a/aodh/aodh-common_6.0.0-0ubuntu1_all.deb



          It will then check the SHA256 hash of this similar to doing this:



          $ sha256sum aodh-common_6.0.0-0ubuntu1_all.deb 
          98cbde3960701b083bc6744cb57fa2b3946d4d5f6c71512e2265f762d4650a3e aodh-common_6.0.0-0ubuntu1_all.deb


          Your proxy is modifying the data which breaks the integrity hash check, because the contents have been changed. You should step through the process of running these commands manually, such as downloading the file via your browser and running sha256sum on the command line to see the hashes don't match.



          Next you should see what is actually different between the files and why. It's possible your proxy is able to determine that the .deb file is an "archive" that uses gzip compression and is re-packing the contents, even if that seems rather stupid in this context it could be used for a virus/malware scanning utility.



          Let's assume you have two .deb files, one downloaded via the broken proxy and one downloaded via a proper working connection. You can compare the two by unpacking them and running diff on the two directories to see which files (if any) are different. If the diff outputs no differences, then it's likely the proxy is repacking. If the diff outputs something inspect what the differences are and why your proxy is making such changes as it's likely a security concern in addition to a usability problem.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 21 '18 at 8:53









          Kristopher Ives

          1,8181016




          1,8181016








          • 1




            That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
            – Sachin Borkar
            Dec 21 '18 at 9:04










          • OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
            – Sachin Borkar
            Dec 21 '18 at 11:29












          • There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
            – Kristopher Ives
            Dec 21 '18 at 15:24














          • 1




            That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
            – Sachin Borkar
            Dec 21 '18 at 9:04










          • OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
            – Sachin Borkar
            Dec 21 '18 at 11:29












          • There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
            – Kristopher Ives
            Dec 21 '18 at 15:24








          1




          1




          That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
          – Sachin Borkar
          Dec 21 '18 at 9:04




          That's what I call 'bang on target' answer. Though I am yet to try out your suggestions, I am sure their outcome will be greatly helpful. Thank you so much for taking time and offering such a detailed help. I will revert with outcomes as soon as I find time to go through your suggestions practically. Thanks again.
          – Sachin Borkar
          Dec 21 '18 at 9:04












          OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
          – Sachin Borkar
          Dec 21 '18 at 11:29






          OK, just went through the process. diff is outputting no difference between the hash sums whatsoever. So the proxy must be repacking, correct?. So should I talk to the sysadmin to make the proxy stop repacking the packages? And if the proxy isn't making any difference to the file while repacking, why the mismatch is occurring in the first place?
          – Sachin Borkar
          Dec 21 '18 at 11:29














          There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
          – Kristopher Ives
          Dec 21 '18 at 15:24




          There are many ways to gzip/compress data, for example you can do it with a compression level of 1 or a level of 9, among other things, each of them would produce slightly different packed versions of the files.
          – Kristopher Ives
          Dec 21 '18 at 15:24













          -1














          Maybe check your source list



          sudo rm -rf /var/lib/apt/lists/*


          then:



          sudo apt-get update


          Do you get the same error without connecting with proxy? try closing may be configured incorrectly






          share|improve this answer

















          • 1




            Been there, done that. No use. Thanks for taking time to help though.
            – Sachin Borkar
            Dec 21 '18 at 8:40
















          -1














          Maybe check your source list



          sudo rm -rf /var/lib/apt/lists/*


          then:



          sudo apt-get update


          Do you get the same error without connecting with proxy? try closing may be configured incorrectly






          share|improve this answer

















          • 1




            Been there, done that. No use. Thanks for taking time to help though.
            – Sachin Borkar
            Dec 21 '18 at 8:40














          -1












          -1








          -1






          Maybe check your source list



          sudo rm -rf /var/lib/apt/lists/*


          then:



          sudo apt-get update


          Do you get the same error without connecting with proxy? try closing may be configured incorrectly






          share|improve this answer












          Maybe check your source list



          sudo rm -rf /var/lib/apt/lists/*


          then:



          sudo apt-get update


          Do you get the same error without connecting with proxy? try closing may be configured incorrectly







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 21 '18 at 8:34









          Hakan san

          1




          1








          • 1




            Been there, done that. No use. Thanks for taking time to help though.
            – Sachin Borkar
            Dec 21 '18 at 8:40














          • 1




            Been there, done that. No use. Thanks for taking time to help though.
            – Sachin Borkar
            Dec 21 '18 at 8:40








          1




          1




          Been there, done that. No use. Thanks for taking time to help though.
          – Sachin Borkar
          Dec 21 '18 at 8:40




          Been there, done that. No use. Thanks for taking time to help though.
          – Sachin Borkar
          Dec 21 '18 at 8:40


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1103529%2fwhy-updating-from-behind-a-proxy-results-in-hash-sum-mismatch-error-while-direct%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕