RE: Help for adding a privacy prompt prior to checkout execution
From: Markus Schaber <m.schaber_at_codesys.com>
Date: Sun, 3 Sep 2017 15:52:23 +0000
From: Bob Zhu [mailto:bzhu_at_fortinet.com]
> We definitely don't wan to do anything client side since that would be a
To be honest, I think your upper management should re-think this detail of their decision.
First, anchoring everything at the "checkout" operation is a bit too specific - what about operations like "export", "update" or "switch" which can also bring in new data which has not been in the local working copy before?
And second, having a high hurdle before a "checkout" will lead to teammates exchanging working copies directly, keeping zip-files of those "on stock" in case they "need it again later", and other attempts to circumvent it.
One possible solution I could think of is that they need to use a different user name for that specific repository - e. G. instead of "foobar", they need to enter "foobar-I-know-it-is-confidental" using the same password as for their normal account.
Another possibility would be to hide the server behind a proxy, and the proxy requires a separate proxy authentication.
But none of them are implemented "out of the box" with stock SVN.
CODESYS® a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received
This is an archived mail posted to the Subversion Dev mailing list.