On 2012-11-02 02:23, Paul_Koning at Dell.com wrote:
On Nov 1, 2012, at 9:12 PM, Dave McGuire wrote:
On 11/01/2012 05:14 PM, Paul_Koning at Dell.com wrote:
Hey Johnny...this is probably my DECnet inexperience showing...but
when I try to access MIM from RSTS/E, it prompts me for a username
and password. Should it do that? I get right in (for file
operations) from VMS.
RSTS always prompts for user ID for interactive logins. It will then
prompt for a password unless the account you asked for is set not to
require a password.
On the other hand, DECnet objects that work in the context of some
user (like FAL) can be set to have a default user ID that is used
when no access control parameters are included in the connect.
Ahh ok, I get it. That sounds very familiar; I know I've read about
it before. So you're saying that FAL on MIM's end would be set up with
a default user ID, or I'd configure something within DECnet on my end to
pass a default ID?
The former. The receiving end (MIM) decides what the access rules on that end are.
True, but it's not that simple in the end. :-)
Since FAL do have a requirement for authentication of some sort (and I'm not willing to drop that), you need to present a user to RSX. VMS have this concept of a default user if none is provided, RSX do not have this default user concept.
So far, things are easy and obvious.
There is one more thing that relates here, and that is proxy information, which noone (but me) have mentioned so far. The source side of a DECnet connection can also pass on the user identification of the source process to the destination, and the destination side can map that remote user to any local user it wants to, thus getting the user identification for the local system that way instead of having to explicitly pass username and password in the connect request.
That is something of a shared responsibility between both sides, where both have to agree on doing this, and the destination must also have a mapping for that remote user to a local user in order for it to be accepted.
Now, I've set up a proxy user on MIM, which essentially maps *::* to the local user DECNET, thereby creating something pretty similar to a default account. But it do require that the connecting side sends proxy user information to MIM, or else it will not work.
But yes, in the end, the access rules are defined by the receiving end - MIM. But the sending side needs to provide information one way or another.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
From: Dave McGuire <mcguire at neurotica.com>
On 10/31/2012 03:34 PM, Sampsa Laine wrote:
I thought encryption and commercial messages were strictly verboten
on HAM stuff.
They are. So let's not encrypt stuff. And how much commercial data
flows across HECnet? ;)
I'd be much more concerned about the rules on swearing! I'd violate that
in a more or less continuous stream if I didn't know what I was typing was
going over the air...
This is a wonderfully bad idea -- I love it. Somewhere I have an old
DUP11 that I picked up 20+ years ago with the idea of using it for packet.
The AX.25 spec and a kit-built Flesher TU1200 are around here somewhere too ...
I really wish I'd moved on that project back when there would have been people
to talk to! (TNCs came along about ten seconds after I lost interest, natch -
all the name "Kantronics" means to me is the Rockhound!)
John Wilson, KC1P
D Bit
On Thu, Nov 1, 2012 at 11:59 PM, Dave McGuire <mcguire at neurotica.com> wrote:
On 11/01/2012 11:56 PM, Cory Smelosky wrote:
On Nov 1, 2012, at 11:44 PM, "Bob Armstrong" <bob at jfcl.com> wrote:
There are mountains...that'd be tough.
Bigger tower :-)
We can borrow some of the ideas from AT&T Long Lines and have our own hobbyist telecom grid. I mean, it's the next logical step right? Know anyone with large fibre or copper spools laying around? ;)
We can do this.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello!
Currently the longest run for WiFi happens to be around the distance
from the hills somewhere inside Clark County NV to about the hills
somewhere by Salt Lake Utah. But I'm not sure what was used.
Oh and look into how the return to Mars prior to the group we've got
up there now accomplished its work.
Oh and Dave all of them used the shower.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 11/01/2012 11:56 PM, Cory Smelosky wrote:
On Nov 1, 2012, at 11:44 PM, "Bob Armstrong" <bob at jfcl.com> wrote:
There are mountains...that'd be tough.
Bigger tower :-)
We can borrow some of the ideas from AT&T Long Lines and have our own hobbyist telecom grid. I mean, it's the next logical step right? Know anyone with large fibre or copper spools laying around? ;)
We can do this.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Nov 1, 2012, at 11:44 PM, "Bob Armstrong" <bob at jfcl.com> wrote:
There are mountains...that'd be tough.
Bigger tower :-)
We can borrow some of the ideas from AT&T Long Lines and have our own hobbyist telecom grid. I mean, it's the next logical step right? Know anyone with large fibre or copper spools laying around? ;)
Bob
On 11/01/2012 11:44 PM, Bob Armstrong wrote:
There are mountains...that'd be tough.
Bigger tower :-)
I like the way you think. :)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
And licenses. ;)
It's pretty easy to pass the test, especially for technician. I'm a VE
(that's "volunteer examiner") and we run regular testing sessions here in
Silicon Valley twice a month. Almost everybody who comes in to take the
technician test passes - even little kids :-)
Bob WU6V
On 11/01/2012 11:35 PM, Bob Armstrong wrote:
We'd probably use DDCMP to get it to the async level, right?
Maybe. I know that AX.25 has a protocol ID byte that specifies the packet
type being piggybacked - I'm pretty sure IP is 0xCC. It might be that
someone has already implemented a DECnet payload, but it's a long shot.
I doubt it. We could, though.
We could build our own TNCs that spoke 1200/9600 baud AX.25 on one side
and DDCMP on the other. All it really takes is some firmware... That'd be a
really cool gizmo, and completely useless to anyone except for a couple of
people to boot :-)
I would LOVE to do that. That sounds like great gobs of fun.
Realistically, a smarter thing might be to try WiFi. I think the current
distance record for WiFi is something like 250 miles; how far is between you
and Steve?? Of course, you'll need some pretty tall towers...
I don't know specifically where he is, but I think he's east of me.
There are mountains...that'd be tough.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 11/01/2012 11:40 PM, Cory Smelosky wrote:
We'd probably use DDCMP to get it to the async level, right?
Maybe. I know that AX.25 has a protocol ID byte that specifies the packet
type being piggybacked - I'm pretty sure IP is 0xCC. It might be that
someone has already implemented a DECnet payload, but it's a long shot.
We could build our own TNCs that spoke 1200/9600 baud AX.25 on one side
and DDCMP on the other. All it really takes is some firmware... That'd be a
really cool gizmo, and completely useless to anyone except for a couple of
people to boot :-)
Realistically, a smarter thing might be to try WiFi. I think the current
distance record for WiFi is something like 250 miles; how far is between you
and Steve?? Of course, you'll need some pretty tall towers
And licenses. ;)
Well, get studyin'!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
