public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Planning out Core Update 117
Date: Wed, 22 Nov 2017 11:30:14 +0100	[thread overview]
Message-ID: <3513F240-1613-42F0-B8CD-58FD1E75C30C@ipfire.org> (raw)
In-Reply-To: =?utf-8?q?=3Ctrinity-a0a18c36-a312-4e0c-8eb0-a7c234563211-15112?= =?utf-8?q?67423115=403c-app-mailcom-bs02=3E?=

[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]

Hi,
normally i agree but in that case it differs at least only here ?

Check over HTTP:
-> curl -O http://people.ipfire.org/~ummeegge/OpenVPN-2.4/Core115/ovpn_244_64_v3_core115.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   185  100   185    0     0    326      0 --:--:-- --:--:-- --:--:--   326

-> sha256sum ovpn_244_64_v3_core115.tar.gz 
b8a7ebde1eec9fbba3790e31136fdfe3c7ea5b8c27900df1942f28cbe7b9f9f7  ovpn_244_64_v3_core115.tar.gz

-> ll ovpn_244_64_v3_core115.tar.gz 
-rw-r--r-- 1 root root 185 Nov 22 11:26 ovpn_244_64_v3_core115.tar.gz

-> rm -rf ovpn_244_64_v3_core115.tar.gz

Check over HTTPS:
-> curl -O https://people.ipfire.org/~ummeegge/OpenVPN-2.4/Core115/ovpn_244_64_v3_core115.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  484k  100  484k    0     0  1302k      0 --:--:-- --:--:-- --:--:-- 1304k

-> sha256sum ovpn_244_64_v3_core115.tar.gz 
10bc3162d6f061b291fe6e3b4284700431f061d55903f719cafa16bd33c48f40  ovpn_244_64_v3_core115.tar.gz

-> ll ovpn_244_64_v3_core115.tar.gz 
-rw-r--r-- 1 root root 495633 Nov 22 11:22 ovpn_244_64_v3_core115.tar.gz


whereby i get the same results as Michael Horace, smaller package same SHA256 sum. Nevertheless please use only the package with the correct SHA256 sum !

Greetings,

Erik



> Indeed, the transport method should not impact the file being downloaded.
> Today I did the download again using both HTTP and HTTPS: the size & hash are the same no matter the transport method used.
> Something went wrong on my previous download (the size was only 185K instead of 485): there is no need to change the install procedure.
> 
> I'll continue the tests for OpenVPN 2.4.4 and post results on forum topic.
> 
> 
> Best regards,
> Horace
> 
> 
> 
>> Sent: Tuesday, November 21, 2017 at 1:49 PM
>> From: "Michael Tremer" <michael.tremer(a)ipfire.org>
>> To: ummeegge <ummeegge(a)ipfire.org>, "Horace Michael" <horace.michael(a)gmx.com>, development(a)lists.ipfire.org
>> Subject: Re: Planning out Core Update 117
>> 
>> The checksum should be exactly the same no matter what the protocol is used to
>> transfer it.
>> 
>> -Michael


             reply	other threads:[~2017-11-22 10:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 10:30 ummeegge [this message]
     [not found] <7EA8C1E7-14CC-4906-9688-504DA016795D@gmx.com>
2017-11-10 15:36 ` ummeegge
2017-11-18 20:53   ` Horace Michael
2017-11-21 10:25     ` ummeegge
2017-11-21 11:49       ` Michael Tremer
2017-11-21 12:30         ` Horace Michael
  -- strict thread matches above, loose matches on Subject: below --
2017-11-06 18:32 Michael Tremer
2017-11-06 21:06 ` Matthias Fischer
2017-11-07 10:44   ` Michael Tremer
2017-11-17 12:59     ` Matthias Fischer
2017-11-17 19:37       ` Matthias Fischer
2017-11-17 21:25         ` Michael Tremer
2017-11-17 23:15           ` Matthias Fischer
2017-11-18  7:44         ` Marcel Lorenz
2017-11-06 21:09 ` Matthias Fischer
2017-11-07 10:46   ` Michael Tremer
2017-11-07 15:05     ` Michael Tremer
2017-11-07 18:41       ` Matthias Fischer
2017-11-07 22:47         ` Michael Tremer
2017-11-21 14:42           ` Michael Tremer
2017-11-21 17:35             ` Matthias Fischer
2017-11-22 16:37               ` Michael Tremer
2017-11-10 11:01 ` ummeegge
2017-11-10 12:18   ` Michael Tremer
2017-11-10 13:35     ` ummeegge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3513F240-1613-42F0-B8CD-58FD1E75C30C@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox