[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #OKM-429702]: Setting up an LDM distributor

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #OKM-429702]: Setting up an LDM distributor
  • Date: Tue, 30 Apr 2013 17:10:51 -0600
Leo,

It is possible to build a non-standard LDM that doesn't use port 388 (via the 
"--use-port=<n>" option of the configure(1) script). It is not recommended, 
however, because 1) the so-built LDM will not be able to request data from any 
standard LDM-s without modifications to its REQUEST entries; 2) other, standard 
LDM-s will not be able to request data from the non-standard LDM without 
modifications to their REQUEST entries; and 3) to the best of our knowledge, 
the LDM has never been hacked in order to gain access to the host system 
(indeed, I would argue that that is impossible).

We've also noticed that sites that worry about port 388 usually have port 80 
wide open (for HTTP traffic), which is a greater security risk by many orders 
of magnitude.

> Steve,
> 
> I forgot one question.  Is it mandatory to use Port 388 when talking between 
> LDMs?
> 
> Regards,
> 
> //SIGNED//
> Leo R. Rivard, Contractor, AFWA/SEMS
> SEMS II Database Architect
> Northrop Grumman Information Systems
> email: address@hidden
> COMM: 402-232-0271 / DSN: 272-0271
> Alternate Email: address@hidden

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: OKM-429702
Department: Support LDM
Priority: Normal
Status: Closed