Re: apt-transport-https not sending client certificate
Re-posting this to the list, because I'm an idiot and didn't notice
that I originally replied directly to Andrei, and I don't want people
to think I blanked him. :)
(Here's hoping I don't noob this one up, as well)
On 28 June 2011 21:00, Andrei POPESCU <andreimpopescu@gmail.com> wrote:
> On Ma, 28 iun 11, 15:51:43, Mel Collins wrote:
>> On 28 June 2011 12:19, Andrei POPESCU <andreimpopescu@gmail.com> wrote:
>> > Just out of curiosity, but why are you doing this?
>>
>> So I can create a secure repository with limited access (local
>> because it's currently only proof-of-concept, or lack thereof!), using
>> a method more secure than just sticking a username and password in the
>> apt URL. My understanding is that the sources.list file must be
>> world-readable, so isn't a very good place to keep secrets. :)
>> I've read a few posts here and there about people implementing
>> something similar, but if you have any better solutions I'm all ears
>> to that, too. :)
>
> "limited access" makes sense of course. I was asking merely because some
> people don't realise that secure-apt works even if the debs come from a
> completely untrustworthy source and/or are transmitted over insecure
> connections ;)
>
> Sorry to waste your time without even being able to help.
>
> Regards,
> Andrei
> P.S. If your message was meant for the list (instead of private mail)
> feel free to include my reply
>_>
- Mel
Reply to: