full-disclosure - Possibly a stupid question RPC over HTTP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

From: farrenkm at ohsu.edu (Matthew Farrenkopf)
Subject: Possibly a stupid question RPC over HTTP

"Daniel H. Renner" <dan@...angelescomputerhelp.com> 10/13/2004 8:37:12
AM:
> Daniel,
>
> Could you please point out where you read this data?  I would like
to
> see this one...

Ye god, it's true.  And it's recommended by Microsoft as well.  One
example:

http://www.microsoft.com/downloads/details.aspx?FamilyID=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en

This is the Exchange Server 2003 deployment guide.  Self-extracting
ZIP.  Contains the guide, nothing else.

Page 154:

- - - - - 8< - - - - -
Configuring RPC over HTTP for Outlook 2003

When you deploy RPC over HTTP in your corporate environment, you have
two deployment options that are based on where you locate your RPC Proxy
server: 

* Option 1 (recommended)   Deploy an advanced firewall server such as
Internet Security and Acceleration (ISA) Server in the perimeter
network, and position your RPC Proxy server within the corporate
network.

Note   
When you use ISA Server as your advanced firewall server, you have
several deployment options. For information about how to install ISA
Server as an advanced firewall server, see the guide Using Microsoft
Exchange 2000 Front-End Servers
(http://go.microsoft.com/fwlink/?linkid=14575).

* Option 2   Position the Exchange 2003 front-end server acting as an
RPC Proxy server in the perimeter network.
- - - - - 8< - - - - -

Matt