Re: Sendmail trojan...?

From: Emacs (admin@crimelords.org)
Date: 10/09/02


Date: Wed, 9 Oct 2002 09:16:28 -0500 (CDT)
From: Emacs <admin@crimelords.org>
To: Ken Ebling <deevil@deevil.homeunix.org>

I'm hoping so myself...although my build date is out of the range the CERT
defines....I guess you could verify via the md5's?

-e

On Wed, 9 Oct 2002, Ken Ebling wrote:

> http://www.cert.org/advisories/CA-2002-28.html
>
> I'm assuming recent cvs buildworlds are immune to this??
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message



Relevant Pages

  • RE: [Full-Disclosure] Openssl proof of concept code? / Neoteris
    ... its own built-in cert and offers it up without solicitation. ... SSL connection with the server with a corrupt cert like that. ... modify a copy of openssl such that it sends a client certificate ... verify error:num=20:unable to get local issuer certificate ...
    (Full-Disclosure)
  • Re: certificates for signing documents
    ... but won't verify with is own cert because its root CA ... a public key certificate from a client certificate using makecert ...
    (microsoft.public.platformsdk.security)
  • RE: CryptVerifyCertificateSignature fails with NTE_BAD_SIGNATURE
    ... you should use signer's public key to verify the signature. ... to verify if the cert is self-signed. ... > want is to check whether a signed file has been tampered with but the ...
    (microsoft.public.platformsdk.security)
  • RE: Backing up keys
    ... in case of certificates you should archive the verifying cert chain. ... (Although some of these certs may be much longer lifetime than the signing ... > order to verify the sig, the relevant public sig key is ... in order to verify the ...
    (microsoft.public.platformsdk.security)
  • Re: Questions (Rants?) About IPSEC
    ... I guess what happened was I got it stuck in my head that the ... "certificate_type x509" directive specified the *remote* cert and ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)