Kelvin,

Telnet doesn't use any kind of encryption in it's transfers so anyone
"sniffing" your data stream would not have any problems pulling things out
like your telnet login and password along with any of the data you send back
and forth.  On the other hand SSH I believe uses 128 bit encryption so that
whoever is sniffing your data will not be able to get anything out of it
unless they have a 18-wheeler full of supercomputers to work on it.  If you
are just  going across your internal LAN you shouldn't have any problem
using Telnet unless you have internal saboteurs.

Matt Schneider 
Programmer/System Administrator 
SKLD Information Services, LLC 



-----Original Message-----
From: Poon, Kelvin (Infomart) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 22, 2003 7:36 AM
To: 'Martin Moss'
Cc: '[EMAIL PROTECTED]'
Subject: RE: [Perl-unix-users] Perl and UNix
Importance: High



Thank you for your advice, but I just want to ask you one more question.
Why is Telnet not secure?  What kind of security problems will I face if I
do use Net::Telnet to do so.  

The other solution I was thinking of is LWP, but I am not sure how that
would work.

Kelvin
-----Original Message-----
From: Martin Moss [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 1:44 PM
To: Peter Eisengrein; 'Poon, Kelvin (Infomart)'
Cc: [EMAIL PROTECTED]
Subject: Re: [Perl-unix-users] Perl and UNix


Whilst Net::Telnet is a groovy thing, Telnet isn't as secure as ssh.
I haven't had any use of the Net::SSH stuff out there, but perhaps it would
be a consideration,

Regards

Marty
----- Original Message -----
From: "Peter Eisengrein" <[EMAIL PROTECTED]>
To: "'Poon, Kelvin (Infomart)'" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, January 21, 2003 6:46 PM
Subject: RE: [Perl-unix-users] Perl and UNix


> http://www.cpan.org
> http://search.cpan.org
>
>
>
> -----Original Message-----
> From: Poon, Kelvin (Infomart) [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 21, 2003 9:39 AM
> To: 'Thomas_M'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: [Perl-unix-users] Perl and UNix
>
>
> Thanks a lot for all anyone who replied, thanks
>
> I had been reading what you guys contribute and I think Net::Telnet will
be
> a good way I might try that.  I was trying to find the cpan site to
download
> that module...but can't find that site, can anyone give me more
information
> about that? thanks
>
> Kelvin
>
> -----Original Message-----
> From: Thomas_M [mailto:[EMAIL PROTECTED]]
> Sent: January 21, 2003 8:16 AM
> To: 'Poon, Kelvin (Infomart)';
> '[EMAIL PROTECTED]'
> Subject: RE: [Perl-unix-users] Perl and UNix
>
>
> Poon, Kelvin wrote:
> > Ok, I need a perl script that opens/access a file on a Unix
> > system (RS6000/AIX to be specific).  Well, you would think
> > this is a beginner problem, and yes it would be if I told you
> > ur perl script is on the unix system itself.  BUt the problem
> > is my perl script has to be outside of that system.  So which
> > means, my perl script is going  to be placed on my PC and I
> > need that perl script to access the Unix machine and then
> > gets the files out from it.
>
> There are many ways to do it. Leave perl aside for a moment and ask
yourself
> how you would get that file from the unix system now. Would you telnet
into
> the box and 'cat' it? Would you connect with an FTP program and transfer
it?
> Do you have the ability to set up the unix box as a Windows file server
> using Samba?
>
> If you can FTP, use Net::FTP. If you need to telnet, use Net::Telnet. If
you
> can set it up as a Samba file server, you need not do anything special on
> the Windows side.
>
> > It is a text file I need to get and it is used in my CGI program.
>
> This adds a performance consideration. Can your CGI program run on the
unix
> machine? That would be ideal. Otherwise, use caching. Make sure you don't
> unnecessarily transfer the file on each CGI request. You can do this a
> number of ways. Why not let the program that updates the file also
transfer
> it to your web server? If that is not possible, perhaps you can write a
cron
> job (aka Scheduled Task) that pushes the file to your web server every X
> minutes. If you are constrained to using perl on the Windows system only,
> you could set up a scheduled task that fetches the file every X minutes
> using one of the techniques above. If none of the above is possible, you
can
> do the caching in your CGI program: use the local file if it is less than
X
> minutes old, otherwise retransfer it.
>
> Hope this helps,
>
> - Mark.
>
> --
> Mark Thomas                    [EMAIL PROTECTED]
> Internet Systems Architect     User Technology Associates, Inc.
>
> $_=q;KvtuyboopuifeyQQfeemyibdlfee;; y.e.s. ;y+B-x+A-w+s; ;y;y; ;;print;;
>
> _______________________________________________
> Perl-Unix-Users mailing list
> [EMAIL PROTECTED]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> _______________________________________________
> Perl-Unix-Users mailing list
> [EMAIL PROTECTED]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
_______________________________________________
Perl-Unix-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________
Perl-Unix-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to