Ok guys I see, point taken. :) and you are absolutely right!
I was blinded by my enthusiasm, I didn't count with the non-technical
part at all.
On 12/02/2014, Joe Zeff wrote:
> On 02/12/2014 09:09 AM, Bruno Wolff III wrote:
>> On Wed, Feb 12, 2014 at 11:10:19 +0100,
>>Robert Dady wrote:
>>>
On 02/12/2014 09:09 AM, Bruno Wolff III wrote:
On Wed, Feb 12, 2014 at 11:10:19 +0100,
Robert Dady wrote:
The thing is that circumvention is also possible by disabling direct
proxy
script download and set direct internet access, in that case there is no
need set up service-subdomain multiple
On Wed, Feb 12, 2014 at 11:09:13 -0600,
Bruno Wolff III wrote:
On Wed, Feb 12, 2014 at 11:10:19 +0100,
Robert Dady wrote:
The thing is that circumvention is also possible by disabling direct proxy
script download and set direct internet access, in that case there is no
need set up service-s
On Wed, Feb 12, 2014 at 11:10:19 +0100,
Robert Dady wrote:
The thing is that circumvention is also possible by disabling direct proxy
script download and set direct internet access, in that case there is no
need set up service-subdomain multiplexing.
Doing this might get you fired. is it rea
The thing is that circumvention is also possible by disabling direct proxy
script download and set direct internet access, in that case there is no
need set up service-subdomain multiplexing.
It could also be possible to set httpd:80 and everything else on 443 where
some php script switches which
On 02/12/2014 12:26 AM, Robert Dady wrote:
Could this work? What else do I need to make this work?
This is actually a brainstorming, but who knows maybe it results
something useful.
To be honest, this sounds like you're trying to violate (or at least
circumvent) your company's security policy
