David E. Ross wrote:
> For example, a hash mismatch would cause the downloaded file to be
> deleted. Also a misformed hash would block downloading. Both of these
> create denial-of-service opportunities; all a hacker has to do is alter
> the hash in the anchor (link) that would be used to initi
Nelson B wrote:
> A certificate that you make for yourself, with your own play/pretend
> CA, may look (superficially) like a real code signing cert from a
> real CA, but it won't work like one for most browser users. You may
> be able to get a few of your closest friends to download and trust
> yo
Nelson B wrote:
>>-u certusage Specify certificate usage:
>> C SSL Client
>> V SSL Server
>> S Email signer
>> R Email Recipient
>> O O
[EMAIL PROTECTED] wrote:
> I created the certificate request using certutil (from what I
> remember) :
> certutil -R -s "CN=t, O=req, L=req, ST=req, C=RE" -p "555-555-" -o
> mycert.req -d ~/.xulapp
The problem with your end-entity cert (the one with the [EMAIL PROTECTED]
nickname) is that it d
4 matches
Mail list logo
