On 06/10/2018 05:17 PM, Jon Trulson wrote:
This is still an issue and I opened a ticket for it a week or so ago
(ttsession). Wouldn't surprise me if rpc.ttdbserver has that issue as
well. At XiG, we recommended never to run dtspcd or rpc.ttdbserver
unless you really had a need to, and we never enabled them by default :)
Having been on the ToolTalk team at Sun and an original CDE Sun team
developer, and helped with rpc.cmsd, I can tell you that rpc.ttdbserver,
dtspcd, and rpc.cmsd, were designed for intranet only!
All of them did (not sure if they still do), assume the UID is the same
across systems. Clearly not valid on the big net.
dtspcd was only mildly tweaked from the original HP spcd. And spcd was
written on SVR3, long before most people ever heard of the Internet. And
long before anyone cared about hackers.
With rpc.ttdbserver, is all you have to do (unless it has been updated),
is make a user with the same UID on your system, and you can remotely
execute TT on a system where you can connect.
With rpc.cmsd, matching UID's can see each others calendars.
dtspcd - was always a mysterious mess of code. When I registered dtspcd
on port 6112 at IANA, they wanted to know what it did. I had a hell of
time, because no one could find the original developers to find out what
it did. Still not sure.
So: --> Most diffidently, absolutely, positively, do NOT run them over
the Internet. :-)
--
Doug Royer - (http://DougRoyer.US http://goo.gl/yrxJTu )
douglasro...@gmail.com
714-989-6135
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
