On Dec 30, 2011, at 5:42, Johnny Billquist <bqt at softjar.se> wrote:
On 2011-12-30 02.44, Brian Hechinger wrote:
Agh, magica. Those were the good old days. :)
Magica is still around. I only wish I could turn her on more often. Cooling is the problem.
I really need to go dig my /70 out and start running it one of these days. That and my /34a. I don't currently have anywhere appropriate to run them, however. :(
Hum...? I think that it terminated on our VAX 8650.
That is the only thing I can remember on which I had serial ports to spare. Running Ultrix on the machine at the time.
Maybe that's it and I'm misremembering. I remember it ran Ultrix but remember it being MIPS for some reason.
That machine is also still around, but also powered off because of cooling. Big ECL machine. Lots of heat... But it's KRILLE (1.8).
It can boot VMS, Ultrix and NetBSD. Only got DECnet for VMS though.
Yeah, a shame it's too expensive to run. Nice machine.
-brian
Johnny,
You are talking about the INFO.TXT file that is located in the default
DECnet directory.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, December 30, 2011 8:46 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Someone (I don't remember who) had a suggestion a year or two ago, that
machines should have a file in the default DECnet directory, with some
basic information about the node in a defined format, and the file with
a defined name, so that anyone could easily extract and figure out
information about atleast running nodes.
Maybe that idea could be expanded upon?
Seems very tedious for people to constantly mail updates... Although I
could of course take additional information as I'm already keeping a
nodename database in Datatrieve. No big deal to add additional
information if we'd like that... Then I can generate any kind of reports
based on this. As can others (if they can get remote Datatrieve to work
against RSX.)
Johnny
On 2011-12-30 15.59, hvlems at zonnet.nl wrote:
Rok, the spreadsheet that I distributed also has a sheet called
'hosts'.
I'm willing to expand that list though I have the basty feeling it's
going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a
relevant command but if so my ncl is *very* rusty and it seems I'm
pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char)
commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single
cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms
with f$element ;-)
So anyone who mails me node data in the format listed gets data
included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar<rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To:<hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology
28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated
list of
all of HECnet? Are you looking for data on all known nodes, even end
nodes
and ones that don't normally run 24x7? And how much data do you want
for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's
the
case! OTOH, I thought you were making a list of the active routing
nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will
not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any
number of
editors. Any volunteers? Hans?
--
Regards, Rok
On 2011-12-30 17.28, Gregg Levine wrote:
Incidentally Johnny Billquist, have we ever worked out a reasonable
method of assigning a dynamic IP address to be reachable by the
efforts of the network? I know it works for websites.....
Uh? Not sure what you mean?
Johnny
Someone (I don't remember who) had a suggestion a year or two ago, that machines should have a file in the default DECnet directory, with some basic information about the node in a defined format, and the file with a defined name, so that anyone could easily extract and figure out information about atleast running nodes.
Maybe that idea could be expanded upon?
Seems very tedious for people to constantly mail updates... Although I could of course take additional information as I'm already keeping a nodename database in Datatrieve. No big deal to add additional information if we'd like that... Then I can generate any kind of reports based on this. As can others (if they can get remote Datatrieve to work against RSX.)
Johnny
On 2011-12-30 15.59, hvlems at zonnet.nl wrote:
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar<rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To:<hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
So I was digging through the garage (we just moved and it is packed full of crap) and ran across the VAXstation 4000/90 so I pulled it out. I was very excited until I realized I had a problem. Mainly, no way to plug it into the network.
Crap, now where are my AUI transceivers buried?
I'll find one. I swear! :)
-brian
I think SLAVE::INFO.TXT is a fairly good example of the format.
Fortunately you appear to be using pretty much the same format as I am.
The good thing about standards is that there are so many to choose from
:-)
Bob
On Fri, 30 Dec 2011, Gregg Levine wrote:
reachable via the Internet via SSH and then VNC. The listing of who
and what regarding the attempted break-ins on the SSH port is
Speaking of SSH, for those that run Linux on the list and like to leave ssh open - I normally use public/private keys but I don't normally have my laptop or key-on-a-stick with me so I allow passwords as well on my home server. A little program called "sshdfilter" automatically watches logs (via a named pipe) and when someone comes knocking (or guesses a password wrong x times) it automatically firewalls the IP for a good long time. I use it on most any host I expose to the Internet with ssh.
Hopefully this isn't too offtopic ...
Fred
On 30/12/2011 16:15, Bob Armstrong wrote:
Bob describes the format in his version. I don't know how up-to-date it
is... Bob???
The format description is as current as any that I know about.
The actual data about my local machines is a little out of date, but the
syntax of the file is correct.
$ TYPE LEGATO::INFO.TXT
Bob
I think SLAVE::INFO.TXT is a fairly good example of the format.
Regards, Mark.
On Fri, Dec 30, 2011 at 8:05 AM, Fred <fcoffey at misernet.net> wrote:
On Fri, 30 Dec 2011, Johnny Billquist wrote:
I'm still looking for script kiddies trying to hack MIM. Once in a while I
do get people who try to login repeatedly as root, falken, and other known
Unix accounts. Poor kids... ;-)
I'm glad I'm not the only one!
I leave telnet open on one of my VMS hosts and love looking at the audit
logs. Most of the time folks just disconnect without even trying a
username. Other times it is "Administrator" and their ilk ... Once or twice
a month I'll read the logs and just laugh. You'd have to know me pretty
well to guess the password for the few accounts on the system, I change them
every 90, and of course intrusion detection is going to get you long before
you get close. :)
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
Hello!
I quite agree. On my resident Linux (Intel) platform here, who also
hosts my website, I would when vacation time loomed set it to be
reachable via the Internet via SSH and then VNC. The listing of who
and what regarding the attempted break-ins on the SSH port is
hilarious. It would be the classic dictionary attack at work. That's
the exact same one tried out on a VAX running BSD 4,2 all the way back
in 1987 (or so), the cuckoo's egg case at work.
Come to think of it I would also from time to time check his error and
access logs for the web serving functions. It's downright laughable
the preposterous efforts people would try that would cause anything
except Apache on Linux to stumble.
Incidentally Johnny Billquist, have we ever worked out a reasonable
method of assigning a dynamic IP address to be reachable by the
efforts of the network? I know it works for websites.....
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Bob describes the format in his version. I don't know how up-to-date it
is... Bob???
The format description is as current as any that I know about.
The actual data about my local machines is a little out of date, but the
syntax of the file is correct.
$ TYPE LEGATO::INFO.TXT
Bob
I would take a look at LEGATO::INFO.TXT as a start. Bob describes the format in his version. I don't know how up-to-date it is... Bob???
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Friday, December 30, 2011 11:02 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry Steve I wasn't aware of info.txt. I"l find a copy and look at it.
-----Original Message-----
From: "Steve Davidson" <jeep at scshome.net>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 10:17:19
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: RE: [HECnet] Re: Topology 28-Dec-2011
The INFO.TXT files in the default DECnet directories already give this information. An agreed apon format has already been established. Can you make use of that?
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Friday, December 30, 2011 9:59 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar <rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To: <hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
Sorry Steve I wasn't aware of info.txt. I"l find a copy and look at it.
-----Original Message-----
From: "Steve Davidson" <jeep at scshome.net>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 10:17:19
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: RE: [HECnet] Re: Topology 28-Dec-2011
The INFO.TXT files in the default DECnet directories already give this information. An agreed apon format has already been established. Can you make use of that?
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Friday, December 30, 2011 9:59 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar <rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To: <hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
Yup, I stand corrected. Use a comma instead since my default csv separator is a semicolon.
------Origineel bericht------
Van: Bob Armstrong
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Re: Topology 28-Dec-2011
Verzonden: 30 december 2011 16:03
<address>-<name>-<hardware>-<os name>
Um, don't most hardware names contain dashes? VAX-11/730, PDP-11/70,
VAX-8350, ... ?
Or are you looking for something more basic - VAX, PDP, PC, ??
Bob
The INFO.TXT files in the default DECnet directories already give this information. An agreed apon format has already been established. Can you make use of that?
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Friday, December 30, 2011 9:59 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar <rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To: <hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
<address>-<name>-<hardware>-<os name>
Um, don't most hardware names contain dashes? VAX-11/730, PDP-11/70,
VAX-8350, ... ?
Or are you looking for something more basic - VAX, PDP, PC, ??
Bob
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar <rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To: <hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
I can add whatever interesting information and I can add any number of
editors.
Once upon a time I tried to keep a list of the HECnet nodes - there's a
copy, albeit somewhat out of date, here-
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
feel free to copy whatever data from that one that you want.
FWIW, you're probably at least the third person to attempt an inventory of
HECnet, but don't let that discourage you :-)
Bob
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
This should round out the map for area 19.
Rok -
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Bob
Rok,
PLUTO:: (19.23) DECnet/E 4.1 is up. MARS:: (19.84) is a mess and I don't have a workable RSX-11M-PLUS distribution to fix it so I think it is a complete loss. SIGH...
The STARS:: VAXcluster (19.77) and hopefully the GALAXY:: VMScluster (19.150) will be up either this evening or tomorrow.
This should round out the map for area 19.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rok Vidmar
Sent: Friday, December 30, 2011 6:16 AM
To: hecnet at update.uu.se
Subject: [HECnet] Re: Topology 28-Dec-2011
Step closer to CSV:
Have a peek:
<https://docs.google.com/spreadsheet/ccc?key=0AmeaHhGPxCnRdFpmdXhhcG1YODd1UW…>
--
Regards, Rok
On Fri, 30 Dec 2011, Johnny Billquist wrote:
I'm still looking for script kiddies trying to hack MIM. Once in a while I do get people who try to login repeatedly as root, falken, and other known Unix accounts. Poor kids... ;-)
I'm glad I'm not the only one!
I leave telnet open on one of my VMS hosts and love looking at the audit logs. Most of the time folks just disconnect without even trying a username. Other times it is "Administrator" and their ilk ... Once or twice a month I'll read the logs and just laugh. You'd have to know me pretty well to guess the password for the few accounts on the system, I change them every 90, and of course intrusion detection is going to get you long before you get close. :)
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
An 8650 sure makes a fine central heating unit !
-----Original Message-----
From: Johnny Billquist <bqt at softjar.se>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 11:42:42
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Circuit costs - Area 19 revised
On 2011-12-30 02.44, Brian Hechinger wrote:
Agh, magica. Those were the good old days. :)
Magica is still around. I only wish I could turn her on more often.
Cooling is the problem.
What was that monster MIPS box you had that you terminated the serial tunnel on? Wasn't it the one that came in the same style as the VAX 6000?
Hum...? I think that it terminated on our VAX 8650.
That is the only thing I can remember on which I had serial ports to
spare. Running Ultrix on the machine at the time.
That machine is also still around, but also powered off because of
cooling. Big ECL machine. Lots of heat... But it's KRILLE (1.8).
It can boot VMS, Ultrix and NetBSD. Only got DECnet for VMS though.
Johnny
-brian
On Dec 29, 2011, at 18:38, Johnny Billquist<bqt at softjar.se> wrote:
Fun story:
A number of years ago I had a russian guy who asked for a guest account on Magica (MIMs predecessor, a real PDP-11/70, which is still around).
A day or so later, the system had crashed, and I had received an email with an apology from the russian guy for crashing the system.
It turned out that he and some friends had a russian cloned RSX system from some old age, which they had done plenty of hacking and working on, and in the process had found some potential exploits. Curious as they were, they decided to check if those exploits were still around in the latest version of RSX, which they had not touched before. Since I had protected all the directories and source files from random access, they couldn't check the source code, but they could write programs, so they did.
And yes, the possible exploits and holes were still around, and thus Magica crashed. This was in V4.5, if I remember right. I thanked them for the information, rebooted the system and sent what they told be on towards Mentec. The russian promised to not do that again, and I just thought it was fun.
V4.6 fixed one or two of the problems, but a couple of them are still around.
So, once it a while, you actually do find someone who knows what they are doing, but such people are normally not evil.
I'm still looking for script kiddies trying to hack MIM. Once in a while I do get people who try to login repeatedly as root, falken, and other known Unix accounts. Poor kids... ;-)
Johnny
On 2011-12-29 14.17, Brian Hechinger wrote:
Or Solaris, or *BSD, or.....
If they can't run a script on linux or windows they can't hack in.
Yes, I have a very poor view of crackers these days. :-D
-brian
On 12/29/2011 4:24 AM, hvlems at zonnet.nl wrote:
MIM uses guest/guest and a script that asks for your name. Not secure
but then again what's there to steal? And I doubt whether hackers know
their way in any DEC OS ...
-----Original Message-----
From: "Steve Davidson"<jeep at scshome.net>
Sender: owner-hecnet at Update.UU.SE
Date: Wed, 28 Dec 2011 22:42:17
To:<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: RE: [HECnet] Circuit costs -
Area 19 revised
I do not create any accounts unless asked by the node owner...
Only some machines have guest accounts and as far as I know we have no
standard. This site does not have guest accounts. I do create accounts
on request for some of the machines. Mostly PLUTO::, because it is the
only RSTS/E system on HECnet, but it is not up all of the time. With
the exception of PLUTO:: none of my machines offer anything that HECnet
users don't already have.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Brian Hechinger
Sent: Wednesday, December 28, 2011 10:09 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Circuit costs - Area 19 revised
Ah, no guest accounts have been setup unless Steve did it so I'm
assuming he hasn't. I'll create some guest accounts tomorrow.
What's the standard HECnet guest?
-brian
On Dec 28, 2011, at 19:43, hvlems at zonnet.nl wrote:
Hi Brian, It may have been an example of the NML issue discussed here
a couple of days ago. Anyway set host rifter worked fine. I tried
guest/guest and hecnet/guiest but that didn't work. Well, I quit for the
day, it's late out here.
Hans
------Origineel bericht------
Van: Brian Hechinger
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Circuit costs - Area 19 revised
Verzonden: 29 december 2011 01:07
On 12/28/2011 6:44 PM, H Vlems wrote:
Brian, is RIFTER a phase V node? NCP set exec node RIFTER doesn't
work, even
when I jump to SG1 first.
No, it's a Phase IV node.
-brian
On 2011-12-30 02.44, Brian Hechinger wrote:
Agh, magica. Those were the good old days. :)
Magica is still around. I only wish I could turn her on more often. Cooling is the problem.
What was that monster MIPS box you had that you terminated the serial tunnel on? Wasn't it the one that came in the same style as the VAX 6000?
Hum...? I think that it terminated on our VAX 8650.
That is the only thing I can remember on which I had serial ports to spare. Running Ultrix on the machine at the time.
That machine is also still around, but also powered off because of cooling. Big ECL machine. Lots of heat... But it's KRILLE (1.8).
It can boot VMS, Ultrix and NetBSD. Only got DECnet for VMS though.
Johnny
-brian
On Dec 29, 2011, at 18:38, Johnny Billquist<bqt at softjar.se> wrote:
Fun story:
A number of years ago I had a russian guy who asked for a guest account on Magica (MIMs predecessor, a real PDP-11/70, which is still around).
A day or so later, the system had crashed, and I had received an email with an apology from the russian guy for crashing the system.
It turned out that he and some friends had a russian cloned RSX system from some old age, which they had done plenty of hacking and working on, and in the process had found some potential exploits. Curious as they were, they decided to check if those exploits were still around in the latest version of RSX, which they had not touched before. Since I had protected all the directories and source files from random access, they couldn't check the source code, but they could write programs, so they did.
And yes, the possible exploits and holes were still around, and thus Magica crashed. This was in V4.5, if I remember right. I thanked them for the information, rebooted the system and sent what they told be on towards Mentec. The russian promised to not do that again, and I just thought it was fun.
V4.6 fixed one or two of the problems, but a couple of them are still around.
So, once it a while, you actually do find someone who knows what they are doing, but such people are normally not evil.
I'm still looking for script kiddies trying to hack MIM. Once in a while I do get people who try to login repeatedly as root, falken, and other known Unix accounts. Poor kids... ;-)
Johnny
On 2011-12-29 14.17, Brian Hechinger wrote:
Or Solaris, or *BSD, or.....
If they can't run a script on linux or windows they can't hack in.
Yes, I have a very poor view of crackers these days. :-D
-brian
On 12/29/2011 4:24 AM, hvlems at zonnet.nl wrote:
MIM uses guest/guest and a script that asks for your name. Not secure
but then again what's there to steal? And I doubt whether hackers know
their way in any DEC OS ...
-----Original Message-----
From: "Steve Davidson"<jeep at scshome.net>
Sender: owner-hecnet at Update.UU.SE
Date: Wed, 28 Dec 2011 22:42:17
To:<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: RE: [HECnet] Circuit costs -
Area 19 revised
I do not create any accounts unless asked by the node owner...
Only some machines have guest accounts and as far as I know we have no
standard. This site does not have guest accounts. I do create accounts
on request for some of the machines. Mostly PLUTO::, because it is the
only RSTS/E system on HECnet, but it is not up all of the time. With
the exception of PLUTO:: none of my machines offer anything that HECnet
users don't already have.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Brian Hechinger
Sent: Wednesday, December 28, 2011 10:09 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Circuit costs - Area 19 revised
Ah, no guest accounts have been setup unless Steve did it so I'm
assuming he hasn't. I'll create some guest accounts tomorrow.
What's the standard HECnet guest?
-brian
On Dec 28, 2011, at 19:43, hvlems at zonnet.nl wrote:
Hi Brian, It may have been an example of the NML issue discussed here
a couple of days ago. Anyway set host rifter worked fine. I tried
guest/guest and hecnet/guiest but that didn't work. Well, I quit for the
day, it's late out here.
Hans
------Origineel bericht------
Van: Brian Hechinger
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Circuit costs - Area 19 revised
Verzonden: 29 december 2011 01:07
On 12/28/2011 6:44 PM, H Vlems wrote:
Brian, is RIFTER a phase V node? NCP set exec node RIFTER doesn't
work, even
when I jump to SG1 first.
No, it's a Phase IV node.
-brian
On 2011-12-23 15.51, Brian Hechinger wrote:
RIFTER$ mcr ncp show known circuits
[...]
Nice...
The last time I was joined to HECnet was 11 years ago!!
Long time no see. :-)
That got me thinking about that time. Things were much different back
then. Johnny's bridge program didn't bridge ethernet at that time. It
bridged serial!
Gha! I was trying to remember who might have been around back then. So that was you... I think that makes you the first place outside my own experimentation that was connected to HECnet. :-)
Serial ports was my first solution. It seemed like a very easy thing to do, and it worked just fine. The only "problem" was that DECnet over asynch serial ports are slow, since they are limited to 9600 bps.
I might have run with that for at most a year before I wrote the bridge program to replace it.
I also needed physical serial ports all over the place. :-)
Johnny
