On 17.03.20 09:33, Dietmar Maurer wrote:
Does anyone have an assessment of the risk we would run? I still don't
understand the security implications of the mapping of higher UIDs.
However this is quickly becoming a major issue for us.
The risk is that it is not supported by us. Thus, we do
> Does anyone have an assessment of the risk we would run? I still don't
> understand the security implications of the mapping of higher UIDs.
> However this is quickly becoming a major issue for us.
The risk is that it is not supported by us. Thus, we do not
test that and I do not know what
Dear all,
On 13.03.20 14:13, Frank Thommen wrote:
On 3/12/20 7:58 PM, Frank Thommen wrote:
On 3/12/20 5:57 PM, Dietmar Maurer wrote:
I fear
this might be a container-related issue but I don't understand it and I
don't know if there is a solution or a workaround.
Any help or hint is highly
On 3/12/20 7:58 PM, Frank Thommen wrote:
On 3/12/20 5:57 PM, Dietmar Maurer wrote:
I fear
this might be a container-related issue but I don't understand it and I
don't know if there is a solution or a workaround.
Any help or hint is highly appreciated
Yes, we only map 65535 IDs for a single
On 3/12/20 5:57 PM, Dietmar Maurer wrote:
I fear
this might be a container-related issue but I don't understand it and I
don't know if there is a solution or a workaround.
Any help or hint is highly appreciated
Yes, we only map 65535 IDs for a single container. We cannot allow
the full range
On 3/12/20 6:10 PM, Daniel Berteaud wrote:
- Le 12 Mar 20, à 16:35, Frank Thommen f.thom...@dkfz-heidelberg.de a écrit
:
Dear all,
we have a strange issue with a CentOS 7 container running on PVE 6.1-3,
that UIDs > 65535 are invalid. The container is used as a "SSH
jumphost" to
- Le 12 Mar 20, à 16:35, Frank Thommen f.thom...@dkfz-heidelberg.de a écrit
:
> Dear all,
>
> we have a strange issue with a CentOS 7 container running on PVE 6.1-3,
> that UIDs > 65535 are invalid. The container is used as a "SSH
> jumphost" to access a special network: Users log in to
> I fear
> this might be a container-related issue but I don't understand it and I
> don't know if there is a solution or a workaround.
>
> Any help or hint is highly appreciated
Yes, we only map 65535 IDs for a single container. We cannot allow
the full range for security reasons.
