HP3000-L Archives

February 1997, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Wed, 26 Feb 1997 11:18:05 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
Gregory writes about Client Server.

I would advise sockets. If you are writing in Cobol and Image, read and
write to a socket.
At least that way you'll be in command on what you do with what you
receive.

If you allow outsiders to establish a session, well they could do
anything - if they found out how to be manager.sys.

I would also not attach the HP3000 to the internet directly unless
through firewall/routers etc.

Mail me privately for Cobol to socket stuff. Look at our web site
http://www.bankmed.co.za for an example of how it works.

Regards

Neil




> -----Original Message-----
> From: HP-3000 Systems Discussion [SMTP:[log in to unmask]] On
> Behalf Of Stigers, Gregory - ANDOVER
> Sent: Tuesday, February 25, 1997 11:28 PM
> To:   [log in to unmask]
> Subject:      daemons, NS-VT, and TELNET
>
> I am about to get out of my league here, but we are co-developing an
> application using the 3K as a data server with another software
> company
> (using IMAGE and COBOL no less!). One of their people wanted me to
> turn
> on TELNET so that the client can talk to the HP across TCP/IP,
> replacing
> the current DTC / serial connections currently used by the
> application.
> Problem is, our IP addresses are real, and I don't want intrepid souls
> hacking our 3K from some Internet connection. Their guy couldn't find
> specs for NS/VT to use that as a service. But when I told him about
> our
> IP addresses, he was less excited about turning on TELNET for much the
> same security concerns.
>
> I know that their must be more than one way to skin this cat (no
> offense). We might be able to add filtering to the router, although
> that
> is less than sure. I bet someone sells some products to do something
> like this; but we are understandably reluctant to throw money at the
> problem, especially without knowing the inner workings of the
> solution.
> Perhaps we could write our own listeners, but I'm not that smart this
> morning, and there is the same chance of someone smarter than us
> finding
> the whole in our security. We could get the NS/VT spec and use that if
> that can be done (Wirt?), although that locks that piece into only
> being
> useful on the 3K. TANSTAAFL. Any ideas, anyone?
>
>
> Opinions are mine. Your rights may vary from state to state.

ATOM RSS1 RSS2