Re: socket path length

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 24, 2019 at 06:10:03AM +0200, Damian Ivanov wrote:
> >it becomes part of the ABI, and so it can't easily be changed without
> >breaking older user space applications.
> Thanks! Those keywords are enough to be kinda sure this is a non-go
> for a while...
> 
Right, Usually the workaround is to convert to using anonymous sockets, storing
correlary information to find the socket later using non-fs based methods.

Neil

> On Tue, Dec 24, 2019 at 12:39 AM Neil Horman <nhorman@xxxxxxxxxx> wrote:
> >
> > On Mon, Dec 23, 2019 at 10:48:16PM +0200, Damian Ivanov wrote:
> > > Hello everyone and Happy holidays!
> > >
> > > Some applications (like gnome-boxes) rely on socket path
> > > https://gitlab.gnome.org/GNOME/gnome-boxes/issues/267
> > >
> > > A lot of flatpaks as well (filled report here
> > > https://github.com/flatpak/flatpak/issues/3336 )
> > >
> > > If an organizations username structure is
> > > firstname.lastname@xxxxxxxxxxxxxxxx for example my username (more than
> > > one first name, not to mentioned that in some regions middle-name's
> > > are used as well) would be 42 characters which exceeds the limit (17)
> > > mentioned in the gnome BR.
> > >
> > > I could not find any information if having the socket length limited
> > > is still something that is required nowadays as it seems this is
> > > mostly for compatibility reasons?
> > >
> > > Do you think that this us something that could/should/would be changed
> > > nowadays as a config option?
> > >
> > Its part of the unix protocol address specification (see man 7 unix).  Its hard
> > coded, and while the Single Unix Specification leaves it undefined, once
> > selected, it becomes part of the ABI, and so it can't easily be changed without
> > breaking older user space applications.
> >
> > Neil
> >
> > > Thanks in advance!
> > > Best Regards,
> > > Damian
> > > _______________________________________________
> > > kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
> > > To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
> >
> 
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux