0 INFO-VAX	Sun, 01 Feb 2004	Volume 2004 : Issue 62      Contents: Re: $SETUAI() Query/Problem  Re: $SETUAI() Query/Problem  Re: $SETUAI() Query/Problem  Re: $SETUAI() Query/Problem 0 Re: Canadian Troll infestation in rec.travel.air0 Re: Canadian Troll infestation in rec.travel.air0 Re: Canadian Troll infestation in rec.travel.air0 Re: Canadian Troll infestation in rec.travel.air Re: DCL questions . Does iSCSI infringe on any MSCP patents or IP?< Re: Flashing lights on my disk drives on an Alphaserver ES40 Re: Hobbyist questions? : Re: It is almost certain now, INTEL will have 64bit x86 !!: Re: It is almost certain now, INTEL will have 64bit x86 !!# Re: Jacques Chirac and JF M-e-z-e-i  Re: Jacques Chirac and JF Mezei  Re: JF's black helicopter world # Re: Mezei domain theft - nobody.com 0 Re: New Variant MyDoom.B targeting Microsoft.comJ Re: OpenVMS vs unix security ... Andrew, the IBM guy awaits your response! Re: Renaissance of VAX-VMS ?/ Re: The VMS Path Not Taken: Now It Can be Told!   F ----------------------------------------------------------------------  # Date: Sat, 31 Jan 2004 22:15:13 GMT # From: Jonas Lindholm <jlhm@usa.net> $ Subject: Re: $SETUAI() Query/Problem: Message-ID: <RNVSb.168539$4F2.19936568@twister.nyc.rr.com>  H Can you give us an example how you define SYSUAF and RIGHTSLIST logical - names on NODEA to access the files on NODEB ?   G Remember you need proxy access on NODEB if you don't also specify your  ) username and password in the definitions.    /Jonas  ! covendotartdottalk21dotcom wrote: @ > "Richard B. Gilbert" <rgilbert88@comcast.net> wrote in message, > news:ad6dnX9EqrC4eIfdRVn-hA@comcast.com... > F >>I seem to recall that the logicals used by SYSUAF must be defined inD >>EXECUTIVE_MODE.   They need not be in the system table but must beF >>/EXEC.  This applies to  SYSUAF, RIGHTSLIST, NETPROXY and NET$PROXY. >  > : > Unfortunately, I've tried /EXEC too, but still no cigar. > F > I'm loathe to temporarily remove the defintion from the system tableH > on my development system (because I'm not the only person who uses it,H > and deassigning it would cause a few login problems for everyone else,@ > let alone the batch jobs that run at unpredictable intervals). > E > However, it would at least prove whether or not $GETUAI()/$SETUAI() H > only uses the system table definition, or whether or not it then falls, > back to using any other logical defintion. > H > The only thing I can see as a possibility would be going back to Bob'sD > response(ish), in that you can specify an optional context used toI > maintain an open channel to the authorisation file;  if it was possible G > to hijack usage of this, and somehow get UAF to use a.n.other channel F > that one manually opens to the remote UAF - but I've no idea how theD > "channel" is actually opened by $GETUAI() or $SETUAI(), although I% > would guess it is probably $OPEN().  > G > As for then setting up the FAB for indexed file access - well, that's F > unchartered territory for me, filled with potential landmines if oneG > doesn't get it right (related to which is the $GETUAI() documentation F > warning about not using the context returned by it, as a context forF > then passing to $SETUAI();  for what I'm sure is a very good reason,F > even if the developers or documentation authors chose not to explain > why).  >  >  > Mark >  >    ------------------------------    Date: 31 Jan 2004 18:05:59 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) $ Subject: Re: $SETUAI() Query/Problem3 Message-ID: <rAoPF48Tifny@eisner.encompasserve.org>   o In article <pO2dnUvFieDoQIbd4p2dnA@brightview.com>, "covendotartdottalk21dotcom" <postmaster@127.0.0.1> writes: < > "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message/ > news:owaUX4dF8GaK@eisner.encompasserve.org...   D >> But if that _did_ work, what gives you the slightest hint that itI >> would meet hour goal of "avoiding sending the password in cleartext" ?  > F > Using $SETUAI in combination with $HASH_PASSWORD gives you a one-way > encrypted password.   C Ok, so they have to use a dictionary attack against the UAF record.   E > If someone also "sniffs" the SALT and algorithm in use (because one D > has to $GETUAI in the first place, to find out the user's SALT andG > algorithm - one can't guarantee that the algorithm in use on NODEB is D > the same as NODEA - in order to use $HASH_PASSWORD appropriately),  D $SETUAI transfers the entire UAF record to disk, because that is theE nature of RMS records.  Rethink your desired use of RMS between nodes - and you will realize this has to be the case.   E > then arguably, "they" could use that to launch a dictionary attempt ? > to see if "they" could ever generate the same hashed password   F Yes, and that is quite straightforward.  VMS Password Security dependsA on two mechanisms that are not available in this threat scenario:    	1. Secrecy of the salt  	2. VMS Breakin Evasion   A The first is mainly a defense against _precomputed_ hash attacks, C raising the level of effort and precomputation data store required. @ But the second is crucial to defense against dictionary attacks,6 reducing the attempt rate to less than one per minute.  D > (provided they had legitimate access to an OpenVMS system, and had  C Such as a free hobbyist license on a free machine offered from time  to time.  F > programming skills available to them to make use of $HASH_PASSWORD).  D Or programming skills on a non-VMS system.  I would not be surprisedD if there is hacker code to do the VMS password algorithm on windows.  @ > However, depending on what criteria are specified for passwordG > selection, the chance of actually generating the same hashed password H > before it gets changed again, may be slim (and depending on how "they"G > attempt to then connect to NODEB, "they" may set off intruder alarms, : > further limiting "their" chances of not being detected).  E If they have the UAF data, they don't need to touch the machine until E they have computed the proper password via offline dictionary attack.   G > Even if someone does generate the same hashed password, the fact that @ > it was not sent in cleartext format, still meets the obscurityD > deptartment's requirement that it is not sent in cleartext format. > F > It's not my fault that they're not more specific in their assessment > of vulnerabilities  A I think you should bring the vulnerability assessment shortcoming % to the attention of upper management.   B >> What makes you think MCR AUTHORIZE uses those system services ? > H > Because it would seem logical, since it gets and sets UAF information;B > having separate code that has to change each time the UAF formatD > changed (i.e. if AUTHORIZE manually traverses the UAF file itself)B > would be nonsensical - why not use perfectly good system service > routines that already exist?  D Those system services (not "perfectly good" due to never implemented; AST capabilities) did not exist when Authorize was written.   C > Ergo, MC AUTHORIZE may manipulate wildcards and convert them into H > suitable $SETUAI()/$GETUAI() calls;  just because it handles wildcards. > doesn't mean it doesn't use system services. > E > But then again, I don't have a copy of the source code, and I'm not > > sure if the source for AUTHORIZE is even included on the CD.   I do, and it is.  @ > Maybe you have access to the source and can tell me different?   I did in my prior post.    ------------------------------  $ Date: Sun, 1 Feb 2004 01:39:41 -00009 From: "covendotartdottalk21dotcom" <postmaster@127.0.0.1> $ Subject: Re: $SETUAI() Query/Problem3 Message-ID: <9JWdndpAE7B9xYHdRVn-gw@brightview.com>   : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:rAoPF48Tifny@eisner.encompasserve.org... 5 > In article <pO2dnUvFieDoQIbd4p2dnA@brightview.com>, ; "covendotartdottalk21dotcom" <postmaster@127.0.0.1> writes: F > $SETUAI transfers the entire UAF record to disk, because that is theG > nature of RMS records.  Rethink your desired use of RMS between nodes / > and you will realize this has to be the case.   C You are of course, presuming that I know the format of UAF records, A and that a user "record" is not actually comprised of a number of ? other smaller "records".  The $GETUAI()/$SETUAI() documentation , doesn't indicate the format of the UAF file.    H > Yes, and that is quite straightforward.  VMS Password Security dependsC > on two mechanisms that are not available in this threat scenario:  >  > 1. Secrecy of the salt > 2. VMS Breakin Evasion  F Again, you're making a presumption (in #2) that access from any DECnetC or IP address is permitted to these systems.  It's not.  Permitted/ ' trusted nodes can be (and are) defined.   B You might then presume that address spoofing is then an issue, but= you don't know what security measures exist in the networking ) components of our network infrastructure.     F > > (provided they had legitimate access to an OpenVMS system, and had > E > Such as a free hobbyist license on a free machine offered from time 
 > to time.  E Well, the box would have to be physically connected into our network, B and not using any kind of addressing mechanism that would conflictE with existing systems in the network, in addition to having access to C the datacomms rooms, and reconfiguring ports to which the box could ' then be connected, to make them active.   D Assuming of course that "they" could actually find a source of cheap& second-hand VMS boxes in this country.  D Whilst "never say never" and "nothing is impossible" may be relevantD phrases here, I doubt very much that all of the elaborate steps thatC would be required for such an attack to occur in our network, would C actually be fulfilled, and in any case, other systems which monitor E the output of these boxes would indicate within seconds a DOS attack, D or an attempt to change the output into something which "they" would" achieve some kind of benefit from.    H > > programming skills available to them to make use of $HASH_PASSWORD). > F > Or programming skills on a non-VMS system.  I would not be surprisedF > if there is hacker code to do the VMS password algorithm on windows.  E I don't have a set of VMS source code, so I don't know whether or not E $HASH_PASSWORD() code is included (in its entirety), but I would have  thought this unlikely.  A Is $HASH_PASSWORD()'s functionality generic (not specifically the = algorithms that are used), or is (some of) the implementation 
 VMS-specific?       F > Those system services (not "perfectly good" due to never implemented= > AST capabilities) did not exist when Authorize was written.   A That's as may be, but instead of repeating your argument, why not D indicate whether or not that is still the case, or whether Authorize% has, in fact, "moved with the times"?       E > > Ergo, MC AUTHORIZE may manipulate wildcards and convert them into J > > suitable $SETUAI()/$GETUAI() calls;  just because it handles wildcards0 > > doesn't mean it doesn't use system services. > > G > > But then again, I don't have a copy of the source code, and I'm not @ > > sure if the source for AUTHORIZE is even included on the CD. >  > I do, and it is. > B > > Maybe you have access to the source and can tell me different? >  > I did in my prior post.   E I don't see any reference to "I've got a set of VMS sources, and I've D looked for AUTHORIZE, and it does exist on the CD" in your statement@ "What makes you think MCR AUTHORIZE uses those system services ?4 It can do wildcards and the system services cannot."  C Self-belief of implication is one thing, but it doesn't necessarily C follow that everyone else will infer the same thing, especially for = those for whom [American] English is not their mother tongue.   E It's hard enough getting companies to continue to use VMS these days, A let alone choose it for new solutions, without resurrecting CJL's D attitude and then causing in-fighting amongst the brethren who still practice it...  @ Instead of bitching about the fact that I'm trying to achieve anC automated way of changing passwords on thousands of accounts across F hundreds of systems, have you got any *useful* suggestions on how thisE might be achieved (in a different way to the way I have been trying)?   E Do you now, or have you ever had this problem?  How did you deal with C it?  If you've not had the problem, do you know of someone else who   did?  How did they deal with it?   Mark   ------------------------------  $ Date: Sun, 1 Feb 2004 01:53:30 -00009 From: "covendotartdottalk21dotcom" <postmaster@127.0.0.1> $ Subject: Re: $SETUAI() Query/Problem3 Message-ID: <JcidnSXkfPKAwYHdRVn-vg@brightview.com>   0 "Jonas Lindholm" <jlhm@usa.net> wrote in message4 news:RNVSb.168539$4F2.19936568@twister.nyc.rr.com... >  > I > Can you give us an example how you define SYSUAF and RIGHTSLIST logical / > names on NODEA to access the files on NODEB ?  > H > Remember you need proxy access on NODEB if you don't also specify your+ > username and password in the definitions.  >  > /Jonas  E Well, the logical is created, and the code therefore works fine, so I C don't know that there's really any need to post it here (especially ? as it would take some time to strip it down to the bare minimum E that is normally required for such posts anyway), but it's equivalent $ to having done the following in DCL:  @ $ DEFINE /PROCESS /EXECUTIVE SYSUAF NODEB::SYS$SYSTEM:SYSUAF.DAT  7 where NODEB is defined in the DECnet database on NODEA, G SYS$SYSTEM:SYSUAF.DAT is the correct location of the UAF file on NODEB, G and the UIC under which the executable runs that defines the logical on H NODEA, does have SYSNAM as a default and authorised privelege in NODEA's UAF.  G For the purposes of testing, I'm currently not using $DELLNM() prior to D image rundown, so when returned back to DCL, if I do SHOW LOG SYSUAFG /FULL, I can see (in the system table) the SYSUAF definition of the UAF H on the development system, and prior to this, in the process name table,? the SYSUAF definition (executive mode) pointing to NODEB's UAF.   C I think I'm just trying to achieve the impossible.  Maybe I'll just F have to say that the VMS systems don't meet the security requirements,B and that unless they employ someone two days a week to perform theD laborious process of changing thousands of passwords across hundredsF of systems*, they'll just have to get rid of the hundreds of VMS boxesB we have, and replace them with... er... ah... oh, no other O/S canE achieve this either, so well, ah, the company will just have to close  down.   C Simple.  Everyone out of a job.  Problem no longer exists.  Problem 
 solved. **      D *  And set aside money to cope with the litigation pertaining to the    resulting RSI.   @ ** For all of the po-faced protagonists amongst you, I was being
    facetious.    Mark   ------------------------------  + Date: Sat, 31 Jan 2004 19:13:00 +0000 (UTC) 5 From: "Mike O'sullivan" <mike.osullivan3@nowhere.com> 9 Subject: Re: Canadian Troll infestation in rec.travel.air 2 Message-ID: <bvgunr$2ar$1@hercules.btinternet.com>  0 "edo" <nobody@cryptorebels.net> wrote in message9 news:ace8b8aaabac68b63bd3c695e5da05b6@cryptorebels.net...  > E > It's envy, mostly.  Having to live so close to the US that they can  practically J > smell the abundance and success yet not being able to enjoy it.  It just kills  > them.   > "Poor Canada, so far from God, so close to the United States"!   ------------------------------  % Date: Sat, 31 Jan 2004 13:19:38 -0600 ! From: Ken Pisichko <kenp@mts.net> 9 Subject: Re: Canadian Troll infestation in rec.travel.air ' Message-ID: <401BFFCA.7D9025E5@mts.net>   N Give me a break! Remember "who" provides the northern USA with electricity andP natural gas. Envy?? What for? Remember who destroyed, or tried to destroy "your"" electrical grid as well as "ours".  P Envy?   Physician Heal Thyself! The USA rates itself. The United Nations and theR rest of the world rates everyone. Take a look at the statistics. If you are in theO USA you know you don't have to follow my suggestions, after all you are in "the  land of the free".  K At -41C this last few mornings here "we" are enjoying record sales of "our" B electrical power and natural gas to grateful US utility companies.   Envy??  Surely you jest!  
 edo wrote:  Q > It's envy, mostly.  Having to live so close to the US that they can practically P > smell the abundance and success yet not being able to enjoy it.  It just kills > them.    ------------------------------  # Date: Sat, 31 Jan 2004 20:14:36 GMT % From: "Aramis" <porthos_jb@yahoo.com> 9 Subject: Re: Canadian Troll infestation in rec.travel.air I Message-ID: <M0USb.50165$ef.4615@twister01.bloor.is.net.cable.rogers.com>    Meeeeoooowwwwwwwww, eh?   0 "edo" <nobody@cryptorebels.net> wrote in message9 news:ace8b8aaabac68b63bd3c695e5da05b6@cryptorebels.net... + > Robert Browne <srqace@comcast.net> wrote:  >  > > 5 > >"ivy_mike" <ivy_mike@my-deja.com> wrote in message : > >news:13077cb5.0401310805.620eed68@posting.google.com...; > >> "Jim Anderson" <jim@worldnet.att.net> wrote in message H > >news:<BmCSb.144412$6y6.2810410@bgtnsc05-news.ops.worldnet.att.net>... > >> >: > >> I've got no problem with moderated groups, as long as > > I > >I recently returned to reading the group after an absence of approx. 2  years L > >and find it not even worth the time. I scan it each day to identify postsI > >from Bill Mattox  ( who may be disgusted too since I have not seen him  hereI > >for quite a while)and a couple of others and skip the rest. The trolls  and J > >the U.S. haters and just plain jerks have made it just about worthless. TheyL > >would do usenet a favor if they would take their anti Bush, anti U.S. and9 > >other nonsense to groups set up for that type of post. A > >It used to be fun and informative to read r.t.a., but no more.  > >Bob > D > If you'll notice, most of these foaming-at-the-mouth US-haters are	 Canadian, 2 > with a few Eurotrash like Sjoerd, AJC, Nik, etc. > H > Canadian trolls are like cockroaches, when you see one there's about a million K > other ones lurking in the dark.  Unfortunately, we have the Leader of the B > Canadian Trolls here, JF Mezei, and he has brought out his slave cockroaches to > help him do his dirty work.  > E > It's envy, mostly.  Having to live so close to the US that they can  practically J > smell the abundance and success yet not being able to enjoy it.  It just kills  > them.  >  >  >    ------------------------------  # Date: Sat, 31 Jan 2004 20:39:13 GMT , From: "Tim Kroesen" <tkroesen@earthlink.net>9 Subject: Re: Canadian Troll infestation in rec.travel.air B Message-ID: <RnUSb.4465$jH6.1074@newsread1.news.atl.earthlink.net>  1 Definitely!  For the non-cat speakers amongst us:   H http://groups.google.com/groups?q=troll%2Bmeow%2Bfaq&hl=en&lr=&ie=UTF-8&* selm=afn23950.38.328ABE94%40afn.org&rnum=1   Tim K   0 "Aramis" <porthos_jb@yahoo.com> wrote in messageC news:M0USb.50165$ef.4615@twister01.bloor.is.net.cable.rogers.com...  > Meeeeoooowwwwwwwww, eh?  >    ------------------------------  # Date: Sun, 01 Feb 2004 02:49:29 GMT > From: Michael Austin <maustin@no-more-spam.firstdbasource.com> Subject: Re: DCL questions= Message-ID: <ZOZSb.12180$W53.2250@newssvr22.news.prodigy.com>    Richard B. Gilbert wrote:    > Try this for SCRIPT1 > B > $ SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=(0,1) /OUTPUT=XX.TMP -0 >    'F$CVTIME("YESTERDAY", "ABSOLUTE", "DATE")' > 
 > For SCRIPT2 G > You can get a Ctrl-E character into your file with the sequence GOLD  ' > <keyboard 5> GOLD SPECINS (keypad 3).  > 
 > AMIT wrote:  > 
 >> hello all, G >> I am tryin to write two DCL scripts. I have some problems, and would  >> appreciate any help I get.  >>D >> SCRIPT1: I would like to read a log file which contains a list of@ >> events with timestamps. Only events from yestartday should be; >> extracted into another text file, which would be mailed.  >>  27-jan-2004 14:00:02 >>       fsdfsdfdsfdfdfdfs >>  28-jan-2004 12:00:00 >>       sample2,sample2H >>  Only entries from yesterday need to be extracted. How can I do this? >>G >> SCRIPT2: We use CA's CONSOLE application to check controllers. Using E >> CONSOLE CONNECT xxxx, I generally check the controller, then press  >> Ctrl/E to exit.3 >> if I need to do this using DCL, how can I do it?  >> $console connect xxyyzz >> show failed >> show this_controller I >> ctrl/E<<<<---------- This doesn't work. I need to send the application 	 >> Ctrl-E  >> $exit >> >> >> Thanks in advance >> bye >> AS. >>   >> >    It is a lot easier with pipe...   6 $ pipe SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=(0,1) -4     'F$CVTIME("YESTERDAY", "ABSOLUTE", "DATE")'  | -A     mail sys$pipe /subj="Logs from yesterday" "user@whatever.com"   > As for script 2 goto the dcl.openvms.org website and look for C monitor_hs.com works on both HSZ and HSG controllers.  I use it to  & extract stuff from 36 HSG controllers.  J You can cut/paste from there -- or just use what has already been written.   http://dcl.openvms.org/    Michael Austin.    ------------------------------  % Date: Sat, 31 Jan 2004 16:14:59 -0800 * From: "Jack Peacock" <peacock@simconv.com>7 Subject: Does iSCSI infringe on any MSCP patents or IP? 2 Message-ID: <UYudnRB6d9uZ2IHdRVn-sA@mpowercom.net>  H While reading a newsletter about how well iSCSI is now working as far asL vendor interoperability, it struck me that DEC has done this before with theL MSCP protocol, sending command packets for storage access to remote machinesJ across a network interconnect.  While the command specifics may not match,I is that enough for there to be no hidden big hammer waiting at HP to come L down on storage vendors if iSCSI takes off in a big way?  Did HP inherit anyH patents or trade secrets for MSCP, and what is their status now?  Has HPL made any announcements regarding MSCP?  It's been my understanding that MSCPI was regarded as a proprietary protocol and trade secret, one that DEC did  not release for general use.    Jack Peacock    ------------------------------  % Date: Sat, 31 Jan 2004 19:17:50 -0500 % From: "DAVID TURNER" <DAVID@HPAQ.NET> E Subject: Re: Flashing lights on my disk drives on an Alphaserver ES40 0 Message-ID: <101ohdj5g662a04@news.supernews.com>  L When you have internal disks a junk card is installed in the ES40 - assuming, you have a BA610-6E 6 slot cage in the front? Doesn't really do much - but there are known problems with them ? it is just under the console connection inside the pci bus area  My bet is that it is hosed   dt     --   Island Computers US Corp 2700 Gregory St Suite 180  Savannah GA 31404  Tel: 912 4476622 Fax: 912 201 0402 , Email (SPAMproofed) dbturner@islandco.nospam (replace nospam with .com)    > "Matt Finbow" <matthew.finbow@btinternet.com> wrote in message7 news:ec25d2bf.0401280454.449e1545@posting.google.com... 1 > rcbryan@hotmail.com (RC Bryan) wrote in message 9 news:<fbcf38dc.0401271228.44398a76@posting.google.com>... L > > > > on the front.  When it came up again, it could not read from any DKAL > > > > devices and the lights on my disk drives were all flashing together. > > >  > > > Try first !  > > >  > > > >>> SHOW DEVICE  > > > C > One thing to check for might be where are the disks plugged into?  > H > The fact that the lights are all 'flashing together' seems to indicateE > a RAID controller - check to see where the disks actually go to and ; > then check that the controller is seen by the SRM console  > / > i.e. show config should return something like 5 > 'Bus nn Slot nn:CPQ SmartArray 5300   pyan.n.n.n.n' H > or whatever the controller is - even if it is not a RAID controller itG > should be listed in SRM e.g. a PKxn device. If the system can't see a 4 > controller then it won't see disks the other side. > B > If it is a 5300, check the installation manual to see if the SRM@ > variables have changed - i.e. the HEAP_EXPAND and the BOOTBIOS > H > If the RAID controller is seen by SRM, go into the RAID config utilityA > and check that (a.) your physical drives are seen and (b.) your " > logical drives are still defined > F > At a wild guess, if you had a RAID 0 stripe set across all the disksD > and one failed I would imagine that the logical drive would not be@ > available - but I don't know whether it would flash the lights > A > try posting the 'show device' and 'show config' output for more F > detailed help, also get a look at the drive controller (physically). > G > Also note that if you have embedded SCSI adaptors on the system board G > AND a RAID card, it might be normal to have no devices showing on the H > internal SCSI bus(es), so if the RAID card disappears then there wouldF > be 'unused' controllers - make sure you follow the disk cables back! > F > Disclaimer: I don't have an ES40, the only OpenVMS RAID controller IH > have is a KZPAC running unsupported 36Gb disks and the above is only aC > gut feeling. (Although PC RAID controllers do tend to flash drive G > lights to indicate groups / problems), on the otherhand I did do some G > reading up on the SA5300A to see if I could use a secondhand Proliant  > (PC) version in a DS10 >  > Matt.  > > E > > The way I know it does not see any DKA devices is because I did a  > >  > > >>> show device  > > G > > I was kind of baffled by the results since it listed a SCSI bus.  I I > > had to go to another system and compare the results to see that I was F > > supposed to see the disks.  I expect this is one of those problemsC > > that will go away as soon as I take everything apart and put it J > > together again.  If it was my PC, I would have had it in pieces a longH > > time ago.  Since it is a 4 processor ES40 alphaserver, I think I may" > > just wait for a tech from HPQ. > > F > > The way all the lights are flashing together tells me something, IA > > just don't know what.  I need a magic decoder ring/book/CD or  > > something. >  > >  > > Thanks, 
 > > /RC Bryan    ------------------------------  # Date: Sat, 31 Jan 2004 21:50:29 GMT  From: <russ@dittmer.com>  Subject: Re: Hobbyist questions?0 Message-ID: <FqVSb.197584$xy6.1017420@attbi_s02>   The reason I ask is:  H My goal is to make my little AlphaStation  into a web accesible VMS gameJ station.  I would do this for free of course (I love a challenge).  If oneH registers, at no cost, they would get an account whereby they could saveJ their games, and if not, then they would have to access via the annonymous account with no save function.   RD    2 "Russ Dittmer" <russ@dittmer.com> wrote in message# news:401b0562_2@news1.prserv.net...  > Hello  > G > I applied for the associate membership with http://www.montagar.com/.  > < > Where does one acquire the CD-Roms for VMS 7.3-2 and such? > K > I understand I'll receive the hobbyist licenses and such after I register = > with HP, which will happen when I receive my membership ID.  >  > Just curious.  >  > RD >  >    ------------------------------    Date: 31 Jan 2004 12:40:24 -0800' From: icerq4a@spray.se (David Svensson) C Subject: Re: It is almost certain now, INTEL will have 64bit x86 !! = Message-ID: <734da31c.0401311240.12ebb42a@posting.google.com>   d "Bill Todd" <billtodd@metrocast.net> wrote in message news:<ssKdnXdIn9OlN4fdRVn-vg@metrocast.net>...4 > "Brian Chase" <bdc@world.std.com> wrote in message$ > news:bvcrr0$bco$1@pcls4.std.com...6 > > In article <bvbham$ald$1@news1.tilbu1.nb.home.nl>,$ > > Dirk Munk  <munk@home.nl> wrote: > > N > > > What many of us have been predicting for the last couple of years now is >  goingG > > > to be a reality. Intel will have 64bit x86 cpu's. Please read the  >  following+ > > > article from the news agency Reuters:  > > >  > > >  > N > http://www.reuters.com/newsArticle.jhtml?type=technologyNews&storyID=4233918 >  ) > > 5 > > A similar story is being carried on news.com too: 4 > > ( http://news.com.com/2100-1006_3-5150336.html ) > > $ > > ->  Intel shifts 64-bit emphasis > > ->  By Stephen Shankland# > > ->  Staff Writer, CNET News.com  > > ->J > > ->  Intel plans to demonstrate a 64-bit revamp of its Xeon and PentiumN > > ->  processors in mid-February--an endorsement of a major rival's strategy= > > ->  and a troubling development for Intel's Itanium chip.  > M > Thanks - I hadn't seen that second article, with the explicit rumor about a * > planned Intel demo in a couple of weeks. > G > I'm not about to start prancing around in a flight suit in front of a H > "Mission Accomplished!" banner, but it really is starting to look likeK > Truth, Justice, and at least what I'd like to think is still The American N > Way may triumph after all over strong-arm market tactics and spin - a lessonN > in the power of "Never surrender!" grassroots activism which I hope will notL > be lost on both corporate and political entities in this country (though IJ > fear it will take a few more repetitions before it *really* takes hold). >  > - bill  C I thought you were more interested in technology (and competition). F People can think whatever they want about EPIC/VLIW, but if shows thatD you can get better performance with a new idea I think it is a greatB thing to explore that. If it does not work out as good as expectedE that is also good. Then we know it, and can perhaps explore other new E ideas. To me, Itanium has some good ideas in it, but the success with   Xeon has not made things easier.  " You are probably better informed, 0 I don't know what mission you are talking about?   ------------------------------  % Date: Sat, 31 Jan 2004 21:39:42 -0500 * From: "Bill Todd" <billtodd@metrocast.net>C Subject: Re: It is almost certain now, INTEL will have 64bit x86 !! 2 Message-ID: <uoidnc8RSvJE-4Hd4p2dnA@metrocast.net>  4 "David Svensson" <icerq4a@spray.se> wrote in message7 news:734da31c.0401311240.12ebb42a@posting.google.com... 7 > "Bill Todd" <billtodd@metrocast.net> wrote in message . news:<ssKdnXdIn9OlN4fdRVn-vg@metrocast.net>...6 > > "Brian Chase" <bdc@world.std.com> wrote in message& > > news:bvcrr0$bco$1@pcls4.std.com...8 > > > In article <bvbham$ald$1@news1.tilbu1.nb.home.nl>,& > > > Dirk Munk  <munk@home.nl> wrote: > > > I > > > > What many of us have been predicting for the last couple of years  now is
 > >  goingI > > > > to be a reality. Intel will have 64bit x86 cpu's. Please read the  > >  following- > > > > article from the news agency Reuters:  > > > >  > > > >  > >  > > L http://www.reuters.com/newsArticle.jhtml?type=technologyNews&storyID=4233918 > >  ) > > > 7 > > > A similar story is being carried on news.com too: 6 > > > ( http://news.com.com/2100-1006_3-5150336.html ) > > > & > > > ->  Intel shifts 64-bit emphasis > > > ->  By Stephen Shankland% > > > ->  Staff Writer, CNET News.com  > > > ->L > > > ->  Intel plans to demonstrate a 64-bit revamp of its Xeon and PentiumG > > > ->  processors in mid-February--an endorsement of a major rival's  strategy? > > > ->  and a troubling development for Intel's Itanium chip.  > > G > > Thanks - I hadn't seen that second article, with the explicit rumor  about a , > > planned Intel demo in a couple of weeks. > > I > > I'm not about to start prancing around in a flight suit in front of a J > > "Mission Accomplished!" banner, but it really is starting to look likeD > > Truth, Justice, and at least what I'd like to think is still The AmericanI > > Way may triumph after all over strong-arm market tactics and spin - a  lessonL > > in the power of "Never surrender!" grassroots activism which I hope will not L > > be lost on both corporate and political entities in this country (though I L > > fear it will take a few more repetitions before it *really* takes hold). > > 
 > > - bill > E > I thought you were more interested in technology (and competition).   I I'm certainly interested in technology, and I think that competition is a E good thing.  Both of those inform my attitude toward Itanic:  I don't F believe it's very useful technology (at least not the EPIC part:  someK surrounding chip features like the cache architecture merit respect), and I F strongly resent the fact that despite its technological inferiority itL managed to kill off superior products (though that's more the fault of those" who did so than of Itanic per se).   ...   2 > I don't know what mission you are talking about?  H The mission to make sure that cHumPaq paid the appropriate price for theH manner in which it killed Alpha - though I've always said I'd settle forD appropriate apologies coupled with real compensation (in the form ofJ dramatically increased VMS support to make up for the hit it took from theK Alphacide).  If if weren't for the Alphacide, Itanic would just have been aeL not-very-interesting side-show for me, since I doubt that anyone would stillL be considering it a viable competitor (after all, there's no indication thatK Intel had a clue where to take it after McKinley and the subsequent shrinksCJ and cache-increases:  they needed the Alpha team to have had any future at all).n   - bill   ------------------------------    Date: 31 Jan 2004 22:27:41 -0000 From: LOL <lol@lol.lol>l, Subject: Re: Jacques Chirac and JF M-e-z-e-i7 Message-ID: <KBONG1UG38017.6858912037@anonymous.poster>J  + rk <stellare@nospamplease.erols.com> wrote:    >nobody wrote: >pL >> This is the same as the WMDs that they will find in September designed toI >> bolster Bush Jr,s election prospects. The USA media will not cover anyaI >> questioning from oustide the USA about the authenticity of such a findkJ >> (since those will have been planted), so the american public will trulyA >> believe that Bush was right and the idiot will get re-elected.m >oL >Of course, other people have made such predictions before.  Another poster M >made this prediction almost a year ago (last March), an a post titled "Just h >for the record - Iraq": >TF >   Because this is an illegal invasion, the USA will feel the need toC >   justify itself by finding as many banned weapons as possible tosE >   parade in front of the media. If it doesn't find anything (eotherkD >   because there was none or because it was destroyed during war), 8 >   the temptation to plant evidence will be too great.  > A >Odd, that didn't happen.  So that poster's credibility is zilch.e   LOL>  y http://groups.google.com/groups?safe=images&ie=UTF-8&oe=UTF-8&as_umsgid=%3C3E78C28C.EAE5C61D@vl.videotron.ca%3E&lr=&hl=enn   ------------------------------    Date: 31 Jan 2004 22:35:23 -0000 From: LOL <lol@lol.lol>t( Subject: Re: Jacques Chirac and JF Mezei7 Message-ID: <XOP5Y99638017.6912384259@anonymous.poster>'  + rk <stellare@nospamplease.erols.com> wrote:i   >nobody wrote: >aL >> This is the same as the WMDs that they will find in September designed toI >> bolster Bush Jr,s election prospects. The USA media will not cover anyoI >> questioning from oustide the USA about the authenticity of such a findtJ >> (since those will have been planted), so the american public will trulyA >> believe that Bush was right and the idiot will get re-elected.B >sL >Of course, other people have made such predictions before.  Another poster M >made this prediction almost a year ago (last March), an a post titled "Just c >for the record - Iraq": >gF >   Because this is an illegal invasion, the USA will feel the need toC >   justify itself by finding as many banned weapons as possible toGE >   parade in front of the media. If it doesn't find anything (eother D >   because there was none or because it was destroyed during war), 8 >   the temptation to plant evidence will be too great.  >aA >Odd, that didn't happen.  So that poster's credibility is zilch.    LOL(  y http://groups.google.com/groups?safe=images&ie=UTF-8&oe=UTF-8&as_umsgid=%3C3E78C28C.EAE5C61D@vl.videotron.ca%3E&lr=&hl=enh   ------------------------------  # Date: Sat, 31 Jan 2004 19:17:01 GMTt9 From: "Frank F. Matthews" <frankfmatthews@houston.rr.com> ( Subject: Re: JF's black helicopter world0 Message-ID: <NaTSb.308$QU1.142@fe2.texas.rr.com>  G Now don't tweak anyone about the unmarked black helicopters.  They are sI out there for anyone to see.  Try the airport just off the interstate in o Meridian Miss.  FFM.  . > JF Mezei <jfmezei.spamnot@istop.com> whined: > |1 >  >>Tony Reed wrote: >>J >>>Jeez, J.-F., you need to get out more. You're teetering on the brink of) >>>serious black-helicopter kookery here.w snip   ------------------------------  % Date: Sun, 01 Feb 2004 15:12:13 -0500i From: +- <+-@no.net>, Subject: Re: Mezei domain theft - nobody.com- Message-ID: <a%TSb.43$yf3.418@news.ntplx.net>y  
 edo wrote:  L > nobody.com is a registered domain.  Report Mezei's theft and abuse of this' > domain to its owner  <tdl@canada.com>  >  > Domain Name: NOBODY.COMn > , > Administrative Contact, Technical Contact:' > Southport Technologies tdl@canada.com  > 314 Queen Street South > Suite 158s > Bolton, Ontario L7E 4Z9a > CA  > 905-880-0289 fax: 905-880-3061 >   > Record expires on 24-Aug-2004.  > Record created on 25-Aug-1995. >  > Also report him to:  >  > abuse@sympatico.ca > abuse@bellglobal.com > abuse@istop.com  >  > Jean-Francois Mezei  > 86 Harwood Gaten > Beaconsfield, QC H9W3A3  > (514) 695-8259 >  > A DECADE OF USENET TROLLINGe >  > jfmezei@istop.come > jfmezei.spamnot@istop.com, > jfmezei@videotron.ca > jfmezei@vl.videotron.cae > nospam.jfmezei@videotron.cam  > "jfmezei"@videotron.ca[nospam] > nobody <nobody@nobody.com>+ > Conspiracy Theory <conspiracy@theory.org>h( > Lou Raccoon <L.Raccoon@wilderness.org>& > Flapping Labias <flabia@anatomy.org>' > Throbbing vulva <t.vulva@anatomy.org>  > Twin Gonads <two@gonads.com>' > Loose Scrotum <l.scrotum@anatomy.org>k$ > Raised Organ <R.Organ@anatomy.org>& > Popped Cherry <P.Cherry@anatomy.org>/ > Monica Lewinski <billclinton@westchester.com>h) > Deep Fried Foreskin <dff@mcdonalds.com>f$ > Aroma of Smegma <aroma@chanel.org> > Wet fart <w.Fart@smell.org>l) > Pubic dandruff <P.dandruff@anatomy.org>.* > Voluptuous Nipple <V.nipple@anatomy.org>( > Inserted Finger <I.Finger@anatomy.org>! > Pubic Nair <shaved@anatomy.org>a) > Flatulent Meatus <F.Meatus@anatomy.org>g' > Lihk Mhygroin <L.MyGroin@anatomy.org>o > Pre Khum <P.Khum@anatomy.org>t# > Phi Mosis <Phi.Mosis@anatomy.org>w% > Bal Anatis <Bal.Anatis@anatomy.org>a" > Fren Ullum <F.Ullum@anatomy.org>& > Ivanna Getlaid <I.Getlaid@onani.org>( > Ivanna Wankalot <I.Wankalot@onani.org>& > Ivanna Umpalot <Humpalot@drevil.com>, > Wan Tnoneofit <W.Tnoneofit@weirdnames.org>  > Wan Itbad <W.Itbad@inneed.org># > Wan Towank <W.ToWank@anatomy.org>e! > Wan Tolik <w.tolik@anatomy.org>t& > Testos Terone <t.terone@anatomy.org># > Upper Gonad <U.Gonad@anatomy.org>t# > Right Gonad <R.Gonad@anatomy.org>f" > Left Gonad <L.Gonad@anatomy.org>& > Tyson's Glands <Tyson.G@anatomy.org>  > Nose Hair <n.hair@anatomy.org>' > Coronal Sulcus <C.Sulcus@anatomy.org>p' > Corpus Cavernus <manhood@anatomy.org>i& > Armpit moisture <armpit@anatomy.org> > Onani Room <onani@hotels.com>n( > Arnie's Banana <weiner@terminator.com>* > Raised eyebrows <r.eyebrows@anatomy.org>' > Vas Deferens <V.deferens@anatomy.org> ' > Naked Canuck <N.canuck@naturists.org>s( > Arni's socks <Smelly.Socks@arnold.org>, > Notable Exception <N.exception@untied.com>( > Unpopped Cherry <U.Cherry@anatomy.org>) > Tatooed Ovaries <T.Ovaries@anatomy.org>n) > Pierced eyelid <p.eyelid@piercings.org>m* > Limp Tomato <limp.tomato@vegetables.org>. > Eggplant Earrings <e.earrings@piercings.org>0 > Banana Underpants <B.Underpants@hillfiger.org> > Naval Lint <navel@lint.mil> ) > Ingrown Toenail <i.toenail@anatomy.org>d' > Empty Stomach <E.Stomach@anatomy.org>$& > Full Stomach <f.stomach@anatomy.org>$ > Smelly Cat <S.Cat@friends.nbc.com>( > Torn Ligament <T.Ligament@anatomy.org>% > Art Tistic <A.Tistic@modern.museum>s* > Furry Raccoon <F.Raccoon@wilderness.org>' > Wet Racoon <W.Racoon@wildnerness.org>C$ > Mad Racoon <M.Racoon@wildlife.org>' > Lazy Racoon <L.Racoon@wilderness.org> ( > Eaten Racoon <E.Raccoon@mcdonalds.com>) > Happy Raccoon <H.Racoon@wilderness.org>,+ > Sleeping Racoon <S.Racoon@wilderness.org>t) > Hungry Racoon <H.Racoon@wilderness.org>u$ > Horny Raccoon <H.Racoon@fauna.org>* > Smart Raccoon <S.Raccoon@wilderness.org>. > George W Raccoon <GW.Raccoon@wilderness.org>- > Ronald McRaccoon <r.raccoon@wilderness.org>e, > Thirsty Raccoon <T.Raccoon@wilderness.org>* > Johnny Raccoon <J.Racoon@wilderness.org>) > Oshi Santo <O.Santo@nx01.starfleet.org>t, > Oishi Chinko <O.Chinko@nx01.starfleet.org>! > T.Yellow <T.Yellow@nowhere.com>a > Q <queue@continuum.net>n > Borg Queen <1of1@borg.org>, > Ronald Wilkerson <wilkersonr@sympatico.ca>+ > John Balterman <j.balterman@sympatico.ca>g    ! What is your isue with this dude?  --  J +-; the point where things begin and end, where the end is start and start comes to it's final end.....   ------------------------------    Date: 31 Jan 2004 17:41:30 -0800% From: a.greig@virgin.net (Alan Greig)r9 Subject: Re: New Variant MyDoom.B targeting Microsoft.comh= Message-ID: <af3b9b31.0401311741.473a4223@posting.google.com>y  x "Ken Farmer" <KFarmer@NOSPAM.SpyderByte.com> wrote in message news:<6f8Sb.21725$F86.1916164@twister.southeast.rr.com>...9 > "JF Mezei" <jfmezei.spamnot@istop.com> wrote in message   E >    Mydoom.B is a new variant of the Mydoom worm and is about 29,184dD >    bytes. This variant attempts to perform a Distributed Denial ofH >    Service (DDoS) attack against Microsoft.com. Details regarding thisK >    new worm are still emerging, but it has been validated as spreading in I >    the wild. Facts about the worm will be further qualified with follow 0 >    up reports following this initial analysis.  B A quick search on Kazaa (this worm can spread via Kazaa as well asC email) shows extremely high infection resulting from the .A variantkF but nothing I can find from the .B variant. In other words the  attack@ is against www.sco.com . The attack against www.microsoft.com isA either hallucinated or not working. So far anyway... But the wormuA opens up a listener port to allow an autoupdate of itself so thise
 might change.d  F The SCO website appears to have been taken offline by this DDOS attack0 already. Stats at www.netcraft.com confirm this:  7 http://uptime.netcraft.com/perf/graph?site=www.sco.com c  N Compare this with http://uptime.netcraft.com/perf/graph?site=www.microsoft.com  C Of course main attack against Microsoft starts 2 days later so this A might change but I cant find any infections via Kazaa so probablyeA won't cause any disruption.. Note  the .A variant can be found inm@ Kazaa with a search for winamp5, the .B variant by searching for1 winamp0. Info from various major antivirus sites.e   ------------------------------    Date: 31 Jan 2004 19:14:39 -0800( From: bob@instantwhip.com (Bob Ceculski)S Subject: Re: OpenVMS vs unix security ... Andrew, the IBM guy awaits your response!w= Message-ID: <d7791aa1.0401311914.6a25d9b5@posting.google.com>c  m bob@instantwhip.com (Bob Ceculski) wrote in message news:<d7791aa1.0401301650.7b253db6@posting.google.com>...c  9 CERT Advisory CA-2001-02 Multiple Vulnerabilities in BINDu$ The BIND vulnerabilities reported inF www.cert.org/advisories/CA-2001-02.html had the potential to cause theF nameserver to access violate in MultiNet and TCPware. This problem has' been corrected with the following ECOs:i    E CERT Advisory CA-2002-03 - Multiple Vulnerabilities in Simple Networky0 Management Protocol (SNMP) (posted Feb. 5, 2002)C SNMP vulnerabilities reported in the CERT advisory CA-2002-03do notsD pose a security risk for MultiNet and TCPware. For more information,9 please review the MultiNet and TCPware CERT advisory FAQ.     A Here are the only two cert advisories reported with TCPware right A now Andrew ... and notice neither pose a security risk because as @ the first bind advisory states, VMS just stops those "c" garbage; unix code cert bugs right in their tracks with that "access ; violation error" ... can you read and comprehend the above?s   ------------------------------  + Date: Sat, 31 Jan 2004 19:49:47 +0000 (UTC)n% From: bdc@world.std.com (Brian Chase)a% Subject: Re: Renaissance of VAX-VMS ? ( Message-ID: <bvh0sr$eha$1@pcls4.std.com>  3 In article <401b6e22$0$3261$626a54ce@news.free.fr>,c$ Didier Morandi  <no@spam.com> wrote: > Tom Linden wrote:m > > Don't forget EADSh > J > When I say Airbus, I mean EADS. I can also add the French Army and many 7 > "sensitive" others, but on these I cannot say a word.i > M > I do know that you have the same issue in the States, for example. From my  H > letters on migration (http://www.didiermorandi.com/index_us.htm) I got > some mail O > from somewhere under a very strong NDA. May I suggest to HP to address these  P > Customers and prepare for them a serious future, other than telling them that  > they will "migrate to i64" ?  L I'm sure if you can quantify it in monetary terms, HP might listen to you.  J I've no doubts that there are a sizable and very profitable market segmentD of VAX customers out there.  But I don't think HP will listen to youH unless you can spell it out in terms of how many dollars, euros, pounds,! yens, etc. it'd be worth to them.I  J As a contrast to the DEC/Compaq/HP route, take a look at what IBM did withG their mainframe market.  IBM's approach has been to continue to extend,5H update, and support the architecture of the original 360 mainframe line I of hardware and software.  They did this even in the face of the RISC and D workstation fads during the early 1990s.  That's not to say that IBMF didn't ignore the shift to RISC and workstations, but they also didn'tG abandon their bread-and-butter legacy systems like some other companiess did.  C I personally think a 64-bit extended VAX architecture incorporatings2 current processor technologies would be dreamy :-)  F You're just aiming for parity between the VAX, Alpha, and IA-64 ports I of OpenVMS.  I think that'd be great if you can prove to HP it'd be worthI their efforts.   -brian.: -- FF --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----+ Font-o-Meter!      Proportional  Monospacede'                                       ^h   ------------------------------    Date: 31 Jan 2004 18:21:44 -0800. From: fabiopenvms@yahoo.com.br (Fabio Cardoso)8 Subject: Re: The VMS Path Not Taken: Now It Can be Told!= Message-ID: <f30679fb.0401311821.427f7898@posting.google.com>e  u "David Barnes" <david@nospam-bitsolve.com> wrote in message news:<uIvSb.1669$W37.16152730@news-text.cableinet.net>...dF > > Multiple times the idea of purchasing/saving/rescuing VMS has beenI > > floated on this newsgroup.  If there was really a serious effort hereuI > > to purchase VMS, why not sound the alarm and get help from all of thee > > loyal troops.m > C > I would contribute $100 to the cause.. VMS under a GNU licence...a0 > Er.. methinks Lin#* would be dead in a year...  N GNU ? No thanks ! These people of Open Source (Stallman) are a band of nuts ! K Just show the attack agains SCO !  Open Source people will kill each other.hA May be we from the OpenVMS world can survive and have benefits ! p   Regardss   FC t    * > So come on everyone!!! How about a poll?   ------------------------------   End of INFO-VAX 2004.062 ************************ with the litigation pertaining to the    resulting RSInet.se!not-for-mail
Xref: mvb.saic.com alt.food.wine:31242

> > Elie Jeune are and his wife (otherwise known as Madame) are lovely
> > people, and always very welcoming for a visit.

Have you got their adress and phone handy? If so, could you, please ...?

Cheers

Nils Gustaf

^~00002119:0000031243:007307:From: cwdjrxNOSPAM@webtv.net (Cwdjrx _)
Newsgroups: alt.food.wine
Subject: Re: Cognac?
Date: Mon, 3 Feb 2003 00:38:19 -0600 (CST)
Organization: WebTV Subscriber
Lines: 22
Message-ID: <4171-3E3E0E5B-423@storefull-2357.public.lawson.webtv.net>
References: <v3rf4dmblsd2cb@corp.supernews.com>
NNTP-Posting-Host: localhost.webtv.net
Mime-Version: 1.0 (WebTV)
Content-Type: Text/Plain; Charset=US-ASCII
Content-Transfer-Encoding: 7Bit
X-WebTV-Signature: 1
	ETAtAhUAr1RmAi/NLnjS+t+htbPfqG1ymtcCFGWpgJw+HLdLuyCK7GRc7073p1b6 
Content-Disposition: Inline
Path: mvb.saic.com!news.tamu.edu!newsfeed.cs.utexas.edu!vienna1-snh1.gtei.net!chcgil2-snh1.gtei.net!mtvwca1-snh1.ops.genuity.net!paloalto-snf1.gtei.net!news.gtei.net!newssorter-2001.public.lawson.webtv.net!not-for-mail
Xref: mvb.saic.com alt.food.wine:31243

Jerry asks: "Will an open bottle of cognac keep indefinately?  Jerry"

______________________________________

It will not go bad and become undrinkable as does table wine - it has
too much alcohol for that. However the bouquet and taste can slowly
change with time, especially if the Cognac is in a bottle or decanter
with much air space and if it is opened often. This is because many
