[Spread-users] daemon crash on illegal private name
jschultz at spreadconcepts.com
Fri Oct 24 15:05:51 EDT 2003
The problem is the name you are giving to your Spread daemon is too
long. Spread group names are fixed size strings (usually 32 bytes long).
I'm not sure why that particular name is having a problem, as it should
fit within the predefined limit. The daemon should have a check on
itself when it starts that it can at least generate the user name
##spreadname. We'll check and make sure that it does.
Jeremy Hylton wrote:
> I was just testing a spread configuration where each host has a relatively
> long hostname -- storage1.zm.zope.com is an example. I started two spread
> daemons in the same segment and everything looked fine. When I connected
> with spuser, both daemons exited with the error message: "Illegal private
> name #user#storage1.zm.zope.comA" where A was some random highbit character.
> Details: spread 3.17.1, Red Hat Linux 9.
> Buffer overflow? I used just "storage1" for the name and it worked fine. I
> assume the long name exceeded some internal buffer. Could a user
> accidentally crash a running system by connecting with a long name?
> Spread-users mailing list
> Spread-users at lists.spread.org
More information about the Spread-users