… | |
… | |
341 | |
341 | |
342 | =back |
342 | =back |
343 | |
343 | |
344 | =head1 SECURITY CONSIDERATIONS |
344 | =head1 SECURITY CONSIDERATIONS |
345 | |
345 | |
346 | CV uses Pixbuf to load images. Pixbuf is not considered safe for this |
346 | CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe for |
347 | purpose, though (from the gtk-2.2 release notes): |
347 | this purpose, though (from the gtk-2.2 release notes): |
348 | |
348 | |
349 | "While efforts have been made to make gdk-pixbuf robust against invalid |
349 | "While efforts have been made to make gdk-pixbuf robust against invalid |
350 | images, using gdk-pixbuf to load untrusted data is not recommended, due to |
350 | images, using gdk-pixbuf to load untrusted data is not recommended, due to |
351 | the likelyhood that there are additional problems where an invalid image |
351 | the likelyhood that there are additional problems where an invalid image |
352 | could cause gdk-pixbuf to crash or worse." |
352 | could cause gdk-pixbuf to crash or worse." |
… | |
… | |
354 | =head1 BUGS/TODO |
354 | =head1 BUGS/TODO |
355 | |
355 | |
356 | Lots of functionality is missing. |
356 | Lots of functionality is missing. |
357 | |
357 | |
358 | Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with |
358 | Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with |
359 | names incompatible might utf-8 fail. |
359 | names incompatible with utf-8 might fail. |
360 | |
360 | |
361 | rotate on disk |
361 | rotate on disk |
362 | lots of ui issues |
362 | lots of ui issues |
363 | save(?) |
363 | save(?) |
364 | preferences |
364 | preferences |
365 | shift-cursor in schnauzer |
|
|
366 | |
365 | |
367 | =head1 AUTHOR |
366 | =head1 AUTHOR |
368 | |
367 | |
369 | Marc Lehmann <cv@plan9.de>. |
368 | Marc Lehmann <cv@plan9.de>. |
370 | |
369 | |