• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Regarding the "localhostips" property in deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regarding the "localhostips" property in deployment


  • Subject: Re: Regarding the "localhostips" property in deployment
  • From: Hugi Thordarson via Webobjects-dev <email@hidden>
  • Date: Fri, 30 May 2025 11:51:00 +0000

Maik, Paul, Hi!

Just wanted to acknowledge and thank you for the replies, sorry about not
replying earlier.

You had some good questions and I wanted to have better answers to them before
I replied, by setting up a new environment so I can check what happens in
WOHostUtilities that blocks commmunications without the "localhostips"-thing.
Just haven't gotten around to it yet. Picking this up soon.

Cheers,
- hugi


> On 6 May 2025, at 05:19, Maik Musall via Webobjects-dev
> <email@hidden> wrote:
>
> Hi,
>
> I can see this being set in an older installation here, but in many cases I
> don’t even have an /etc/WebObjects directory, and I don’t recall ever setting
> this property by hand.
>
> We do have complex setups with apache on different hosts than wotaskd, but it
> is sufficient to set the IP addresses of the wotaskd hosts in the apache
> adaptor config file to reach them. However, we do not have applications on
> hosts with no local wotaskd, so maybe that’s the one case where this would be
> necessary?
>
> Maik


> On 6 May 2025, at 02:05, Paul Hoadley via Webobjects-dev
> <email@hidden> wrote:
>
>> On 5 May 2025, at 16:38, Hugi Thordarson via Webobjects-dev
>> <email@hidden> wrote:
>>
>> quick question: When setting up a deployment environment you usually have to
>> set the property er.extensions.WOHostUtilities.localhostips (usually in
>> /etc/WebObjects/Properties) to ensure your applications accept incoming
>> admin requests from wotaskd.
>
> Is this only in the setting where wotaskd is on a different host? Because
> I've never done this, though we only deploy with wotaskd+JavaMonitor on the
> host running the app instances.
>
>> I'm still no security expert, so I'm just checking if anyone sees this as a
>> bad idea/security issue, or if this can be safely kept and merged into
>> Wonder.
>
> I'm no security expert either, but it seems reasonable as a default that you
> can override. What happens in the setting where someone doesn't currently set
> the property, though? That is, what default behaviour will you be changing,
> and how astonishing will this be?

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Regarding the "localhostips" property in deployment (From: Hugi Thordarson via Webobjects-dev <email@hidden>)
 >Re: Regarding the "localhostips" property in deployment (From: Paul Hoadley via Webobjects-dev <email@hidden>)
 >Re: Regarding the "localhostips" property in deployment (From: Maik Musall via Webobjects-dev <email@hidden>)

  • Prev by Date: Do we need ERXApplication.Loader anymore?
  • Previous by thread: Re: Regarding the "localhostips" property in deployment
  • Next by thread: JavaXML.framework and Java 21 (and Eclipse)
  • Index(es):
    • Date
    • Thread