search for: 1016960

This issue has been assigned CVE-2013-4419. https://bugzilla.redhat.com/show_bug.cgi?id=1016960 (Note this bug is private, but will be made public shortly) ---------------------------------------------------------------------- When using the guestfish --remote or guestfish --listen options, guestfish would create a socket in a known location (/tmp/.guestfish-$UID/socket-$PID). The location...

Yes, I did -- it made no difference. Should it? Note that I have since discovered that this is not a problem on Windows -- the exception drops through as expected. pz On 2011-07-21, at 5:45 PM, Garrison Venn wrote: > Sorry Peter, just saw this. > > If you are still having the problem: > > Did you set: llvm::JITExceptionHandling = true; ? > > Garrison > > On Jul

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a

...ive file such as -C</etc/shadow> then it would be left world-readable after the edit. +F</etc/shadow> then it would be left world-readable after the edit. It is sufficient to update libguestfs to any version E<ge> 1.16. @@ -2161,11 +2161,11 @@ L<https://bugzilla.redhat.com/1016960> When using the L<guestfish(1)> I<--remote> or guestfish I<--listen> options, guestfish would create a socket in a known location -(C</tmp/.guestfish-$UID/socket-$PID>). +(F</tmp/.guestfish-$UID/socket-$PID>). The location has to be a known one in order for b...