Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.os.vms
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion VMS security vulnerability (POP server)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
John Santos  
View profile  
 More options Jul 2 2007, 1:10 am
Newsgroups: comp.os.vms
From: John Santos <j...@egh.com>
Date: Mon, 02 Jul 2007 05:10:45 GMT
Local: Mon, Jul 2 2007 1:10 am
Subject: Re: VMS security vulnerability (POP server)
Print | View thread | Show original | Report this message | Find messages by this author

Michael Moroney wrote:
> That is a nasty one, since much of what makes VMS resistant to such
> attacks is the ability to sense a breakin attempt and deny access from
> the breakin source even when it gets the password correct.

> Did the attempt seem to target VMS or was it a script kiddie hacking at
> a Windoze box or Unix box (accounts like administrator or root being
> tried)

Works okay in IUPOP3 server <V2.0-4/NETLIB/(DECC) and TCPware V5.7-2.

Still broken in:

"HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.6 - ECO 1
on an HP rx2620  (1.60GHz/3.0MB) running OpenVMS V8.3"

Both IUPOP3 and TCPware POP3 log intrusions for each failed access and
then put you in "INTRUDER" state and initiate break-in evasion after
the appropriate number of failures.  TCPIP (UCX) just logs the failures
to OPCOM.

There are a bunch of logical names that control TCPIP's POP3.  None of
them seem to enable breakin evasion, though.

Plain vanilla POP3 isn't very secure since the usernames and passwords are
transmitted in plain text.  There is an alternate APOP authorization method
that uses shared secrets instead.  I haven't tried setting this up.  It can
also be run over an SSL connection, where everything is encrypted.  I haven't
tried setting this up either.  (All my users are either on the LAN or
coming in over encrypted VPN connections, no WAN access to POP, and they
are all company employees with privileged VMS accounts anyway, so it
doesn't worry me very much.)  Both of these alternate access methods can
be configured by logical names to be used in addition to or in place of
the standard plain-text access on port 110.

If you're letting the outside world get at port 110, then I would either
disable it or firewall it or use one of the alternatives (APOP or SSL)
instead.

--
John Santos
Evans Griffiths & Hart, Inc.
781-861-0670 ext 539


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google