>>>>> Sergio Schvezov <[email protected]> writes:
> On Mon, Oct 7, 2013 at 7:23 PM, Francis Ginther <
> [email protected]> wrote:
>> Updating to the public URLs has been fixed. The "rebuild" link was
>> intentionally left as is.
>>
> Can we revisit the need to obfuscate this IP?
I don't think it's obfuscated, you need access to the VPN to reach it.
But if it's used as part of a url to a job that *is* already published
to jenkins.qa.ubuntu.com, it makes no sense to still point to the
internal IP. It will take time to track all those occurrences in new
runs and fix the old ones at the same time but I think everybody agree
it's the way to go.
> As it is, it's cached everywhere on the web[1] just in case
> obfuscating it brings in a sense of security.
I don't think anyone feels it's secured by obscurity, it's as secured as
the VPN access.
Vincent
--
Mailing list: https://launchpad.net/~canonical-ci-engineering
Post to : [email protected]
Unsubscribe : https://launchpad.net/~canonical-ci-engineering
More help : https://help.launchpad.net/ListHelp
