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
 
Ruslan R. Laishev  
View profile  
 More options Jul 2 2007, 4:19 am
Newsgroups: comp.os.vms
From: "Ruslan R. Laishev" <zzLais...@zzDeltaTelecom.RU-remove.all-zz-to-reply>
Date: Mon, 02 Jul 2007 12:19:43 +0400
Local: Mon, Jul 2 2007 4:19 am
Subject: Re: VMS security vulnerability (POP server)
Print | View thread | Show original | Report this message | Find messages by this author
Hello!

        Have a look to http://starlet.deltatel.ru/~laishev/work/pop3/

        I wrote this as replacement of the IUpop3 and other POP3 server supplied with
IP-package.

        Intrusion detection, TLS support and so on...

JF Mezei wrote:
> OK, it has been a couple of weeks and haven't heard anything back from HP).

> When a pop client requests access to the VMS POP server (Alpha VMS 8.3,
> TCPIP Services 5.6) and provides incorrect username/password, this event
> is not logged in the audit server. A simple message is sent to OPCOM.
> This message does not contain any clue on the origin of the request.

> So overnight, it becomes possible to run brute force attempts on
> usernames via POP since no intrusion detection/evasion is made, and
> short of many messages in operator.log, there is nothing in AnA/AUDIT
> and no information on the IP address of the client that made those
> attempts.

> (I got such an attack with thousands of attempts).

> The whole intrusion detection scheme needs to apply to ALL services
> which grant access to VMS via user/password combination and all such
> application should comply to whateer calling standards to ensure that
> all attempts with invalid credentials are properly logged, including IP
> address and the username that was attempted.

--
+ WBR, OpenVMS [Sys|Net] HardWorker ............. Skype: SysMan-One  +
Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
+http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

 
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