On 4/4/02 10:28 PM, "Max Horn" <[EMAIL PROTECTED]> wrote:
> At 8:31 Uhr -0500 03.04.2002, Chris Zubrzycki wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Is there any way of signing the deb files in the bin dist to make
>> sure they were make by an authorized developer? Is this
On 4/4/02 11:31 PM, "Chris Zubrzycki" <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thursday, April 4, 2002, at 07:28 AM, Max Horn wrote:
>
>> At 8:31 Uhr -0500 03.04.2002, Chris Zubrzycki wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 4, 2002, at 07:28 AM, Max Horn wrote:
> At 8:31 Uhr -0500 03.04.2002, Chris Zubrzycki wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Is there any way of signing the deb files in the bin dist to make sure
>> they
At 8:31 Uhr -0500 03.04.2002, Chris Zubrzycki wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Is there any way of signing the deb files in the bin dist to make
>sure they were make by an authorized developer? Is this in the plan
>for the future? I remember reading that debian maintaine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there any way of signing the deb files in the bin dist to make sure
they were make by an authorized developer? Is this in the plan for the
future? I remember reading that debian maintainers signs thier packages.
just a thought.
- -chris zubrzyc