Yocto Project Manual
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Tiemo,
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Best,
Scott
Quoted 34 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-
recipe-writing-a-new-recipeand since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks. The text should be modified that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall be mentioned.
Would be great if you could take care of this for the next release of the doc.
best regards,
Tiemo
Quoted 4 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Quoted 28 lines
Best,
ScottQuoted 24 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-> >recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks.
From that point onwards it does, but not on the initial build when creating the recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 4 lines
Quoted 4 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall be mentioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Paul,
This sounds reasonable. I will modify based on that practice.
Thanks,
Scott
Quoted 7 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 3:57 AM
To: Rifenbark, Scott M; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project Manual
Quoted 35 lines
Quoted 33 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Best,
ScottQuoted 25 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new->
Quoted 1 line
recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks.
From that point onwards it does, but not on the initial build when creating the
Quoted 23 lines
recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 4 lines
Quoted 4 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall bementioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Cheers,
Paul--
Paul Eggleton
Intel Open Source Technology Centre
Hi,
I have modified this paragraph a bit to deal with the best way to get these checksums. See http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#new-recipe-fetching-code. If there are further concerns just let me know and I can address them.
Scott
Quoted 88 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Rifenbark, Scott M
Sent: Tuesday, July 29, 2014 4:25 AM
To: Paul Eggleton; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualPaul,
This sounds reasonable. I will modify based on that practice.
Thanks,
ScottQuoted 61 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 3:57 AM
To: Rifenbark, Scott M; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualQuoted 4 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Quoted 30 lines
Best,
ScottQuoted 26 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-
Quoted 2 lines
recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks.
From that point onwards it does, but not on the initial build when creating the recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 5 lines
Quoted 5 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall bementioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Quoted 7 lines
Cheers,
Paul--
Paul Eggleton
Intel Open Source Technology Centre--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
This isn't quite what I was thinking of. Yes you should probably use the upstream signatures if they provide them, but it's going to be rare that both md5sum and sha256sum will be provided in my experience. That's why I was suggesting:
1) Recommend if *any* signatures are provided upstream (e.g. md5, sha1, sha256, GPG, etc.) then you should verify these, by hand if necessary (since we only deal with sha256sum and md5sum). This probably should be a note box so that the importance is highlighted.
2) Once that step has been performed if applicable, use the build-fail mechanism to get what you need added to the recipe.
Cheers,
Paul
Quoted 97 lines · Scott M
Hi,
I have modified this paragraph a bit to deal with the best way to get these
checksums. See
http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#new-recipe-> fetching-code. If there are further concerns just let me know and I can address them.Scott
Quoted 88 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Rifenbark, Scott M
Sent: Tuesday, July 29, 2014 4:25 AM
To: Paul Eggleton; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualPaul,
This sounds reasonable. I will modify based on that practice.
Thanks,
ScottQuoted 60 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 3:57 AM
To: Rifenbark, Scott M; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualQuoted 4 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Quoted 28 lines
Best,
ScottQuoted 25 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-> >>> >
Quoted 1 line
recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks.
From that point onwards it does, but not on the initial build when creating the recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 5 lines
Quoted 5 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall bementioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Quoted 7 lines
Cheers,
Paul--
Paul Eggleton
Intel Open Source Technology Centre--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Ahh... okay. I will adjust.
Thanks,
Scott
Quoted 128 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Thursday, July 31, 2014 2:32 AM
To: Rifenbark, Scott M
Cc: Tiemo Krüger; [email protected]
Subject: Re: [yocto] Yocto Project ManualThis isn't quite what I was thinking of. Yes you should probably use the upstream signatures if they provide them, but it's going to be rare that both md5sum and sha256sum will be provided in my experience. That's why I was suggesting:
1) Recommend if *any* signatures are provided upstream (e.g. md5, sha1, sha256, GPG, etc.) then you should verify these, by hand if necessary (since we only deal with sha256sum and md5sum). This probably should be a note box so that the importance is highlighted.
2) Once that step has been performed if applicable, use the build-fail mechanism to get what you need added to the recipe.
Cheers,
PaulQuoted 6 lines · Scott M
Hi,
I have modified this paragraph a bit to deal with the best way to get these checksums. See
http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#new-re
cipe-> fetching-code. If there are further concerns just let me know and I canaddress them.
Quoted 92 lines
Scott
Quoted 89 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Rifenbark, Scott M
Sent: Tuesday, July 29, 2014 4:25 AM
To: Paul Eggleton; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualPaul,
This sounds reasonable. I will modify based on that practice.
Thanks,
ScottQuoted 61 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 3:57 AM
To: Rifenbark, Scott M; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualQuoted 4 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Quoted 29 lines
Best,
ScottQuoted 26 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#n
ew-> >>> >Quoted 1 line
recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks.
From that point onwards it does, but not on the initial build when creating the recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 5 lines
Quoted 5 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall bementioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Quoted 7 lines
Cheers,
Paul--
Paul Eggleton
Intel Open Source Technology Centre--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
Paul Eggleton
Intel Open Source Technology Centre
On reflection, it could be that the manual verification step is after you get the error to make things flow a bit more easily; the critical thing is it should be before you paste the values into the recipe and continue on with the build.
Cheers,
Paul
Quoted 138 lines · Scott M
Ahh... okay. I will adjust.
Thanks,
ScottQuoted 133 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Thursday, July 31, 2014 2:32 AM
To: Rifenbark, Scott M
Cc: Tiemo Krüger; [email protected]
Subject: Re: [yocto] Yocto Project ManualThis isn't quite what I was thinking of. Yes you should probably use the upstream signatures if they provide them, but it's going to be rare that both md5sum and sha256sum will be provided in my experience. That's why I was
suggesting:1) Recommend if *any* signatures are provided upstream (e.g. md5, sha1, sha256, GPG, etc.) then you should verify these, by hand if necessary (since we only deal with sha256sum and md5sum). This probably should be a note box so that the importance is highlighted.
2) Once that step has been performed if applicable, use the build-fail mechanism to get what you need added to the recipe.
Cheers,
PaulQuoted 7 lines · Scott M
Hi,
I have modified this paragraph a bit to deal with the best way to get these checksums. See
http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#new-re
cipe-> fetching-code. If there are further concerns just let me know and I can>address them.
Quoted 94 lines
Scott
Quoted 92 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Rifenbark, Scott M
Sent: Tuesday, July 29, 2014 4:25 AM
To: Paul Eggleton; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualPaul,
This sounds reasonable. I will modify based on that practice.
Thanks,
ScottQuoted 64 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 3:57 AM
To: Rifenbark, Scott M; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualQuoted 4 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Quoted 31 lines
Best,
ScottQuoted 28 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#n
ew-> >>> >Quoted 1 line
recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle attacks.
From that point onwards it does, but not on the initial build when creating the recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 5 lines
Quoted 5 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall bementioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Quoted 7 lines
Cheers,
Paul--
Paul Eggleton
Intel Open Source Technology Centre--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
Paul Eggleton
Intel Open Source Technology Centre
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
ok
Quoted 162 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Thursday, July 31, 2014 6:46 AM
To: Rifenbark, Scott M
Cc: Tiemo Krüger; [email protected]
Subject: Re: [yocto] Yocto Project ManualOn reflection, it could be that the manual verification step is after you get the error to make things flow a bit more easily; the critical thing is it should be before you paste the values into the recipe and continue on with the build.
Cheers,
PaulQuoted 102 lines · Scott M
Ahh... okay. I will adjust.
Thanks,
ScottQuoted 97 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Thursday, July 31, 2014 2:32 AM
To: Rifenbark, Scott M
Cc: Tiemo Krüger; [email protected]
Subject: Re: [yocto] Yocto Project ManualThis isn't quite what I was thinking of. Yes you should probably use the upstream signatures if they provide them, but it's going to be rare that both md5sum and sha256sum will be provided in my experience. That's why I was
suggesting:1) Recommend if *any* signatures are provided upstream (e.g. md5, sha1, sha256, GPG, etc.) then you should verify these, by hand if necessary (since we only deal with sha256sum and md5sum). This probably should be a note box so that the importance is highlighted.
2) Once that step has been performed if applicable, use the build-fail mechanism to get what you need added to the recipe.
Cheers,
PaulQuoted 9 lines · Scott M
Hi,
I have modified this paragraph a bit to deal with the best way to get these checksums. See
http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#new
-re
cipe-> fetching-code. If there are further concerns just let me cipe-> know and
I can>address them.
Quoted 61 lines
Scott
Quoted 59 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Rifenbark, Scott M
Sent: Tuesday, July 29, 2014 4:25 AM
To: Paul Eggleton; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualPaul,
This sounds reasonable. I will modify based on that practice.
Thanks,
ScottQuoted 44 lines
-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 3:57 AM
To: Rifenbark, Scott M; Tiemo Krüger
Cc: [email protected]
Subject: Re: [yocto] Yocto Project ManualQuoted 36 lines · Scott M
Thanks for noting this and contacting me. I am reposting to the [email protected] group for additional input. I will get modifications into the manual.
Best,
ScottQuoted 29 lines
-----Original Message-----
From: Tiemo Krüger [mailto:[email protected]]
Sent: Tuesday, July 29, 2014 2:50 AM
To: Rifenbark, Scott M
Subject: Yocto Project ManualHello Scott,
I just read a little bit in this doc:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.htm
l#n
ew-> >>> >Quoted 1 line
recipe-writing-a-new-recipe
and since your eMail is mentioned on top I contact you regarding the below paragraph in chapter 5.3.5
"To find these checksums, you can comment the statements out and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. Once you have the correct checksums, simply copy them into your recipe for a subsequent build."
We here really think this is the wrong way to create the checksums for a recipe since downloading them and then creating the checksum doesn't protect you against man in the middle
attacks.
Quoted 35 lines
Quoted 35 lines
Quoted 34 lines
Quoted 34 lines
Quoted 21 lines
From that point onwards it does, but not on the initial build when creating the recipe, you are correct. If the upstream website does provide checksums or GPG signatures (and quite a lot don't) then you should use those to verify the source that was fetched.
Quoted 5 lines
Quoted 5 lines
The text should be modified
that the checksums must at least be checked against the checksums provided by the original website even if this is still not completely safe. And simple command line tools like md5sum and sha256sum shall bementioned.
I think the simplest thing is to just add a note which says that you should verify what was fetched against whatever signatures are provided by the upstream (if any). You can still use the build-fail method we currently describe as well so that you get the exact lines you need to put in the recipe rather than having to type those out each time.
Quoted 7 lines
Cheers,
Paul--
Paul Eggleton
Intel Open Source Technology Centre--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoQuoted 4 lines
Quoted 4 lines
--
Paul Eggleton
Intel Open Source Technology Centre--
Paul Eggleton
Intel Open Source Technology Centre