per
https://mail.google.com/mail/u/0/#inbox/13e852c000fcda37
line 255 on lshosts.c : no mallocing, trying to overwrite over array
security check, but don't look at it too much: find out how to exploit buffer
overflows and try to get escalated access.
probably will require refactoring
replication: contact user for more details, but it is probably a long string,
like a username, if his hostnames are any indication, or a bad formatter.
regression:
* test case with long hostnames or resources
then
refactoring test cases:
* switches before, must be identical to switches after
* output before, must be identical to switches after
* ?
Original issue reported on code.google.com by geo...@marsel.is on 13 May 2013 at 10:50
Original issue reported on code.google.com by
geo...@marsel.ison 13 May 2013 at 10:50