T.R | Title | User | Personal Name | Date | Lines |
---|
1407.1 | Tis a feature... | REQUE::whocrz.zko.dec.com::Gumbel | Dick Gumbel | Thu May 22 1997 16:01 | 10 |
|
This is a feature. See page 3-2 of the Commands and Utilities Reference
manual. If you wildcard the host, then the username MUST ALSO be
wildcard. In other words, all users on the remote hosts map into
the localuser specified.
Dick Gumbel
ObjectBroker development
|
1407.2 | | WLDBIL::KILGORE | BEAmer Bill | Thu May 22 1997 16:06 | 12 |
|
The combination of explicit remote user and wildcard remote host is
specifically disallowed by the command line interface code. I also
believe the combination is not checked for at runtime when looking for
applicable proxies (I forced the illegal combination into the security
registry, but it wasn't picked up during a proxy check).
The history behind the decision to disallow this combination is vague.
You could make a formal request for this functionality through
the product manager...
|
1407.3 | | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Thu May 22 1997 17:31 | 14 |
| > A customer wan't to use wildcard for HOST only. He has 800 users and they may
> login an any of 300 PC's. He wan't to have the same username in Windows and
> VMS. But allow any host.
Does the customer have physical security of their entire network
(ie. no one could plug in a laptop or handheld computer into
the network)?
The problem with wildcarding the hostname is that it makes it even
easier than it already is to gain unauthorized access to the server.
But if the customer is sure their physical network is secure, and
has system management control of all the systems, then I agree
with Bill, give them the rope .....
|
1407.4 | | RULLE::KLASSON | Sven-Olof Klasson @GOO | Fri May 23 1997 10:38 | 10 |
| Hi,
Thanks for the replies.
I have recommended the customer to use the following proxy
OBB> add proxy * /remote=(user=*,host=sprutt)
I tried it and it seems to match the same local username as
the username on the remote host.
Sven-Olof
|