Hi Johannes, [EMAIL PROTECTED] wrote: > So, my question is, how can I avoid that PC connected from extern start an > update session. > > The differentiation is possible by the IP address - from extern it is a > different range than > being internal connected.
So you could simply limit access to the share where wpkg.js is stored for road warriors. Thus automatically preventing WPKG to execute wpkg.js from that share when not within the local network. If you cannot, don't know how or just don't want to do that you might use a pre-execution script (see WPKG client configuration). Such a script could check (by IP for example) if the machine is within the local network and then either return a non-zero exit status (check failed) or exit status 0 (when the client is actually internal). Any non-zero exit status will prevent WPKG client to continue executing wpkg.js. br, Rainer ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/wpkg-users
