On Fri, Dec 28, 2012 at 9:28 AM, Matthew Seaman wrote:
> On 27/12/2012 21:01, Garrett Wollman wrote:
>>> I'm creating my own repository and have created a key for it.
>> [...]
>>> >What does pkg expect to be in this file?
>
>> A public key. It does not use X.509 (nor is there any reason why it
>>
On 27/12/2012 21:01, Garrett Wollman wrote:
>> I'm creating my own repository and have created a key for it.
> [...]
>> >What does pkg expect to be in this file?
> A public key. It does not use X.509 (nor is there any reason why it
> should, although I suppose it could be made to at the cost of
>
Am Thu, 27 Dec 2012 16:01:43 -0500 (EST)
schrieb Garrett Wollman :
> In article <20121227162311$6...@grapevine.csail.mit.edu>,
> rai...@ultra-secure.de writes:
>
> >I'm creating my own repository and have created a key for it.
> [...]
> >What does pkg expect to be in this file?
>
> A public key.
In article <20121227162311$6...@grapevine.csail.mit.edu>,
rai...@ultra-secure.de writes:
>I'm creating my own repository and have created a key for it.
[...]
>What does pkg expect to be in this file?
A public key. It does not use X.509 (nor is there any reason why it
should, although I suppose i
On Thu, Dec 27, 2012 at 6:22 PM, Rainer Duffner wrote:
> Hi,
>
> I'm creating my own repository and have created a key for it.
>
> I've created a CSR for it and used that to generate a certificate via
> our internal CA. Because there was no other information available, I
> used the profile that we
Hi,
I'm creating my own repository and have created a key for it.
I've created a CSR for it and used that to generate a certificate via
our internal CA. Because there was no other information available, I
used the profile that we use to generate SSL-certificates for web
servers.
I copied the cer
