From idwg-public-request@semper.org  Mon Jul 22 11:03:37 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06518
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 11:03:35 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 2DA8634798; Mon, 22 Jul 2002 17:04:02 +0200 (CEST)
Old-Return-Path: <mike@cs.hmc.edu>
Delivered-To: semper-idwg-public@opencard.org
Date: Mon, 22 Jul 2002 08:03:34 -0700
From: Mike Erlinger <mike@cs.hmc.edu>
To: intrusion detection wg <idwg-public@zurich.ibm.com>
Subject: [support@comodo.net: ORDER #13898 - IMPORTANT INFORMATION]
Message-Id: <20020722150334.GB26249@cs.hmc.edu>
Reply-To: mike@cs.hmc.edu
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="liOOAslEiF7prFVr"
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Resent-Message-ID: <t0nUP.A.hoE.i7BP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/529
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 22 Jul 2002 17:04:02 +0200 (CEST)


--liOOAslEiF7prFVr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

who wanted it?

-- 
Mike Erlinger, Professor and Chair Computer Science
www:      http://www.cs.hmc.edu/~mike
email:    mike@cs.hmc.edu
smail:    Computer Science Dept., Harvey Mudd College,
          301 E. 12th Street, Claremont, CA, 91711 
          909-621-8912,   FAX: 909-607-8364

--liOOAslEiF7prFVr
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <support@comodo.net>
Received: from webserver2.comodo.net ([64.69.179.3])
	by muddcs.cs.hmc.edu (8.10.2+Sun/8.9.3) with ESMTP id g6MCQiD29676
	for <staff@cs.hmc.edu>; Mon, 22 Jul 2002 05:26:44 -0700 (PDT)
Received: from 192.168.5.8 (ora1 [192.168.5.5])
	by cobalt-eth1.comodo.net (8.10.2/8.10.2) with SMTP id g6MCe1e12469;
	Mon, 22 Jul 2002 13:40:01 +0100
Date: Mon, 22 Jul 2002 13:40:01 +0100
Message-Id: <200207221240.g6MCe1e12469@webserver2.comodo.net>
Subject: ORDER #13898 - IMPORTANT INFORMATION
From: Comodo Security Services <support@comodo.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="(AlternativeBoundary)"
To: staff@cs.hmc.edu

--(AlternativeBoundary)
Content-Type: multipart/alternative; boundary="(AlternativeBoundary2)"

--(AlternativeBoundary2)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Your InstantSSL Certificate for bossman.cs.hmc.edu is attached!

Dear staff@cs.hmc.edu,

Thank you again for selecting Comodo as your Certification Authority. We have now
successfully completed the necessary background checks and are pleased to
announce that your InstantSSL Certificate for bossman.cs.hmc.edu has been issued.

Installation Instructions:
You will find a number of certificates attached to this email. It is essential
that all certificates be installed on your webserver software. For more
installation instructions please refer to www.instantssl.com/support:
  1. Install GlobalSignRootCA.crt, GlobalSignPartnersCA.crt and
    ComodoClass3SecurityServicesCA.crt.
  2. The fourth certificate attached to this email is your
    InstantSSL Certificate for bossman.cs.hmc.edu.
    Install this certificate on your webserver. If you require instructions on
    how to install your certificate, please use the online support resources
    available at www.instantssl.com/support.

When you have implemented your SSL Certificate, be sure to display the
secure site seal. Promoting your secure site is the ideal way to help
customers feel safe and confident in using your secure online services.

Get your secure site seal now: http://www.instantssl.com/support/siteseal

Should you have any questions or issues you would like to discuss, please do not
hesitate to contact us.


Kind Regards,


Comodo Security Services

Support Email: support@comodo.net
WWW: http://www.comodo.net/support
Telephone: +44 1274 730505
Fax: +44 1274 730909
Postal Address: PO Box 229, Bradford BD7 1XN, UK

--(AlternativeBoundary2)
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
<head>
  <style type=text/css>
  <!--
    body { font-family: Arial, Helvetica, sans-serif; font-size: 10pt }
    p { font-family: Arial, Helvetica, sans-serif; font-size: 10pt }
    td { font-family: Arial, Helvetica, sans-serif; font-size: 10pt }
    .p8 { font-family: Arial, Helvetica, sans-serif; font-size: 8pt; font-weight: normal }
    .p4 { font-family: Arial, Helvetica, sans-serif; font-size: 10pt; color: #006699; font-weight: bold }
    A:link { font-family: Arial; font-size: 10pt; color: #EC5F00; text-decoration: underline }
    A:visited { font-family: Arial; font-size: 10pt; color: #EC5F00; text-decoration: underline }
    A:active { font-family: Arial; font-size: 10pt; color: #EC5F00; text-decoration: underline }
    A:hover { font-family: Arial; font-size: 10pt; color: #666666; text-decoration: underline }
    A.white:link { font-family: Arial; font-size: 8pt; color: #FFFFFF; text-decoration: underline }
    A.white:visited { font-family: Arial; font-size: 8pt; color: #FFFFFF; text-decoration: underline }
    A.white:active { font-family: Arial; font-size: 8pt; color: #FFFFFF; text-decoration: underline }
    A.white:hover { font-family: Arial; font-size: 8pt; color: #33CCFF; text-decoration: underline }
    .title { font-family: Arial, Helvetica, sans-serif; font-size: 12pt; font-weight: bold; color: #003399 }
    -->
  </style>
</head>
<body bgcolor=#CCCCCC text=#000000 leftmargin=4 topmargin=5>
<table width=100% border=0 cellspacing=0 cellpadding=1 align=center>
  <tr>
    <td bgcolor=#000000>
      <table width=100% border=0 cellspacing=0 cellpadding=3>
        <tr>
          <td bgcolor=#FFFFFF>
            <p><font size=2 class=title>Your InstantSSL Certificate for bossman.cs.hmc.edu is attached!</font>
          </td>
          <td bgcolor=#FFFFFF align=right>
            <a href=http://www.instantssl.com/><img src=http://www.instantssl.com/images/instantssl_espotting.gif width=90 height=53 border=0></a>
          </td>
        </tr>
        <tr>
          <td bgcolor=#FFFFFF colspan=2>
            <p>Dear staff@cs.hmc.edu,</p>
            <p>Thank you again for selecting Comodo as your Certification Authority.
              We have now successfully completed the necessary background checks
              and are pleased to announce that your InstantSSL Certificate for bossman.cs.hmc.edu
              has been issued.</p>
            <p><b>Installation Instructions:</b></p>
            <p>You will find a number of certificates attached to this email.
              It is essential that all certificates be installed on your webserver
              software. For more installation instructions please refer to <a href=http://www.instantssl.com/support>www.instantssl.com/support</a> -</p>
            <p>1. Install GlobalSignRootCA.crt, GlobalSignPartnersCA.crt and ComodoClass3SecurityServicesCA.crt.<br><br>
              2. The fourth certificate attached to this email is your InstantSSL Certificate for bossman.cs.hmc.edu.
              Install this certificate on your webserver. If you require instructions on how to install your certificate
              please use the online support resources available at <a href=http://www.instantssl.com/support>www.instantssl.com/support</a></p>
            <p>When you have implemented your SSL Certificate, be sure to display the
              secure site seal. Promoting your secure site is the ideal way to help
              customers feel safe and confident in using your secure online services.</p>
            <p>Get your secure site seal now: <a href=http://www.instantssl.com/support/siteseal>http://www.instantssl.com/support/siteseal</a></p>
            <p>Should you have any questions or issues you would like to discuss,
              please do not hesitate to contact us.</p>
            <p><br>Kind Regards,</p>
            <p><br><b>Comodo Security Services</b></p>
            <p class=p8><b>Support Email:</b> <a href=mailto:support@comodo.net>support@comodo.net</a><br>
              <b>WWW:</b> <a href=http://www.comodo.net/support target=_blank>http://www.comodo.net/support</a><br>
              <b>Telephone:</b> +44 1274 730505</br>
              <b>Fax:</b> +44 1274 730909<br>
              <b>Postal Address:</b> PO Box 229, Bradford BD7 1XN, UK
            </p>
          </td>
        </tr>
      </table>
    </td>
  </tr>
</table>
</body>
</html>

--(AlternativeBoundary2)--

--(AlternativeBoundary)
Content-Type: application/pkix-cert; name="GlobalSignRootCA.crt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="GlobalSignRootCA.crt"
Content-Transfer-Encoding: 7bit

-----BEGIN CERTIFICATE-----
MIIDdTCCAl2gAwIBAgILAgAAAAAA1ni3lAUwDQYJKoZIhvcNAQEEBQAwVzELMAkG
A1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEDAOBgNVBAsTB1Jv
b3QgQ0ExGzAZBgNVBAMTEkdsb2JhbFNpZ24gUm9vdCBDQTAeFw05ODA5MDExMjAw
MDBaFw0xNDAxMjgxMjAwMDBaMFcxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9i
YWxTaWduIG52LXNhMRAwDgYDVQQLEwdSb290IENBMRswGQYDVQQDExJHbG9iYWxT
aWduIFJvb3QgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDaDuaZ
jc6j40+Kfvvxi4Mla+pIH/EqsLmVEQS98GPR4mdmzxzdzxtIK+6NiY6arymAZavp
xy0Sy6scTHAHoT0KMM0VjU/43dSMUBUc71DuxC73/OlS8pF94G3VNTCOXkNz8kHp
1Wrjsok6Vjk4bwY8iGlbKk3Fp1S4bInMm/k8yuX9ifUSPJJ4ltbcdG6TRGHRjcdG
snUOhugZitVtbNV4FpWi6cgKOOvyJBNPc1STE4U6G7weNLWLBYy5d4ux2x8gkasJ
U26Qzns3dLlwR5EiUWMWea6xrkEmCMgZK9FGqkjWZCrXgzT/LCrBbBlDSgeF59N8
9iFo7+ryUp9/k5DPAgMBAAGjQjBAMA4GA1UdDwEB/wQEAwIABjAdBgNVHQ4EFgQU
YHtmGkUNl8qJUC99BM00qP/8/UswDwYDVR0TAQH/BAUwAwEB/zANBgkqhkiG9w0B
AQQFAAOCAQEArqqf/LfSyx9fOSkoGJ40yWxPbxrwZKJwSk8ThptgKJ7ogUmYfQq7
5bCdPTbbjwVR/wkxKh/diXeeDy5slQTthsu0AD+EAk2AaioteAuubyuig0SDH81Q
gkwkr733pbTIWg/050deSY43lv6aiAU62cDbKYfmGZZHpzqmjIs8d/5GY6dT2iHR
rH5Jokvmw2dZL7OKDrssvamqQnw1wdh/1acxOk5jQzmvCLBhNIzTmKlDNPYPhyk7
ncJWWJh3w/cbrPad+D6qp1RF8PX51TFl/mtYnHGzHtdS6jIX/EBgHcl5JLL2bP2o
Zg6C3ZjL2sJETy6ge/L3ayx2EYRGinij4w==
-----END CERTIFICATE-----

--(AlternativeBoundary)
Content-Type: application/pkix-cert; name="GlobalSignPartnersCA.crt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="GlobalSignPartnersCA.crt"
Content-Transfer-Encoding: 7bit

-----BEGIN CERTIFICATE-----
MIIDnjCCAoagAwIBAgILAgAAAAAA1ni50a8wDQYJKoZIhvcNAQEEBQAwVzELMAkG
A1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEDAOBgNVBAsTB1Jv
b3QgQ0ExGzAZBgNVBAMTEkdsb2JhbFNpZ24gUm9vdCBDQTAeFw05OTAxMjgxMjAw
MDBaFw0wOTAxMjgxMjAwMDBaMF8xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9i
YWxTaWduIG52LXNhMRQwEgYDVQQLEwtQYXJ0bmVycyBDQTEfMB0GA1UEAxMWR2xv
YmFsU2lnbiBQYXJ0bmVycyBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBANIs+DKsShJ6N8gpkaWujG4eDsA0M4jlM3EWHHiEaMMYNFAuFj6xlIJPsZqf
APjGETXGaXuYAq0ABohs50wzKACIJ0Yfh7NxdWO8MruI3mYYDlAGk7T2vBQ3MD0i
3z3/dX7ZChrFn7P80KyzCHqJ0wHoAFznSgs9TXsmordiBovaRt2TFz8/WwJLC7aI
IBGSAK27xy7U40Wu9YlafI2krYVkMsAnjMbyioCShiRWWY10aKKDQrOePVBBhm8g
bvb9ztMZ4zLMj+2aXm0fKPVSrG4YXvg90ZLlumwBiEsK8i3eZTMFQqBMqjF2vv2/
gXj5cRxGXi0VlS0wWY5MQdFiqz0CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgAGMB0G
A1UdDgQWBBRDJI1wFQhiVZxPDEAXXYZeD6JM+zAfBgNVHSMEGDAWgBRge2YaRQ2X
yolQL30EzTSo//z9SzAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBBAUAA4IB
AQBm7bSIaRGZgiGDrKFti5uErQ8tyB6Mynt+rarUjt4H1p5Fx6W4nAc5YCVVGsBP
GeXPFylJiRg1ZuXrKEBOV8mvs+S4IAWjO5VQkUmUKX0s5YhBpUWIXp2CJ/fS71u1
T5++/jVlLFVkn+FR2iJhd7pYTo/GeVlZbjCAok+QbiELrdBoOZAQm+0iZW8eETjm
f4zS8zltR9Uh6Op1OkHRrfYWnV0LIb3zH2MGJR3BHzVxLOsgGdXBsOw95W/tAgc/
E3tmktZEwZj3X1CLelvCb22w0fjldKBAN6MlD+Q9ymQxk5BcMHu5OTGaXkzNuUFP
UOQ9OK7IZtnHO11RR6ybq/Kt
-----END CERTIFICATE-----

--(AlternativeBoundary)
Content-Type: application/pkix-cert; name="ComodoClass3SecurityServicesCA.crt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="ComodoClass3SecurityServicesCA.crt"
Content-Transfer-Encoding: 7bit

-----BEGIN CERTIFICATE-----
MIIEJDCCAwygAwIBAgILAwAAAAAA673P5PkwDQYJKoZIhvcNAQEFBQAwXzELMAkG
A1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExFDASBgNVBAsTC1Bh
cnRuZXJzIENBMR8wHQYDVQQDExZHbG9iYWxTaWduIFBhcnRuZXJzIENBMB4XDTAy
MDEzMTE4MzAzMloXDTA4MTIzMTEyMDAwMFowgdwxCzAJBgNVBAYTAkdCMRcwFQYD
VQQKEw5Db21vZG8gTGltaXRlZDEdMBsGA1UECxMUQ29tb2RvIFRydXN0IE5ldHdv
cmsxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9mIHVzZTogaHR0cDov
L3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDIgQ29t
b2RvIExpbWl0ZWQxLDAqBgNVBAMTI0NvbW9kbyBDbGFzcyAzIFNlY3VyaXR5IFNl
cnZpY2VzIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoc9BbyPV
mvY6/4DdrjXs1X5qjSNjYh1nxIpUPGT1zUJiUJ9PeImeQbXkrM+Oi7I31br3yohR
VxvT2pURGu6AuOY44J7JltxuN9Jv1VkzMSfizJoBQ8pVJC0bJdFIgYBjugVI8izi
40rb3toUr4255xIHFo38VQqpAmy4x9tMiiwsKd05itN3dQytiVjBZJEaYVHg9f5E
1MBmOZd1C+ZstnCg7QLZ2luapjvTe+j1pKaQzLhuUC+TGw52oW+wMClHgsSks+g+
ihteTniX0/H3iJ2Y5WqrAkJM4BnPd3pQ2G127K1x4iUleKP8cj6ljT4jp6ApVD9I
UnA9VD5DwQYgbQIDAQABo2MwYTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/BAUw
AwEB/zAdBgNVHQ4EFgQUfn6NxFBVtS7TT1nZZVmh8VoM6rEwHwYDVR0jBBgwFoAU
QySNcBUIYlWcTwxAF12GXg+iTPswDQYJKoZIhvcNAQEFBQADggEBALa2wymjPg9B
oNhaIaOmvWgcGWEHYue0MNm+il1vnvR5xIkJu+7I+VkIElut0ng3546ExbnC36p3
xLr+phfIxqMqkjxM5PqSxt8b/qzPwRGIh0KNpTZQbg0MZKTpMcF7tsIREg6aV9yb
JiumHAtJPj5JmpNSUNr6DmQdfm3q+8IJxW9w17OOrT2ZlAN/tNuBqjBrcAQ1qLar
gILgMbNj8Tr6prjdOOvRZk3Z/Riej0HdzVdRYyTNBU4gnohBmv55/uLd1AyZzkbV
PeUPcICWLbzW5iQgY5y/CLpmiPiKUPVlLd2koc6XtWGvENg4EMcaSAVzCUyVVXWx
iM1ikzYwywE=
-----END CERTIFICATE-----

--(AlternativeBoundary)
Content-Type: application/pkix-cert; name="bossman.cs.hmc.edu.crt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="bossman.cs.hmc.edu.crt"
Content-Transfer-Encoding: 7bit

-----BEGIN CERTIFICATE-----
MIIGBDCCBOygAwIBAgIRAK2tFLjJnQ/5zpJiQTyPswwwDQYJKoZIhvcNAQEFBQAw
gdwxCzAJBgNVBAYTAkdCMRcwFQYDVQQKEw5Db21vZG8gTGltaXRlZDEdMBsGA1UE
CxMUQ29tb2RvIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25k
aXRpb25zIG9mIHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkx
HzAdBgNVBAsTFihjKTIwMDIgQ29tb2RvIExpbWl0ZWQxLDAqBgNVBAMTI0NvbW9k
byBDbGFzcyAzIFNlY3VyaXR5IFNlcnZpY2VzIENBMB4XDTAyMDcwNDAwMDAwMFoX
DTAzMDcwNDIzNTk1OVowggGdMQswCQYDVQQGEwJVUzEOMAwGA1UEERMFOTE3MTEx
EzARBgNVBAgTCkNhbGlmb3JuaWExEjAQBgNVBAcTCUNsYXJlbW9udDEcMBoGA1UE
CRMTQ2xhcmVtb250IENBLCA5MTcxMTEdMBsGA1UECRMUMjYwIEUuIEZvb3RoaWxs
IEJsdmQxHDAaBgNVBAoTE0hhcnZleSBNdWRkIENvbGxlZ2UxEzARBgNVBAsTCklu
c3RhbnRTU0wxOTA3BgNVBAsTMElzc3VlZCB0aHJvdWdoIGhhcnZleSBtdWRkIGNv
bGxlZ2UgRS1QS0kgTWFuYWdlcjFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlv
bnMgb2YgdXNlOiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0G
A1UECxMWKGMpMjAwMSBDb21vZG8gTGltaXRlZDEkMCIGA1UECxMbQ29tcHV0ZXIg
U2NpZW5jZSBEZXBhcnRtZW50MRswGQYDVQQDExJib3NzbWFuLmNzLmhtYy5lZHUw
gZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANqtGVGjnjOei8UaJzUuD7oEC25z
0VpxOjdpwSvkHDStQ5OmLBC5fswE5VpP6rewKm7N3sR9iaIWxcuKDaE0ECrdIamm
F5ndDpXRopAk4vJhOKF5PUvF+KRoWPFQTY0mT1Gofr8FCKZVKUw2tYKZzi3eJw7d
c7TnRZL6C/s3JMMBAgMBAAGjggF/MIIBezAfBgNVHSMEGDAWgBR+fo3EUFW1LtNP
WdllWaHxWgzqsTAdBgNVHQ4EFgQU+aP2ZUGhnv7BZtak2QJKEAxA2VIwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwRgYD
VR0gBD8wPTA7BgwrBgEEAbIxAQIBAwQwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9z
ZWN1cmUuY29tb2RvLm5ldC9DUFMwgaoGA1UdHwSBojCBnzA2oDSgMoYwaHR0cDov
L2NybC5jb21vZG8ubmV0L0NsYXNzM1NlY3VyaXR5U2VydmljZXMuY3JsMDigNqA0
hjJodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DbGFzczNTZWN1cml0eVNlcnZpY2Vz
LmNybDAroCmgJ4ElQ2xhc3MzU2VjdXJpdHlTZXJ2aWNlc0BjcmwuY29tb2RvLm5l
dDARBglghkgBhvhCAQEEBAMCBkAwDQYJKoZIhvcNAQEFBQADggEBADTJ1WgG1o2+
ElytXkrOhX6Vd0aGewp3qAzu0Zr6W0m2WiKF6wXRPnx44ZMfjw7xVBMwe9TRVX5M
unrMj49PIqvfIZCFr1/tieLiLuFfc2ydes1u5OlsOzyB3F+WQYnLt1HWLJTZTK2x
vqpX2Pb3DDrcd347JwVmmQgUhlpv6LlyPFOI9lJ00T7clO0c6o7C7DOio6nhmUr6
9dPLcSkqdrLmAX0o3mcdt5wFVt/XtANywVCJC+OaZimV64SsEEvGAZ4c8ir3JhVf
WIyBMsVWyT+Ogl91h+8Tz5i43JQwQQ3NU4zSp8m3/0RKe90S2xFxm5tvqXB8KcGZ
Myw1hrDtHaA=
-----END CERTIFICATE-----

--(AlternativeBoundary)--

--liOOAslEiF7prFVr--



From idwg-public-request@semper.org  Mon Jul 22 12:42:04 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14005
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 12:42:04 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id D754F34844; Mon, 22 Jul 2002 18:42:05 +0200 (CEST)
Old-Return-Path: <tep@SDSC.EDU>
Delivered-To: semper-idwg-public@opencard.org
Date: Mon, 22 Jul 2002 09:41:43 -0700
Message-Id: <200207221641.g6MGfhp03202@lart.sdsc.edu>
From: Tom Perrine <tep@SDSC.EDU>
To: mike@cs.hmc.edu
Cc: idwg-public@zurich.ibm.com
In-Reply-To: <20020722150334.GB26249@cs.hmc.edu> (message from Mike Erlinger
	on Mon, 22 Jul 2002 08:03:34 -0700)
Subject: Re: [support@comodo.net: ORDER #13898 - IMPORTANT INFORMATION]
X-Organization: San Diego Supercomputer Center, San Diego, California
X-Sbforce: tep@sdsc.edu
References:  <20020722150334.GB26249@cs.hmc.edu>
Resent-Message-ID: <dGQyoC.A.7CF.dXDP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/530
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 22 Jul 2002 18:42:05 +0200 (CEST)

Of course, now all the certificates are worthless.....

-- 
Tom E. Perrine <tep@SDSC.EDU> | San Diego Supercomputer Center 
http://www.sdsc.edu/~tep/     | 



From idwg-public-request@semper.org  Mon Jul 22 12:49:08 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14995
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 12:49:08 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id C81E234844; Mon, 22 Jul 2002 18:49:49 +0200 (CEST)
Old-Return-Path: <jeff@tcnet.org>
Delivered-To: semper-idwg-public@opencard.org
Date: Mon, 22 Jul 2002 12:49:01 -0400 (EDT)
From: Jeff <jeff@tcnet.org>
To: Tom Perrine <tep@SDSC.EDU>
Cc: mike@cs.hmc.edu, <idwg-public@zurich.ibm.com>, <idwg-public@semper.org>
Subject: Re: [support@comodo.net: ORDER #13898 - IMPORTANT INFORMATION]
In-Reply-To: <200207221641.g6MGfhp03202@lart.sdsc.edu>
Message-ID: <Pine.LNX.4.44.0207221244100.22329-100000@hendryx.tcnet.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-Message-ID: <3FiH0.A.ERF.teDP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/531
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 22 Jul 2002 18:49:49 +0200 (CEST)


On Mon, 22 Jul 2002, Tom Perrine wrote:

> Of course, now all the certificates are worthless.....

Hardly. You've just become one of the many on this list to obtain early
access to them. The private key is (presumably) still secure on
bossman.cs.hmc.edu, and the certificates that were attached to the
original message are all public. Not really all that much different than
if you had connected to https://bossman.cs.hmc.edu/ after the
certificate(s) had been installed (this assumes that the cert is intended
for HTTP over SSL/TLS).

If the certificates were private/sensitive data, do you think that the CA
would mail them in plaintext? :)

-jeff

-- 
Jeff Godin
Network Specialist
Traverse Area District Library / Traverse Community Network
jeff@tcnet.org




From idwg-public-request@semper.org  Mon Jul 22 13:07:22 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17125
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 13:07:22 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id AFCE334842; Mon, 22 Jul 2002 19:08:03 +0200 (CEST)
Old-Return-Path: <mike@cs.hmc.edu>
Delivered-To: semper-idwg-public@opencard.org
Date: Mon, 22 Jul 2002 10:07:41 -0700
From: Mike Erlinger <mike@cs.hmc.edu>
To: intrusion detection wg <idwg-public@zurich.ibm.com>
Subject: Miss directed email
Message-Id: <20020722170741.GA3167@cs.hmc.edu>
Reply-To: mike@cs.hmc.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Resent-Message-ID: <Zk0UsB.A.FgF.zvDP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/532
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 22 Jul 2002 19:08:03 +0200 (CEST)

Early this morning i miss-directed an email about a certificate from
comodo.  the email was meant to go to a local list of people working
on an implementation of idmef/idxp.  

At least the email has generated some idwg mail list activity :-)

FYI, we are working on creating a complete implementation of idmef/idxp.
By the end of the summer I hope to have a paper that describes our work
and pointers to available code.

Sorry about the spam.

mike

-- 
Mike Erlinger, Professor and Chair Computer Science
www:      http://www.cs.hmc.edu/~mike
email:    mike@cs.hmc.edu
smail:    Computer Science Dept., Harvey Mudd College,
          301 E. 12th Street, Claremont, CA, 91711 
          909-621-8912,   FAX: 909-607-8364



From idwg-public-request@semper.org  Mon Jul 22 14:37:09 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26137
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 14:37:09 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id B107A34844; Mon, 22 Jul 2002 20:37:46 +0200 (CEST)
Old-Return-Path: <ltinnel@teknowledge.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <5.1.0.14.2.20020722141517.043c7070@mahi.dc.teknowledge.com>
X-Sender: ltinnel@mahi.dc.teknowledge.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 22 Jul 2002 14:35:28 -0400
To: idwg-public@zurich.ibm.com
From: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Subject: Problem reporting PIDs with IDMEF
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-Message-ID: <F8TLmB.A.DIG.6DFP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/533
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 22 Jul 2002 20:37:46 +0200 (CEST)

We are in the midst of an experiment that uses IDMEF 0.3 (ack!) for a bunch 
of sensors that report alerts to a single collection point. During the 
course of our preparation, we discovered that Windows 2000 at times reports 
very *large* numbers for new process IDs. The host based sensor that 
analyzes the Windows audit trail accurately reports the PID according to 
the log (I will not comment on the validity of the Windows log!!) The 
problem is that the IDMEF spec states that PIDs are of type integer, and 
the number is larger than that which can be stored in an integer on the 
alert collection host (Sparc Ultra 5 with Solaris 2.7).

Couple of questions. 1. Is there a particular reason that type "integer" 
was chosen? It would seem that "unsigned" would be better since operating 
systems tend to use positive numbers for PIDs. 2. The actual size of an 
integer is platform dependent. This is problematic in a networked 
heterogeneous environment. How do you propose handling situations where an 
integer value is valid on one host and sent to another where it is too 
large a value and considered invalid?

Thanks,
Laura



From idwg-public-request@semper.org  Mon Jul 22 15:00:34 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28297
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 15:00:34 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 9656434845; Mon, 22 Jul 2002 21:01:15 +0200 (CEST)
Old-Return-Path: <davy@cynicus.net>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <200207221900.g6MJ0Ld23518@intrepid.cynicus.net>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
To: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Cc: idwg-public@zurich.ibm.com
Subject: Re: Problem reporting PIDs with IDMEF 
In-Reply-To: <5.1.0.14.2.20020722141517.043c7070@mahi.dc.teknowledge.com> 
Comments: reply to message from "Laura S. Tinnel" <ltinnel@teknowledge.com> 
          dated Mon, 22 Jul 2002 14:35:28 EDT
Date: Mon, 22 Jul 2002 15:00:21 -0400
From: "David A. Curry" <davy@cynicus.net>
Resent-Message-ID: <D8F-1B.A.hUG.7ZFP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/534
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 22 Jul 2002 21:01:15 +0200 (CEST)



>>>>> On Mon, 22 Jul 2002, Laura S. Tinnel, identified as "Laura" below, wrote:

  Laura> Couple of questions. 1. Is there a particular reason that type
  Laura> "integer" was chosen? It would seem that "unsigned" would be better
  Laura> since operating systems tend to use positive numbers for PIDs. 2. The
  Laura> actual size of an integer is platform dependent. This is problematic
  Laura> in a networked heterogeneous environment. How do you propose handling
  Laura> situations where an integer value is valid on one host and sent to
  Laura> another where it is too large a value and considered invalid?

1. Remember, XML doesn't actually have types.  The only reason we identified
   types for things at all was just to make it clear, for example, that we
   expect an integer-ype datum here, as opposed to say, a string.

   In hindsight, your point about unsigned is a good one, although since we
   do not specify minimum or maximum values for those sorts of data, I'm not
   sure it would ultimately make any difference (you can always find a size
   it won't fit in).

2. "Be conservative in what you send, and liberal in what you accept."  :-)

You could certainly use an unsigned, if you wanted to.  Or, put it out in
hexadecimal and don't worry about the sign.

I will point out that "0.3" is a pretty old version of IDMEF.  You might want
to think about getting a newer one, depending on how far along you are.

--Dave



From idwg-public-request@semper.org  Mon Jul 22 19:20:47 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20627
	for <idwg-archive@odin.ietf.org>; Mon, 22 Jul 2002 19:20:46 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 2E7B634798; Tue, 23 Jul 2002 01:21:27 +0200 (CEST)
Old-Return-Path: <ltinnel@teknowledge.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <5.1.0.14.2.20020722152942.043c7070@192.168.100.10>
X-Sender: ltinnel@192.168.100.10
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 22 Jul 2002 19:20:27 -0400
To: "David A. Curry" <davy@cynicus.net>
From: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Subject: Re: Problem reporting PIDs with IDMEF
Cc: idwg-public@zurich.ibm.com
In-Reply-To: <200207221900.g6MJ0Ld23518@intrepid.cynicus.net>
References: <5.1.0.14.2.20020722141517.043c7070@mahi.dc.teknowledge.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-Message-ID: <YGYtzD.A.2nG.3NJP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/535
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Tue, 23 Jul 2002 01:21:27 +0200 (CEST)

At 03:00 PM 7/22/2002, David A. Curry wrote:
>1. Remember, XML doesn't actually have types.  The only reason we identified
>    types for things at all was just to make it clear, for example, that we
>    expect an integer-ype datum here, as opposed to say, a string.

Yes. But unfortunately if you say "integer", people think that's what you 
mean. It would appear that folks appear to be taking it at face value and 
encoding the internal parsing of their software based on the spec. E.g., we 
use the JHU APL JavaIDMEF software. It throws an exception if you pass in a 
number that won't fit in an integer. Perhaps it would be better to say it's 
a numeric value and don't use well defined types that one might accidently 
interpret as the actual type to be encoded.

>    In hindsight, your point about unsigned is a good one, although since we
>    do not specify minimum or maximum values for those sorts of data, I'm not
>    sure it would ultimately make any difference (you can always find a size
>    it won't fit in).

>2. "Be conservative in what you send, and liberal in what you accept."  :-)

Unfortunately we cannot control what an operating system encodes as a PID, 
so we cannot be conservative in what we send exactly. Basically our 
(hopefully temporary) work-around is to set the PID to -1 (since it IS 
signed) and to use AdditionalData of type string to encode the actual value.

>You could certainly use an unsigned, if you wanted to.  Or, put it out in
>hexadecimal and don't worry about the sign.

Ummm... the spec says integer, not hex. So that's what folks expect. I 
understand that XML natively doesn't actually enforce this stuff, but a DTD 
should. Any software compliant with the DTD must enforce what it says. 
We're developing plug-and-play sensor/alert collector/correlator software 
around IDMEF. That IS the purpose of IDMEF, right??? If we use hex, then 
other software will not expect hex because the spec says integer. That 
means our system is technically not compliant with the spec and won't be 
plug-and-play. The spec needs to clearly define what it expects to see in 
these fields. People must be able to develop software knowing what to 
expect based on what the spec says. Otherwise, IDMEF is useless for the 
purpose of integrating heterogeneous sensors.

>I will point out that "0.3" is a pretty old version of IDMEF.  You might want
>to think about getting a newer one, depending on how far along you are.

Yes. We're well aware and very much want to move to a newer version. 
Unfortunately when we got started on this, 0.3 was the latest. We plan to 
move to 0.7 (or newer if available) but cannot do so until this experiment 
is completed.

-Laura



From idwg-public-request@semper.org  Tue Jul 23 08:03:50 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07015
	for <idwg-archive@lists.ietf.org>; Tue, 23 Jul 2002 08:03:50 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 9EAE034798; Tue, 23 Jul 2002 14:04:20 +0200 (CEST)
Old-Return-Path: <ltinnel@teknowledge.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <5.1.0.14.2.20020723073435.0a2e1120@192.168.100.10>
X-Sender: ltinnel@192.168.100.10
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 23 Jul 2002 08:03:59 -0400
To: "Sims, Rayford" <Rayford.Sims.02@McKenna.edu>
From: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Subject: RE: Problem reporting PIDs with IDMEF
Cc: "'David A. Curry '" <davy@cynicus.net>,
        "'idwg-public@zurich.ibm.com '" <idwg-public@zurich.ibm.com>
In-Reply-To: <C8B79FB0EC51C743889E90259C6209A901CA3805@mss2-mach.MCKENNA
 .EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-Message-ID: <aBKS_.A.tbH.EZUP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/536
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Tue, 23 Jul 2002 14:04:20 +0200 (CEST)

At 01:33 AM 7/23/2002, Sims, Rayford wrote:
> >Ummm... the spec says integer, not hex. So that's what folks expect. I
> >understand that XML natively doesn't actually enforce this stuff, but a
> >DTD should.
>
>If I recall correctly the spec specifically says that an INTEGER may be
>encoded in base10 or base16.  It is not for the DTD to enforce dataypes,
>since XML specifically prevents this, but the full specification does say
>waht the datatypes should mean and every compliant parser should enforce
>this.

You are right. I went back to section 4.4.1 and it does state base16 as 
being OK. I missed that. As long as it states that you can use either, then 
software must be written to expect either. This is fine because it clearly 
states the two formats expected. What isn't fine is that it does not bound 
the values.

>I believe that this is a problem with the IDMEF libraries that you are
>using.

It is a problem in that they used the type "integer" internally (that's 
what the spec said, after all...) and tried to take the numeric string 
inside the <PID> tags and stuff it into the integer. Well... this doesn't 
work too well when the actual number is larger than what can be stored in 
the integer type on that platform.

>To be sure, it would not be a bad idea for the spec to define the
>range of these values, however just because the spec uses the word INTEGER
>it is not necessary that this fit into a 32 bit integer.

Yep. One can always come up with a value that can exceed what the storage 
is capable of representing. Obviously some error checking in the library we 
are using would have been desirable. I'm just trying to point out that the 
spec should be clear on the bounds of what can be expected in fields of 
various types. Then folks can write software that is compliant AND 
interoperable.

>I do agree
>however, that the word INTEGER is misleading.
>
>As David points out, the use of a hex value would avoid this problem and it
>owuld not be a violation of the spec.
>
> >Basically our (hopefully temporary) work-around is to set the PID to -1
> >(since it IS signed) and to use AdditionalData of type string to encode
> >the actual value.
>
>This is a good work around.  Again I think that the long term solution is
>for the JavaIDMEF software to conform to the full letter of the spec and to
>support hex PIDs if it does not already.

It may. We didn't try this.

>I don't mean to send you away to someone else for help with your problem,
>but although the spec is somewhat ambiguous it does state that hex values
>are to be supported.

I'm not looking for help with my problem. I've already found something that 
will work. I am trying to make the authors of the spec recognize and fix 
what I perceive to be a deficiency in IDMEF from the actual use of it in a 
real distributed system as opposed to just reviewing a document. If you 
want IDMEF to get better and be adopted and used by the community, you need 
this kind of feedback.

>If the javaIDMEF software doesn't support this you
>should take it up with the authors of that software.

It is no longer supported. It implements IDMEF 0.3. We are going to have to 
do a rewrite just to move to 0.7.

>But I do think that we should have some talk about bounding these values or
>using only base16 encoding to disambiguate this some or not using the word
>integer.  Let me know what you all think.

My vote would be to not use the word integer as it is very misleading. 
Instead state that it is a numeric value represented in either base10 or 
base16 that falls within some defined range. Alternatively you could state 
that it is a 16-bit (or 32-bit - choose) integer (better - for PIDs to be 
unsigned). Then it is up to the software to be able to handle it 
appropriately based on their platform. At least code developers will be 
told explicitly what to expect and know what to write.

-L
p.s. Hey Mike - here's your mailing list traffic....




From idwg-public-request@semper.org  Tue Jul 23 09:49:57 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11917
	for <idwg-archive@lists.ietf.org>; Tue, 23 Jul 2002 09:49:57 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 792BB34846; Tue, 23 Jul 2002 15:50:37 +0200 (CEST)
Old-Return-Path: <davy@cynicus.net>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <200207231348.g6NDmrU02597@intrepid.cynicus.net>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
To: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Cc: "Sims, Rayford" <Rayford.Sims.02@McKenna.edu>,
        "'idwg-public@zurich.ibm.com '" <idwg-public@zurich.ibm.com>
Subject: Re: Problem reporting PIDs with IDMEF 
In-Reply-To: <5.1.0.14.2.20020723073435.0a2e1120@192.168.100.10> 
References: <C8B79FB0EC51C743889E90259C6209A901CA3805@mss2-mach.MCKENNA.EDU> 
            <5.1.0.14.2.20020723073435.0a2e1120@192.168.100.10> 
Comments: reply to message from "Laura S. Tinnel" <ltinnel@teknowledge.com> 
          dated Tue, 23 Jul 2002 08:03:59 EDT
Date: Tue, 23 Jul 2002 09:48:53 -0400
From: "David A. Curry" <davy@cynicus.net>
Resent-Message-ID: <WxPoZD.A.4E.t8VP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/537
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Tue, 23 Jul 2002 15:50:37 +0200 (CEST)


Just to be difficult, I will point out that when we all learned what an
"integer" was in elementary school, we didn't learn anything about 32
bits.  Integers are the set of positive whole numbers, negative whole
numbers, and zero.  When the IDMEF specification says "integer," that's
what it means.  :-)

I will agree with Laura, though, that the specification is not clear on
what developers should do.  However, I'm very hesitant to go through and
say "32 bits" or "16 bits" or whatever -- we're bound to get something
wrong and cause more problems (e.g., what if we had said "16 bits" for
PID?).

I would instead be inclined to specifically state that we are not going
to specify a min/max value for these types, and that implementors should
be prepared to deal with this -- use the largest "reasonable" data types
they can, and have some way to handle values that cannot fit in those
types without failing.

Thoughts?

On a separate note, I'm still curious about Laura's more-than-32-bit PIDs.
Win2k is a 32-bit o/s, right?  So unless they're using 64-bit data types
for PIDs (which seems unlikely), PIDs should fit in 32 bits.  Laura, are
you sure the data you're getting (or the things reporting the data) aren't
broken?  (Of course, even if they are broken, you may not be able to do
anything about it.)

--Dave



From idwg-public-request@semper.org  Tue Jul 23 11:26:36 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17534
	for <idwg-archive@odin.ietf.org>; Tue, 23 Jul 2002 11:26:35 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 4A2EB34844; Tue, 23 Jul 2002 17:27:16 +0200 (CEST)
Old-Return-Path: <ltinnel@teknowledge.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <5.1.0.14.2.20020723110916.043c7070@192.168.100.10>
X-Sender: ltinnel@192.168.100.10
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 23 Jul 2002 11:26:08 -0400
To: "David A. Curry" <davy@cynicus.net>
From: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Subject: Re: Problem reporting PIDs with IDMEF
Cc: "Sims, Rayford" <Rayford.Sims.02@McKenna.edu>,
        "'idwg-public@zurich.ibm.com '" <idwg-public@zurich.ibm.com>
In-Reply-To: <200207231348.g6NDmrU02597@intrepid.cynicus.net>
References: <5.1.0.14.2.20020723073435.0a2e1120@192.168.100.10>
 <C8B79FB0EC51C743889E90259C6209A901CA3805@mss2-mach.MCKENNA.EDU>
 <5.1.0.14.2.20020723073435.0a2e1120@192.168.100.10>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-Message-ID: <Gow9d.A.0U.UXXP9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/538
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Tue, 23 Jul 2002 17:27:16 +0200 (CEST)

At 09:48 AM 7/23/2002, David A. Curry wrote:
>On a separate note, I'm still curious about Laura's more-than-32-bit PIDs.
>Win2k is a 32-bit o/s, right?  So unless they're using 64-bit data types
>for PIDs (which seems unlikely), PIDs should fit in 32 bits.  Laura, are
>you sure the data you're getting (or the things reporting the data) aren't
>broken?  (Of course, even if they are broken, you may not be able to do
>anything about it.)

I'm pretty sure it's broken. I've never seen a valid PID that couldn't fit 
in a 16-bit integer. This is the PID as reported in the Windows 2000 event 
log after a buffer overflow attack. Enough said. :-(



From idwg-public-request@semper.org  Fri Jul 26 10:57:40 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23470
	for <idwg-archive@odin.ietf.org>; Fri, 26 Jul 2002 10:57:39 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id D970534843; Fri, 26 Jul 2002 16:58:15 +0200 (CEST)
Old-Return-Path: <Benjamin.Feinstein@guardent.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <397E0659AA2DD411843500508B64F1CE0431030A@USBOSMX01>
From: Benjamin.Feinstein@guardent.com
To: idwg-public@zurich.ibm.com
Cc: glenn@cysols.com
Subject: IDXP status
Date: Fri, 26 Jul 2002 10:59:28 -0400
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Resent-Message-ID: <6p2wP.A.tOG.GOWQ9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/539
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Fri, 26 Jul 2002 16:58:15 +0200 (CEST)

I have made all the updates I am planning to make, and have posted them in
the draft-ietf-idwg-beep-idxp-05 memo of June 17, 2002. The last unresolved
issue of Glenn's is shown below. Unless I hear anything to support Glenn or
requests to change the wording, the IDXP memo will stay the way it is.

On Mon, 24 Jun 2002, Glenn Mansfield Keeni wrote:
>  > GMK  4. Sec 5 Page 21
>  > ID    The [protocol] SHOULD be able to ensure non-repudiation of the
>  > ID    origin of IDMEF messages.
>  > ID
>  > ID        IDXP supports non-repudiation of message origin through the
use
>  > ID        of an appropriate underlying BEEP security profile.  The TLS
>  > ID        profile is an example of a security profile that offers non-
>  > ID        repudiation of message origin through the authentication of
>  >
>  > GMK  The above may be misleading. It is not clear how this will be
done.
>  > GMK  To my knowledge TLS does not guarantee non-repudiation of message
>  > GMK  origin. (It can ensure non repudiation of TLS session origination
>  > GMK  - but that does not ensure non-repudiation of message origin.).
This
>  > GMK  is probably a message content matter and thus beyond the
communication
>  > GMK  protocol.
>  >
>  > BSF  Point taken.  I've rewritten this section, hopefully more to
>  > BSF  Glenn's liking.
> Unfortunately not. non-repudiation of message origin cannot be done by
> BEEP/IDXP. And non-repudiation of session origin is not what is sought.
> I would recommend that you drop this. And maybe it should be dropped as
> from the (protocol) requirement document too.

> Ben Feinstein
>   Software Development Engineer, R & D
>   W: 678.585.7865 x6726 F: 770.645.8311 M: 678.772.4126
>   8302 Dunwoody Pl., Suite 320, Atlanta, GA 30350 www.guardent.com
> _____________________________________________________
> G U A R D E N T
>   Enterprise Security and Privacy Programs
> 



From idwg-public-request@semper.org  Mon Jul 29 10:22:30 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00934
	for <idwg-archive@odin.ietf.org>; Mon, 29 Jul 2002 10:22:29 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id A0964347FA; Mon, 29 Jul 2002 16:23:11 +0200 (CEST)
Old-Return-Path: <jccw@mitre.org>
Delivered-To: semper-idwg-public@opencard.org
Date: Mon, 29 Jul 2002 10:22:31 -0400
Subject: Re: IDXP status
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: idwg-public@zurich.ibm.com
To: Benjamin.Feinstein@guardent.com
From: John White <jccw@mitre.org>
In-Reply-To: <397E0659AA2DD411843500508B64F1CE0431030A@USBOSMX01>
Message-Id: <9E970258-A2FE-11D6-A61A-00039383E392@mitre.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Resent-Message-ID: <XOyDu.A.lKE.P_UR9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/540
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 29 Jul 2002 16:23:11 +0200 (CEST)
Content-Transfer-Encoding: 7bit

My belief is that your rewrite is accurate as it stands, and should stay 
that way. If I understand Glenn's issue correctly, he is saying that 
the  requirements document calls for our protocol to do something that a 
protocol simply cannot do. An alternative view would be that we 
interpret the requirements document to have stated the requirement 
rather poorly, and that our protocol does what it "really" meant. I 
think the latter view makes sense at this point.

-John-

On Friday, July 26, 2002, at 10:59 AM, Benjamin.Feinstein@guardent.com 
wrote:

> I have made all the updates I am planning to make, and have posted them 
> in
> the draft-ietf-idwg-beep-idxp-05 memo of June 17, 2002. The last 
> unresolved
> issue of Glenn's is shown below. Unless I hear anything to support 
> Glenn or
> requests to change the wording, the IDXP memo will stay the way it is.
>
> On Mon, 24 Jun 2002, Glenn Mansfield Keeni wrote:
>>> GMK  4. Sec 5 Page 21
>>> ID    The [protocol] SHOULD be able to ensure non-repudiation of the
>>> ID    origin of IDMEF messages.
>>> ID
>>> ID        IDXP supports non-repudiation of message origin through the
> use
>>> ID        of an appropriate underlying BEEP security profile.  The TLS
>>> ID        profile is an example of a security profile that offers non-
>>> ID        repudiation of message origin through the authentication of
>>>
>>> GMK  The above may be misleading. It is not clear how this will be
> done.
>>> GMK  To my knowledge TLS does not guarantee non-repudiation of message
>>> GMK  origin. (It can ensure non repudiation of TLS session origination
>>> GMK  - but that does not ensure non-repudiation of message origin.).
> This
>>> GMK  is probably a message content matter and thus beyond the
> communication
>>> GMK  protocol.
>>>
>>> BSF  Point taken.  I've rewritten this section, hopefully more to
>>> BSF  Glenn's liking.
>> Unfortunately not. non-repudiation of message origin cannot be done by
>> BEEP/IDXP. And non-repudiation of session origin is not what is sought.
>> I would recommend that you drop this. And maybe it should be dropped as
>> from the (protocol) requirement document too.
>
>> Ben Feinstein
>>   Software Development Engineer, R & D
>>   W: 678.585.7865 x6726 F: 770.645.8311 M: 678.772.4126
>>   8302 Dunwoody Pl., Suite 320, Atlanta, GA 30350 www.guardent.com
>> _____________________________________________________
>> G U A R D E N T
>>   Enterprise Security and Privacy Programs
>>
>




From idwg-public-request@semper.org  Mon Jul 29 11:21:20 2002
Received: from www.opencard.org (www.opencard.org [195.176.20.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03657
	for <idwg-archive@odin.ietf.org>; Mon, 29 Jul 2002 11:21:19 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id B4DB134842; Mon, 29 Jul 2002 17:22:09 +0200 (CEST)
Old-Return-Path: <Benjamin.Feinstein@guardent.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <397E0659AA2DD411843500508B64F1CE04310311@USBOSMX01>
From: Benjamin.Feinstein@guardent.com
To: idwg-public@zurich.ibm.com
Cc: jccw@mitre.org
Subject: non-repudiation of message origin
Date: Mon, 29 Jul 2002 11:23:58 -0400
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Resent-Message-ID: <-3RVND.A.0YE.h2VR9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/541
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 29 Jul 2002 17:22:09 +0200 (CEST)

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just as an FYI, here is the text from Section 5 of the current
draft-ietf-idwg-beep-idxp-05:

   The [protocol] SHOULD be able to ensure non-repudiation of the
origin
   of IDMEF messages.

      IDXP supports non-repudiation of session origin through the use
of
      an appropriate underlying BEEP security profile.  An IDXP peer
      application MAY use IDMEF content and/or BEEP session
credentials
      to provide for non-repudiation of message origin.  The TLS
profile
      is an example of a security profile that offers non-repudiation
of
      session origin through the authentication of public-key
      certificates.  TLS MUST be offered as a mechanism to provide
non-
      repudiation of session origin, and TLS SHOULD be used to
provide
      non-repudiation of session origin.

Cheers,
Ben

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA+AwUBPUVfYPt7bOk+HH2bEQKkegCeObX5TFBMvZ9G512ivEAvHF7aEbgAkwTG
MKDB+AA63HHd+rmmkZx5J4c=
=90bI
-----END PGP SIGNATURE-----



