1 INFO-VAX	Tue, 20 Jun 2006	Volume 2006 : Issue 341       Contents:( Data format of audit's listener mailbox?, Re: Data format of audit's listener mailbox?, Re: Data format of audit's listener mailbox? [VMS 7.3-2] UPDATE ECO 7 is out # Re: [VMS 7.3-2] UPDATE ECO 7 is out # Re: [VMS 7.3-2] UPDATE ECO 7 is out  [VMS 8.2] UPDATE ECO 3 is out ! Re: [VMS 8.2] UPDATE ECO 3 is out ! Re: [VMS 8.2] UPDATE ECO 3 is out ! Re: [VMS 8.2] UPDATE ECO 3 is out   F ----------------------------------------------------------------------   Date: 20 Jun 2006 09:17:01 GMT7 From: yehavi@vms.huji.ac.il (Yehavi Bourvine (58-4279)) 1 Subject: Data format of audit's listener mailbox? % Message-ID: <2006Jun20.091701@hujicc>    Hello,  J   I would like to monitor the audit events in real-time in order to locate5 break-in attempts to my system and react accordingly.   K   In the security manual I see a reference to listener mailbox to which the E audit server can send records to. However, there is no description of . the data format. Any idea where I can find it?    B                                                  Thanks! __Yehavi:   ------------------------------    Date: 20 Jun 2006 02:08:23 -0700  From: "Ian Miller" <ijm@uk2.net>5 Subject: Re: Data format of audit's listener mailbox? B Message-ID: <1150794503.166860.83520@h76g2000cwa.googlegroups.com>   See this exampleO http://h18000.www1.hp.com/support/asktima/appl_tools/CHAMP_SRC931102006764.html    ------------------------------  % Date: Tue, 20 Jun 2006 07:05:47 -0700 ( From: Jeff Cameron <roktsci@comcast.net>5 Subject: Re: Data format of audit's listener mailbox? 0 Message-ID: <C0BD4ECB.21AAC%roktsci@comcast.net>  H On 6/20/06 2:17 AM, in article 2006Jun20.091701@hujicc, "Yehavi Bourvine' 58-4279" <yehavi@vms.huji.ac.il> wrote:    > Hello, > L >   I would like to monitor the audit events in real-time in order to locate7 > break-in attempts to my system and react accordingly.  > M >   In the security manual I see a reference to listener mailbox to which the G > audit server can send records to. However, there is no description of 0 > the data format. Any idea where I can find it? >  > D >                                                  Thanks! __Yehavi:  K You use the system service called SYS$FORMAT_AUDIT, which reads this record B and allows you to pull out the desired information. You can find a4 description in the System services Reference manual:H http://h71000.www7.hp.com/doc/732FINAL/4527/4527pro_004.html#index_x_532   Jeff Cameron   ------------------------------    Date: 20 Jun 2006 13:23:27 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)( Subject: [VMS 7.3-2] UPDATE ECO 7 is out* Message-ID: <4497f6cf@news.langstoeger.at>  K As you may already have noticed, the quarterly wave of UPDATE ECOs arrived. " And I already found discrepancies.   eg. Q ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/ALPHA_V732_MASTER_ECO_LIST.txt I states that VMS732_LOADSS-V0200 is included/superceded by UPDATE V7 while J ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_UPDATE-V0700.txt9 states that it includes VMS732_LOADSS-V0100 (and not V2).    Which is the correct one?    TIA    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Tue, 20 Jun 2006 09:41:32 -0400  From: norm.raphael@metso.com, Subject: Re: [VMS 7.3-2] UPDATE ECO 7 is outQ Message-ID: <OF676094F9.71E21241-ON85257193.004B2FB4-85257193.004B2439@metso.com>    If you would run $PRODUCT LIST  VMS732_UPDATE answer the questions% and check the ".RELEASE_NOTES" files,  you could tell us.  D peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote on 06/20/2006 11:23:27 AM:  D > As you may already have noticed, the quarterly wave of UPDATE ECOs arrived.$ > And I already found discrepancies. >  > eg. 1 > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7. $ > 3-2/ALPHA_V732_MASTER_ECO_LIST.txtK > states that VMS732_LOADSS-V0200 is included/superceded by UPDATE V7 while  > J ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_UPDATE-V0700.txt; > states that it includes VMS732_LOADSS-V0100 (and not V2).  >  > Which is the correct one?  >  > TIA  >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 20 Jun 2006 07:42:07 -0700; From: "george.pagliarulo@hp.com" <george.pagliarulo@hp.com> , Subject: Re: [VMS 7.3-2] UPDATE ECO 7 is outC Message-ID: <1150814527.271972.255130@b68g2000cwa.googlegroups.com>    Hello Peter,  D The Master list is in error.  A new one will be loaded tonight.  The( UPDATE kit contains VMS732_LOADSS-V0100.   George Pagliarulo       Peter 'EPLAN' LANGSTOEGER wrote:M > As you may already have noticed, the quarterly wave of UPDATE ECOs arrived. $ > And I already found discrepancies. >  > eg. S > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/ALPHA_V732_MASTER_ECO_LIST.txt K > states that VMS732_LOADSS-V0200 is included/superceded by UPDATE V7 while L > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_UPDATE-V0700.txt; > states that it includes VMS732_LOADSS-V0100 (and not V2).  >  > Which is the correct one?  >  > TIA  >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 20 Jun 2006 13:29:55 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)& Subject: [VMS 8.2] UPDATE ECO 3 is out, Message-ID: <4497f853$1@news.langstoeger.at>  K As you may already have noticed, the quarterly wave of UPDATE ECOs arrived. " And I already found discrepancies.   eg. O ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.2/ALPHA_V82A_MASTER_ECO_LIST.txt = states that VMS82A_OPCOM-V0100 is included in UPDATE V3 while H ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.2/VMS82A_UPDATE-V0300.txt doesn't list OPCOM.   G In sight of the OPCOM ECOs on other versions and on its release date, I 8 think OPCOM V1 is not included in UPDATE V3. Am I right?   TIA    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Tue, 20 Jun 2006 09:23:27 -0400  From: norm.raphael@metso.com* Subject: Re: [VMS 8.2] UPDATE ECO 3 is outQ Message-ID: <OF20E888F7.09A6844E-ON85257193.00498787-85257193.00497C3C@metso.com>    If you would run $PRODUCT LIST  VMS732_UPDATE answer the questions$ and check the ".RELEASE_NOTES files, you could tell us.  D peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote on 06/20/2006 11:29:55 AM:  D > As you may already have noticed, the quarterly wave of UPDATE ECOs arrived.$ > And I already found discrepancies. >  > eg. 1 > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8. " > 2/ALPHA_V82A_MASTER_ECO_LIST.txt? > states that VMS82A_OPCOM-V0100 is included in UPDATE V3 while J > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.2/VMS82A_UPDATE-V0300.txt > doesn't list OPCOM.  > I > In sight of the OPCOM ECOs on other versions and on its release date, I : > think OPCOM V1 is not included in UPDATE V3. Am I right? >  > TIA  >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Tue, 20 Jun 2006 09:22:24 -0400  From: norm.raphael@metso.com* Subject: Re: [VMS 8.2] UPDATE ECO 3 is outQ Message-ID: <OFA3A96B1E.FB655A1C-ON85257193.004971BD-85257193.004963E5@metso.com>    If you would run $PRODUCT LIST  VMS732_UPDATE answer the questions$ and check the ".RELEASE_NOTES files, you could tell us.  D peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote on 06/20/2006 11:29:55 AM:  D > As you may already have noticed, the quarterly wave of UPDATE ECOs arrived.$ > And I already found discrepancies. >  > eg. 1 > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8. " > 2/ALPHA_V82A_MASTER_ECO_LIST.txt? > states that VMS82A_OPCOM-V0100 is included in UPDATE V3 while J > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.2/VMS82A_UPDATE-V0300.txt > doesn't list OPCOM.  > I > In sight of the OPCOM ECOs on other versions and on its release date, I : > think OPCOM V1 is not included in UPDATE V3. Am I right? >  > TIA  >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 20 Jun 2006 07:50:27 -0700; From: "george.pagliarulo@hp.com" <george.pagliarulo@hp.com> * Subject: Re: [VMS 8.2] UPDATE ECO 3 is outC Message-ID: <1150815027.139450.277760@h76g2000cwa.googlegroups.com>    Peter,  C     Again, the master list is in error.  VMS82A_OPCOM-V0100 did not E ship in the VMS82A_UPDATE-V0300 kit.  It was originally placed in the E UPDATE kit and then removed.  This change did not get carried over to D the Master list.   A similar issue caused the LOADSS discrepancy.  A, new V82A Master List will be loaded tonight.   George Pagliarulo       Peter 'EPLAN' LANGSTOEGER wrote:M > As you may already have noticed, the quarterly wave of UPDATE ECOs arrived. $ > And I already found discrepancies. >  > eg. Q > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.2/ALPHA_V82A_MASTER_ECO_LIST.txt ? > states that VMS82A_OPCOM-V0100 is included in UPDATE V3 while J > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.2/VMS82A_UPDATE-V0300.txt > doesn't list OPCOM.  > I > In sight of the OPCOM ECOs on other versions and on its release date, I : > think OPCOM V1 is not included in UPDATE V3. Am I right? >  > TIA  >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   End of INFO-VAX 2006.341 ************************