Re: Apache VirtualHost Restriction

From: nicolas cunjamalay <n.cunjamalay_at_gmail.com>
Date: Thu, 30 Apr 2015 21:43:16 +0400

You can use the 2 - factor authentication on the web interface for remote
users,

What do u mean by accessible locally?

Are you authorised to block a range of IPs ?

What are your restrictions about the IPs?

Are building an intranet ?


On Thu, Apr 30, 2015 at 8:47 PM, Yuv Joodhisty <locustv2_at_gmail.com> wrote:

> I know about htaccess and htpasswd. This is a nice idea but its just an
> authentication and this is not the right implementation that i need in my
> current situation. I need to completely restrict the user from accessing it
> if possible.
>
> But thanks anyway. Any other ideas?
>
> On Thu, Apr 30, 2015 at 8:39 PM, Ajay R Ramjatan <ajay.ramjatan_at_gmail.com>
> wrote:
>
>> This would be off-topic but I'll give you a pointer. Use authentication.
>> Google for apache htaccess authentication
>>
>>
>> On Thu, Apr 30, 2015 at 8:18 PM, Yuv Joodhisty <locustv2_at_gmail.com>
>> wrote:
>>
>>> Hello guys,
>>>
>>> Does anyone have any idea how to tackle this problem?
>>> I need a virtual host which should be:
>>>
>>> - accessible locally but not publicly
>>> - may be accessible by some remote users
>>> - those remote users doesn't have a static ip
>>>
>>> Thanks
>>> Yuv
>>>
>>
>>
>
Received on Thu Apr 30 2015 - 17:43:28 PST

This archive was generated by hypermail 2.3.0 : Thu Apr 30 2015 - 17:45:04 PST