- Test - lists.nanog.org

Re: 60 Day Termination Notice (fwd)
by Mills＠huey.udel.edu 03 Mar '95

03 Mar '95

HWB, Backroom.udel.edu and one of its relatives still splice the Ether here, most of the time with LEDs dark, but they spring briefly to life once in a while when somebody yells "fuzzball!" The one at SDSC has apparently been overcome by Etheritis due massive load on the wire. Same thing happened at SURA. Dave

1 0

NACR question
by Bob Kupiec 03 Mar '95

03 Mar '95

I have a quick question on the NACR form that is unclear to me. Example: A customer of ours is a private individual with a .us domain. There is no vaild classification for the "orgtype" field to put him in. This is not a business or a non-profit org, but just a single individual. What should I use for "orgtype"? -- Bob Kupiec (N3MML) Phone: 1-609-897-7300 GES, Inc. (JvNCnet) Systems Engineering -or- : 1-800-35-TIGER 3 Independence Way Email: kupiec(a)jvnc.net Fax : 1-609-897-7310 Princeton, NJ 08540

1 0

Second Step in Database transition
by Elise Gerich 03 Mar '95

03 Mar '95

Hi, Many of you have been using the whois clients that permit you to query information in the PRDB. Whereas we are still completing the testing for generating consistent configurations for AS 690 from the RADB, the RADB is populated with all the information that the PRDB knows. Therefore, by Monday, March 6, 1995, when you issue a whois query for a network or a contact, the information that you will receive will come from the RADB. The whois client will return the same information if you query prdb.merit.edu or whois.ra.net. Here are samples of the responses you will see: Sample 1 whois -h whois.ra.net MAINT-AS237 mntner: MAINT-AS237 descr: People authorized to make changes for AS237 admin-c: JMD24 tech-c: JMD24 upd-to: AS237(a)ra.net auth: MAIL-FROM har(a)merit.edu auth: MAIL-FROM har(a)merit.net auth: MAIL-FROM jrv(a)merit.edu auth: MAIL-FROM jrv(a)merit.net auth: MAIL-FROM jmd(a)merit.edu auth: MAIL-FROM jmd(a)merit.net auth: MAIL-FROM jaw(a)merit.edu auth: MAIL-FROM jaw(a)merit.net auth: CRYPT-PW tbYt8hHdWtMPU remarks: # note this is pre-approved for AS 3561 -- please update that entry too mnt-by: MAINT-AS237 changed: dsj(a)merit.edu 950214 source: RADB Sample 2 whois -h whois.ra.net 128.140 route: 128.140.0.0/16 descr: EMORY-INET origin: AS279 advisory: AS690 1:3561(218) 2:3561(11) 3:279 4:86 mnt-by: SURA changed: sherk(a)sura.net 941101 source: MCI route: 128.140.0.0/16 descr: Emory University descr: Atlanta descr: GA 30322, USA comm-list: COMM_NSFNET advisory: AS690 1:3561(218) 2:3561(11) 3:279 4:86 changed: nsfnet-admin(a)merit.edu 941114 source: PRDB Note that if you query whois.ra.net or information on a route, it will return all entries for that route and the source of the information. Possible sources are: ca*net, mci, prdb, radb and ripe. If you query prdb.merit.edu for network or contact information, you will receive information from the RADB with a message indicating that the PRDB is retiring. The standard queries to prdb.merit.edu, whois -h prdb.merit.edu 'contact <#>' and whois -h prdb.merit.edu <#> will continue to work for several more weeks. If you have any questions concerning this next step in the deployment of the RADB aand the retirement of the PRDB, please send email to merit-ie(a)merit.edu. Thanks. --Elise

1 0

Additions to the NSFNET policy-based routing database
by smm＠twain.merit.edu 02 Mar '95

02 Mar '95

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired very soon. Details below. ------------------------------------------------------------------------------ The following changes have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST : Total = As + Bs + Cs + Aggs Registered Networks 48606 = 30 5309 40321 2946 Configured Networks 45693 = 30 5252 37529 2882 Added Networks 135 = 0 5 100 30 Deleted Networks 4 = 0 0 2 2 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 130.205.64/18 NET-RANDOMC C:US 1:1239 2:1800 3:1240 136.143/16 COSTAL C:US 1:3561(218) 2:3561(11) 3:114 148.130/16 SMOS-NETB C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 155.49/16 NEARNET-B-17 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 167.174/16 NET-YAMAHA C:US 1:1800 2:1239 3:1240 167.217/16 IPS C:US 1:3561(218) 2:3561(11) 3:1225(129) 4:1225(131) 5:1225(130) 192.6.4/24 HN-PHARMA-NET C:AT 1:701(136) 2:701(134) 3:1800 192.70.31/24 FNET-NSL C:FR 1:701 2:1800 192.216.106/23 NETBLK-METRICOM C:US 1:701(134) 2:701(136) 3:3561(11) 4:3561(218) 5:200(128) 6:200(144) 192.219.104/24 NET-PLATFORM-NET C:CA 1:701(136) 2:701(134) 192.239.80/23 SUPER-NET2 C:US 1:3561(218) 2:3561(11) 3:86 4:279 192.239.94/23 NCPC-NETBLK C:US 1:3561(218) 2:3561(11) 3:86 4:279 192.239.137/24 AFTACTT-NET1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 193.104.53/24 FR-EOITPF C:FR 1:701(136) 2:701(134) 3:1800 193.125.20/24 TIXM C:RU 1:701(136) 2:701(134) 3:1800 193.163.49/24 WSSD C:DK 1:701(136) 2:701(134) 3:1800 194.135/16 194-135-RU-RELCOM C:RU 1:701(136) 2:701(134) 3:1800 196.4.166/24 CATN-ET C:ZA 1:1957 198.77.84/23 NET-CAMSCI-AG C:US 1:3561(218) 2:3561(11) 3:86 4:279 198.79.160/24 LA-WLF-NET C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.91.32/21 WRLCNET-BLK C:US 1:3561(218) 2:3561(11) 3:86 4:279 198.91.40/23 WRLCNET2-BLK C:US 1:3561(218) 2:3561(11) 3:86 4:279 198.95.64/21 NET-BARRNET198-833 C:US 1:701(134) 2:701(136) 3:3561(11) 4:3561(218) 5:200(128) 6:200(144) 198.205.32/19 NETBLK-ALCALDN C:US 1:3561(218) 2:3561(11) 3:114 198.232.184/24 NETBLK-DELTANET C:US 1:2149 2:174 199.8.70/23 INDTECH.EDU C:US 1:3561(218) 2:3561(11) 3:1225(129) 4:1225(131) 5:1225(130) 199.8.72/21 INDTECH.EDU C:US 1:3561(218) 2:3561(11) 3:1225(129) 4:1225(131) 5:1225(130) 199.77.94/24 TENNESSEE2-NET C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.77.249/24 FERNBANK-DOM C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.77.250/23 FERNBANK-DOM C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.77.252/24 FERNBANK-DOM C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.94.177/24 MPI-177 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.94.178/24 MPI-178 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.94.179/24 MPI-179 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.63/24 CYBERSMITH-63 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.164.140/24 GENIENET C:US 1:701(136) 2:701(134) 199.166.4/24 NET-TCNSG C:CA 1:701(136) 2:701(134) 199.166.5/24 PRESEDGE C:CA 1:701(136) 2:701(134) 199.167.0/21 NET-NORCROSS C:US 1:1800 2:1239 3:1240 199.221.33/24 FLIESH-NET1 C:US 1:1330 199.222.22/24 CBANK-DMZ2 C:US 1:1333 199.222.23/24 CBANK-DMZ3 C:US 1:1333 199.231.16/24 HARTHOSP-16 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.17/24 HARTHOSP-17 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.18/24 HARTHOSP-18 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.19/24 HARTHOSP-19 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.20/24 HARTHOSP-20 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.21/24 HARTHOSP-21 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.22/24 HARTHOSP-22 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.23/24 HARTHOSP-23 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.24/24 HARTHOSP-24 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.25/24 HARTHOSP-25 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.26/24 HARTHOSP-26 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.27/24 HARTHOSP-27 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.28/24 HARTHOSP-28 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.29/24 HARTHOSP-29 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.30/24 HARTHOSP-30 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.231.31/24 HARTHOSP-31 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.233.99/24 CORPSTAFF C:US 1:1800 2:1239 3:1240 199.244.155/24 DOI-OIG1 C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.244.214/23 CAPITALONE-COM C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.244.216/22 CAPITALONE-COM C:US 1:3561(218) 2:3561(11) 3:86 4:279 203.255.224/21 YONNAM-NET0 C:KR 1:297(144) 2:297(145) 204.19.163/24 ZERCOM C:CA 1:1324(36) 2:1324(32) 3:2493(35) 4:2493(91) 204.27.187/24 COX-SD1 C:US 1:1740(218) 2:1740(135) 204.58.152/24 PICNET-CBLK C:US 1:1328 204.58.153/24 PICNET-CBLK C:US 1:1328 204.58.154/24 PICNET-CBLK C:US 1:1328 204.58.155/24 PICNET-CBLK C:US 1:1328 204.90.90/24 EXECNET-DOM C:US 1:1800 2:1239 3:1240 204.135.144/21 SSHE-CIDR-WEST C:US 1:3577 2:1324(35) 3:1324(32) 204.135.160/21 SSHE-CIDR-EAST C:US 1:1324(35) 2:1324(32) 3:3577 204.138.173/24 BGI-ON-CA C:CA 1:2493(35) 2:2493(91) 204.138.174/24 BGI-ON-CA C:CA 1:2493(35) 2:2493(91) 204.138.175/24 BGI-ON-CA C:CA 1:2493(35) 2:2493(91) 204.153.196/22 NETBLK-NETAMERICA C:US 1:3830 204.164.204/24 INFOSOFT-NET204 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.205/24 INFOSOFT-NET205 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.207/24 PITNEYBOWES-NET207 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.64/24 VICOR-64 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.65/24 VICOR-65 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.66/24 VICOR-66 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.67/24 VICOR-67 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.80/24 MERRIMACK-80 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.130/24 VERTEX-130 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.144/24 BIOGEN-NET144 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.145/24 BIOGEN-NET145 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.146/24 BIOGEN-NET146 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.147/24 BIOGEN-NET147 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.148/24 BIOGEN-NET148 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.149/24 BIOGEN-NET149 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.150/24 BIOGEN-NET150 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.151/24 BIOGEN-NET151 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.160/24 GROTON-NET160 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.161/24 GROTON-NET161 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.162/24 GROTON-NET162 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.163/24 GROTON-NET163 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.164/24 GROTON-NET164 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.165/24 GROTON-NET165 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.166/24 GROTON-NET166 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.167/24 GROTON-NET167 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.168/24 GROTON-NET168 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.169/24 GROTON-NET169 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.170/24 GROTON-NET170 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.171/24 GROTON-NET171 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.172/24 GROTON-NET172 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.173/24 GROTON-NET173 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.174/24 GROTON-NET174 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.175/24 GROTON-NET175 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.184/24 XNET5 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.168.150/24 NET-FAC C:US 1:1239 2:1800 3:1240 204.179.110/23 WNET C:US 1:701(136) 2:701(134) 204.179.124/22 DIGITOPIA-NETBLK C:US 1:701(136) 2:701(134) 204.187.79/24 NET-TCS C:CA 1:1240 2:1800 3:1239 204.194.177/24 MNSNET2 C:US 1:3830 2:1800 3:1240 204.194.178/24 MNSNET2 C:US 1:3830 2:1800 3:1240 204.194.179/24 MNSNET2 C:US 1:3830 2:1800 3:1240 204.194.180/24 OS2BBS-NET C:US 1:3830 2:1800 3:1240 204.194.181/24 MNSNET2 C:US 1:3830 2:1800 3:1240 204.194.182/24 MNSNET2 C:US 1:3830 2:1800 3:1240 204.194.183/24 MNSNET2 C:US 1:3830 2:1800 3:1240 204.199.80/21 MVSU-ITTA-BENA-MS-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.199.153/24 ACC-NET2 C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.213.250/23 NET-NECA C:US 1:1239 2:1800 3:1240 204.215.128/18 TIAC64-1 C:US 1:1800 2:1239 3:1240 204.220.140/22 COMPUTERPRO C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.220.151/24 GOFAST1 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.246.64/21 WN-CIDR-2 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.249.5/24 NET-CYBERLYNX C:US 1:1239 2:1800 3:1240 204.250.12/24 NET-ENPOINTE C:US 1:1240 2:1800 3:1239 204.252.15/24 1ST-NET C:US 1:1957 204.252.200/22 CONDENAST C:US 1:701(136) 2:701(134) 204.253.2/23 INTEREST C:US 1:701(136) 2:701(134) 204.253.8/21 WILEY-NET C:US 1:701(136) 2:701(134) 204.253.16/24 DSMCHEM C:US 1:701(136) 2:701(134) Deletions: --193.235.182/23 SE-GAVLEBORG C:SE 1:701(136) 2:701(134) 3:1800 --193.235.184/21 SE-GAVLEBORG C:SE 1:701(136) 2:701(134) 3:1800 --199.170.202/24 GOLDSWORD1 C:US 1:701(136) 2:701(134) --199.170.203/24 GOLDSWORD2 C:US 1:701(136) 2:701(134) Expanded listing, sorted by country, then by organization: ========================================================== The "Expanded Listings" section of this NWG report has been retired since it is sorted by countries and network organization addresses. The replacement configuration generation system is based on the Internet Routing Registry (briefly called the "Global Routing Registry"). See the file ftp.ra.net:pub/radb/OVERVIEW for more information. The remainder of this report will also be retired shortly. ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 3561 - MCI-RESTON - ENSS 144 Peer: 192.203.230.18 - MCI - cpe2.SanFrancisco.mci.net AS690 CIDR Squeezings Report: 9813 Nets, 180 ASs, 2905 Aggregates ------------------------------------------------------------------ 9813 (82%) of the ever-announced more-specific routes within aggregates have been withdrawn. 167 of those were withdrawn within the last week. 575 the week before that. 178 the week before that. 180 ASs have registered aggregates in the PRDB. 161 of those are announcing aggregates. 86 have withdrawn at least one more specific route. 2905 Aggregates are configured. 2133 of these were Top-Level Aggregates (not nested in another aggregate). 1614 of these are being announced to AS690. 1024 of those have at least one subnet configured (the other 590 may be saving the Internet future subnet announcements). 869 have stopped announcing at least one configured more specific route. 837 have stopped announcing half of their configured more specific routes. 808 have stopped announcing most (80%) of their more specific routes. See home.merit.edu:pub/nsfnet/cidr/cidr_savings for more detail. ----------------------------------------------------------- ========================================================== The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00 EST : configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.non-classful nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: gated.nss<NSS number>.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- PRDB CHANGES: (Updated January 19, 1994) As of 1/19/95, ACKs and NAKs will no loger be required (or even read) in the processing of NACRs. In early 1995, as part of the transition to the new Internet Routing Registry (IRR), the Policy Routing Database (PRDB) will be retired. Many of the functions of the PRDB (including generation of router configurations for NSFNET) will be produced based on data from the Global Routing Registry. This change to the NSFNET Backbone service will involve the following changes: - The method for submitting new nets to be routed over AS690 will change. Instead of submitting a NACR to nsfnet-admin(a)merit.edu, you will need to submit a "route template" to auto-dbm(a)ra.net . - Additions and entries to the new registry will be made by the Home AS which creates the route for each net, rather than being submitted by a AS690 peer AS. - Most of the PRDB reports (listed above) will no longer be produced. Equivalent information for most of these reports is available from the global Routing Registry. These are major changes to the system. These changes are being made in order to migrate NSFNET customers and the global user community to a global Internet Routing Registry system, which will be more capable of supporting user needs after the termination of the NSFNET Backbone services in April 1995. For more information, set your web browser to http://www.ra.net/rrinfo.html , or use anonymous ftp to obtain the files "OVERVIEW" and from the directory "ftp.ra.net:pub/radb". Merit would like to minimize the number of problems that this transition may cause you. In order to help us help you through the transition, please send your concerns, your needs, and suggestions on how we can make this happen smoothly to merit-ie(a)merit.edu. The archived discussion list "db-disc(a)merit.edu" also exists for discussion of PRDB and RADB issues. Send a message to "db-disc-request(a)merit.edu" to subscribe. --Dale Johnson (dsj(a)merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nic.merit.edu machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files template.net, template.net.README, template.gate, and template.as. *** Note: As of March 1, 1994, NSFNET AUP NACRs must use the template.net *** (NACR) version 7.1, or the NACR will be returned unprocessed. ******************************* --Stephen McNutt Merit/NSFNET smm(a)merit.edu --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0

VB-95:01 - HP Security Vulnerability in Remote Watch
by CERT Bulletin 02 Mar '95

02 Mar '95

CERT Vendor-Initiated Bulletin VB-95:01 March 2, 1995 Topic: Security Vulnerability in Remote Watch Source: Hewlett-Packard Company To aid in the wide distribution of essential security information, the CERT Coordination Center is forwarding the following information from Hewlett-Packard. Hewlett-Packard urges you to act on this information as soon as possible. Their contact information is included in the forwarded text below; please contact them if you have any questions or need further information. ========================FORWARDED TEXT STARTS HERE============================ ------------------------------------------------------------------------- HEWLETT-PACKARD SECURITY BULLETIN: #00020, 31 January 95 ------------------------------------------------------------------------- Hewlett-Packard recommends that the information in the following Security Bulletin should be acted upon as soon as possible. Hewlett- Packard will not be liable for any consequences to any customer resulting from customer's failure to fully implement instructions in this Security Bulletin as soon as possible. _______________________________________________________________________ PROBLEM: Security vulnerability in Remote Watch in fileset WATCH-RUN for releases of HP-UX. PLATFORM: HP 9000 series 300/400s & 700/800s running HP-UX revisions 8.X, 9.X. DAMAGE: A vulnerability in Remote Watch exists allowing users to potentially gain increased privileges. SOLUTION: Apply patch PHSS_5136 (series 800 , HP-UX 9.X), or PHSS_5185 (series 800 , HP-UX 8.X), or PHSS_5107 (series 700 , HP-UX 9.X), or PHSS_5180 (series 700 , HP-UX 8.X), or PHSS_5120 (series 300/400, HP-UX 9.X), or PHSS_5168 (series 300/400, HP-UX 8.X). AVAILABILITY: All patches are available now. _______________________________________________________________________ I. Update A. It has been found that HP-UX systems with Remote Watch installed have this vulnerability. The vulnerability allows users to potentially gain increased privileges. If these patches are installed, then the vulnerability cannot be exploited. B. Fixing the problem The vulnerability can be eliminated from releases 8.X and 9.X of HP-UX by applying a patch. Hewlett-Packard recommends that all customers concerned with the security of their HP-UX systems apply the appropriate patch as soon as possible. C. How to Install the Patch (for HP-UX 8.X and 9.X) 1. Determine which patch is appropriate for your hardware platform and operating system: PHSS_5136 (series 800 , HP-UX 9.X), PHSS_5185 (series 800 , HP-UX 8.X), PHSS_5107 (series 700 , HP-UX 9.X), PHSS_5180 (series 700 , HP-UX 8.X), PHSS_5120 (series 300/400, HP-UX 9.X), PHSS_5168 (series 300/400, HP-UX 8.X), 2. Hewlett Packard's HP-UX patches are available via email and WWW (MOSAIC) To obtain a copy of the HP SupportLine email service user's guide, send the following in the TEXT PORTION OF THE MESSAGE to support(a)support.mayfield.hp.com (no Subject is required): send guide The users guide explains the process for downloading HP-UX patches via email and other services available. WWW (MOSAIC) service (downloading of patches) is also available via WWW (MOSAIC) our URL is: (http://support.mayfield.hp.com) 3. Apply the patch to your HP-UX system. 4. Examine /tmp/update.log for any relevant WARNINGs or ERRORs. This can be done as follows: a. At the shell prompt, type "tail -60 /tmp/update.log | more" b. Page through the next three screens via the space bar, looking for WARNING or ERROR messages. D. Impact of the patch and workaround No patches will be available for versions of HP-UX prior to 8.0. E. To subscribe to automatically receive future NEW HP Security Bulletins from the HP SupportLine mail service via electronic mail, send an email message to: support(a)support.mayfield.hp.com (no Subject is required) Multiple instructions are allowed in the TEXT PORTION OF THE MESSAGE, here are some basic instructions you may want to use: To add your name to the subscription list for new security bulletins, send the following in the TEXT PORTION OF THE MESSAGE: subscribe security_info To retrieve the index of all HP Security Bulletins issued to date, send the following in the TEXT PORTION OF THE MESSAGE: send security_info_list WWW (MOSAIC) service (Browsing of Bulletins) is also available via WWW (MOSAIC) our URL is: (http://support.mayfield.hp.com) Choose "Support News", then under Support News, choose "Security Bulletins" F. To report new security vulnerabilities, send email to: security-alert(a)hp.com =========================FORWARDED TEXT ENDS HERE============================= CERT bulletins, CERT advisories, information about FIRST representatives, and other information related to computer security are available for anonymous FTP from info.cert.org. CERT advisories and bulletins are also posted on the USENET newsgroup comp.security.announce. If you would like to have future advisories and bulletins mailed to you or to a mail exploder at your site, please send mail to cert-advisory-request(a)cert.org. If you wish to send sensitive incident or vulnerability information to CERT staff by electronic mail, we strongly advise that the e-mail be encrypted. The CERT Coordination Center can support a shared DES key, PGP (public key available via anonymous FTP on info.cert.org) or PEM (contact CERT staff for details). Internet E-mail: cert(a)cert.org Telephone: +1 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are on call for emergencies during other hours. Fax: +1 412-268-6989 CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 USA CERT is a service mark of Carnegie Mellon University.

1 0

Re: 60 Day Termination Notice (fwd)
by Sean Doran 02 Mar '95

02 Mar '95

>We've already ordered a backhoe - we figure we can take out the T3 and >bury the ENSS at the same time :-) Don't you need an environmental impact statement for the EPA first? I'm sure they wouldn't be overly pleased... :-) Saen.

5 5

60 Day Termination Notice (fwd)
by Elise Gerich 01 Mar '95

01 Mar '95

Hi, Some of you may receive this twice since it has been sent to the regional-techs list and FARNET, but it seemed important to try to reach as many folks as possible who might be impacted by this. The IBM, MCI, ANS, and Merit partnership during the NSFNET project was a cohesive collaborative effort, and I was really proud to be a part of it. I hope that those of you who continue to provide backbone services have as much fun and success as we did. --Elise > > -------------------------forwarded message-------------------------- > Date: Tue, 28 Feb 95 12:20:00 EST > Message-Id: <9502281720.AA03150(a)pepper.merit.edu> > To: becker(a)ans.net, dstaudt(a)nsf.gov, dvanbell(a)nsf.gov, phustone(a)nsf.gov > Subject: 60 Day Termination Notice > Cc: ema(a)merit.edu, epg(a)merit.edu, ittai(a)ans.net > Status: RO > > Dear Jordan, > It is with mixed feelings that Merit sends this notification > to ANS to terminate the NSFNET Backbone Service at the > following locations: > > ENSS 128 Palo Alto April 30, 1995 midnight PST > ENSS 129 Champaign April 30, 1995 midnight CST > ENSS 130 Argonne April 30, 1995 midnight CST > ENSS 131 Ann Arbor April 30, 1995 midnight EST > ENSS 132 Pittsburgh April 30, 1995 midnight EST > ENSS 133 Ithaca April 30, 1995 midnight EST > ENSS 134 Cambridge April 30, 1995 midnight EST > ENSS 135 San Diego April 30, 1995 midnight PST > ENSS 136 College Park April 30, 1995 midnight EST > ENSS 137 Princeton April 30, 1995, midnight EST > ENSS 139 Houston April 30, 1995, midnight CST > ENSS 140 Lincoln April 30, 1995, midnight CST > ENSS 141 Boulder April 30, 1995, midnight MST > ENSS 142 Salt Lake City April 30, 1995, midnight MST > ENSS 143 Seattle April 30, 1995, midnight PST > ENSS 144 Moffett Field April 30, 1995, midnight PST > ENSS 145 College Park April 30, 1995, midnight EST > ENSS 146 DC April 30, 1995, midnight EST > ENSS 147 MFS April 30, 1995, midnight EST > > This notification also pertains to the cessation of NSFNET > Backbone Service at the Ameritech, MFS, PacBell, and > Sprint Network Access Points. A termination notice was > issued previously for ENSS 138 (Atlanta) so that node > is not included in this termination notice. > > It is sad to note that at midnight in each respective time > zone, the service that Merit, ANS, IBM, and MCI have > collaborated to provide over the last seven years will > cease to exist. It is also with pleasure that we > complete this grand experiment on such a successful > note. I think that this partnership has succeeded > beyond any of our dreams. It has been fun! > > --Elise > -------------------------end of forwarded message----------- >

1 0

Re: 60 Day Termination Notice (fwd)
by swolff＠cisco.com 01 Mar '95

01 Mar '95

>I envisage a fancy-dress gathering in Ann Arbor and D.C. to >party, get blitzed, and then watch as ENSSes get turned off, >and as a big silver ball descends to mark the end of the >NSFNET backbone service... > >BTW, out of curiosity, will the ENSSes get turned off, just >shutdown(8)ed, or have the interfaces ifconfig-ed off? Gee. I hoped each ENSS was gong to get an Ignite packet to /dev/thermite. <sigh> -s

2 1

Re: 60 Day Termination Notice (fwd)
by Sean Doran 01 Mar '95

01 Mar '95

Wow. History in the making. This is better than CNN. I envisage a fancy-dress gathering in Ann Arbor and D.C. to party, get blitzed, and then watch as ENSSes get turned off, and as a big silver ball descends to mark the end of the NSFNET backbone service... BTW, out of curiosity, will the ENSSes get turned off, just shutdown(8)ed, or have the interfaces ifconfig-ed off? Sean. (who is prepared to sing Auld Lang Syne :) )

5 5

Re: 60 Day Termination Notice (fwd)
by Farrell E Gerbode 28 Feb '95

28 Feb '95

Roger and copy, NSFNET, and thanks for the smooth ride. Thanks for all your patience and your help over the years, Elise. It seems that it was not all that long ago since HWB, an now-unknown IBMer near Atlanta, and I stood around the consoles on the IDNX switches in our respective cities and watched the Frac-T1 NSFNET come up completely for the first time. With fond memories of inside delivery, ABAM-type wire, target practice in the swamp, power reconfiguration at PSC,... Farrell

1 0