mami's questions

I am trying to set up a shared git repo on my Synology NAS. I have checked many step by step articles but don't get why my regular git user cannot clone the repo from Windows cmd and Visual Studio.

After a long investigation, I have the feeling the root cause is git-receive-pack behaving differently for my git user from the Windows cmd and a putty session.

If I try from cmd:

ssh user@host git-receive-pack /path/to/repo

I only get:

008d0000000000000000000000000000000000000000 capabilities^{}

On the contrary, if I open a putty session to the NAS with the same user and run

git-receive-pack /path/to/repo

it returns more:

008d0000000000000000000000000000000000000000 capabilities^{}report-status delete-refs side-band-64k quiet atomic ofs-delta agent=git/2.26.2 0000

Anyone having an idea what makes this difference?

Windows 10, ssh version in cmd is:

OpenSSH_7.6p1, LibreSSL 2.5.3

openssh is configured for rsa key auth.

As far as I know there is/was a limitation for AFS volume name length so one can practically use 22 characters only (we use read only volumes as well so we need to fit into the 31 char limit with adding ".readonly"). Does anyone know if this limit still applies for recent OpenAFS releases and if yes, what is the reason for this limitation other than historic? I would really like to be able to use longer names. (Already asked on superuser.com but realized it fits better here).