On Wed, Feb 08, 2023 at 10:34:46PM +0100, Uwe Brauer wrote:
[...]
> It seems to me that the credential helper system might be helpful for a
> single user szenario.
>
> But PC running Windows and only have one user for all students will
> inevitably run into problems. So that looks a bit over engineered to me.
[...]
Do I understand correctly that the PCs in your department all have a single
user account shared by different people - so that's what you call "single
user"? [*]
If yes, well, I would say that this is the least correct way to run shared
PCs this day and age, but anyway since it's not you who decides on this
stuff, then yes, any credential caching (and I mean it: not only that of Git)
will actively work against the grit here: all such systems imply any
particular account belongs to a physically distinct person and hence any
session created for that account can share certain stuff related to that
person.
If you really use single login for different folks, you has to turn any
credential caching off. If possible, this should be talked about with whoever
administers these PCs so they maybe have such settings made in a centralized
manner - for instance, they could use Windows domain policies to pre-tweak
system-wide Git configuration to turn the GCM off.
[*] I mean, when I hear "single user" I think of a system with 0 or 1 active
login sessions at any given time - like a typical PC running Windows of
its "desktop" flavor. This concept does not mean multiple users share the
same account/credentials - merely just it's impossble to have more than a
single user logged in and active at any given time. To illustrate, on
desktop Windows, logging in remotely over the so-called Remote Desktop
Protocol (RDP) locks the currenly active "console" session - that one
where a user works at the physical I/O devices attached to the machine,
such as the monitor, keyboard and a pointing device (collectively called
"a seat" these days), - and unlocking the console session back would
disconnect the RDP session, enforcing that "single user" policy.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/20230209102439.74yvwymidwj35qkt%40carbon.
