From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: opkg and gpg signed ipk packages
Date: Tue, 19 May 2015 05:56:04 -0600 [thread overview]
Message-ID: <555B24D4.6070101@mlbassoc.com> (raw)
In-Reply-To: <3230301C09DEF9499B442BBE162C5E482599AC00@SESTOEX04.enea.se>
On 2015-05-19 05:47, Sona Sarmadi wrote:
>
>>> I'm guessing you would want something like this in your custom distro
>>> config (or local.conf if you must):
>>>
>>> PACKAGECONFIG_append_pn-opkg = " sha256"
>>> PACKAGECONFIG_append_pn-opkg-native = " sha256"
>>
>
> Thanks a lot guys for your help, this is now working :)
> There is support for sha256 in opkg but not in the opkg-utils.
> opkg-utils (opkg.py) just uses md5 as default option. I changed
>
> opkg.py:
> ........
> # compute the MD5.
> if not self.fn:
> self.md5 = 'Unknown'
> else:
> f = open(self.fn, "rb")
> sum = hashlib.md5()
> to
> sum = hashlib.sha256()
>
> and now I get checksum sha256 in the "Packages" file:
>
> SHA256Sum: 6be1fb5b9dab3de5848fd578d515d05adc5c6cd3b0009f8c1b13ab1250cee594
>
> Do you think this patch would be of interest for someone?
Yes, including everything you found that needs to be set up to
support these checksums.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-05-19 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 19:11 opkg and gpg signed ipk packages Sona Sarmadi
2015-05-07 20:09 ` Paul Barker
2015-05-08 14:26 ` Sona Sarmadi
2015-05-08 16:23 ` Paul Barker
2015-05-13 20:20 ` Sona Sarmadi
2015-05-14 8:49 ` Paul Eggleton
2015-05-14 14:15 ` Sona Sarmadi
2015-05-19 11:47 ` Sona Sarmadi
2015-05-19 11:56 ` Gary Thomas [this message]
2015-05-19 12:01 ` Otavio Salvador
2015-05-19 14:23 ` Mark Hatle
2015-05-20 10:44 ` Sona Sarmadi
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=555B24D4.6070101@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.