On Fri, 19 Feb 2016 13:18:12 +0200
Ioan-Adrian Ratiu wrote:
> On Thu, 18 Feb 2016 11:28:58 +0200
> Ioan-Adrian Ratiu wrote:
>
> > Hello
> >
> > On Thu, 18 Feb 2016 11:04:22 +0200
> > Markus Lehtonen wrote:
> >
> > > Hi,
> > >
> > >
> > >
> > > On 17/02/16 17:41, "Ioan-Adrian Ratiu"
> >
On Thu, 18 Feb 2016 11:28:58 +0200
Ioan-Adrian Ratiu wrote:
> Hello
>
> On Thu, 18 Feb 2016 11:04:22 +0200
> Markus Lehtonen wrote:
>
> > Hi,
> >
> >
> >
> > On 17/02/16 17:41, "Ioan-Adrian Ratiu"
> > > adrian.ra...@ni.com> wrote:
> >
> > >Implement local ipk signing logic inside the g
On 18/02/16 11:28, "Ioan-Adrian Ratiu" wrote:
>Hello
>
>On Thu, 18 Feb 2016 11:04:22 +0200
>Markus Lehtonen wrote:
>
>> Hi,
>>
>>
>>
>> On 17/02/16 17:41, "Ioan-Adrian Ratiu"
>> > adrian.ra...@ni.com> wrote:
>>
>> >Implement local ipk signing logic inside the gpg backend and add a new
>> >
Hello
On Thu, 18 Feb 2016 11:04:22 +0200
Markus Lehtonen wrote:
> Hi,
>
>
>
> On 17/02/16 17:41, "Ioan-Adrian Ratiu"
> adrian.ra...@ni.com> wrote:
>
> >Implement local ipk signing logic inside the gpg backend and add a new
> >bbclass which configures signing similar to how rpm does it.
> >
Hi,
On 17/02/16 17:41, "Ioan-Adrian Ratiu"
wrote:
>Implement local ipk signing logic inside the gpg backend and add a new
>bbclass which configures signing similar to how rpm does it.
>
>The ipk signing process is a bit different from rpm:
>- Signatures are stored outside ipk files; opkg
Implement local ipk signing logic inside the gpg backend and add a new
bbclass which configures signing similar to how rpm does it.
The ipk signing process is a bit different from rpm:
- Signatures are stored outside ipk files; opkg connects to a feed
server and downloads them to verify a pack
