Comments for Liudvikas Bukys http://L.Bukys.org software development, security, opinion Sun, 12 Jun 2011 15:58:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Long form birth certificate: Turn off image enhancement when you’re trying to make a point by Arthur "Two Sheds" Jackson http://L.Bukys.org/2011/04/27/birth-certificate-long-form/#comment-207006 Arthur "Two Sheds" Jackson Sun, 12 Jun 2011 15:58:45 +0000 http://L.Bukys.org/?p=1315#comment-207006 Great question; Version 5.0.3 of "Preview" which comes with "Mac OS 10.6.7" and does directly scan to PDF. Using anything else to modify the PDF file results in changing the content will change the creator, date/time stamp, etc. Therefore, one possibility is the "Scan Optimization" was done during the scanning process. My Epson Scan software does not have that capability and it would be very helpful if someone can prove it's possible with Preview and another scanner. It's also important to realize the basic PDF header info (aka Metadata) does not keep track of combined PDF sources and editing (i.e. an audit trail). In other words, if you combine several sources/pages into a single PDF file, you will not see a string of sources such as Preview, Acrobat, Illustrator, Photoshop, etc. unless you look into the Advanced Metadata which can also be misleading. Another possibility is someone hacked the header info (date, etc.) which is easy to do with a text editor. That would be very difficult to prove, but if possible, it could be a smoking gun. Perhaps another plausible explanation is a Mac OS "Automator" workflow was used? Great question; Version 5.0.3 of “Preview” which comes with “Mac OS 10.6.7″ and does directly scan to PDF.

Using anything else to modify the PDF file results in changing the content will change the creator, date/time stamp, etc.

Therefore, one possibility is the “Scan Optimization” was done during the scanning process. My Epson Scan software does not have that capability and it would be very helpful if someone can prove it’s possible with Preview and another scanner.

It’s also important to realize the basic PDF header info (aka Metadata) does not keep track of combined PDF sources and editing (i.e. an audit trail). In other words, if you combine several sources/pages into a single PDF file, you will not see a string of sources such as Preview, Acrobat, Illustrator, Photoshop, etc. unless you look into the Advanced Metadata which can also be misleading.

Another possibility is someone hacked the header info (date, etc.) which is easy to do with a text editor. That would be very difficult to prove, but if possible, it could be a smoking gun.

Perhaps another plausible explanation is a Mac OS “Automator” workflow was used?

]]> Comment on Long form birth certificate: Turn off image enhancement when you’re trying to make a point by David W http://L.Bukys.org/2011/04/27/birth-certificate-long-form/#comment-206970 David W Thu, 28 Apr 2011 16:42:10 +0000 http://L.Bukys.org/?p=1315#comment-206970 ABBY FineReader OCR will do this. ABBY FineReader OCR will do this.

]]> Comment on Long form birth certificate: Turn off image enhancement when you’re trying to make a point by Liudvikas Bukys http://L.Bukys.org/2011/04/27/birth-certificate-long-form/#comment-206968 Liudvikas Bukys Wed, 27 Apr 2011 20:42:16 +0000 http://L.Bukys.org/?p=1315#comment-206968 The most plausible suggestion I've heard so far is that this is how Adobe Acrobat's "Optimize Scanned PDF" command works. That's a testable hypothesis. However, would that produce a file with metadata saying "PDF Producer: Mac OS X 10.6.7 Quartz PDFContext" and "PDF Version 1.3 (Acrobat 4.x)" [those suggests Mac print drivers, not Adobe Acrobat]. The most plausible suggestion I’ve heard so far is that this is how Adobe Acrobat’s “Optimize Scanned PDF” command works. That’s a testable hypothesis. However, would that produce a file with metadata saying “PDF Producer: Mac OS X 10.6.7 Quartz PDFContext” and “PDF Version 1.3 (Acrobat 4.x)” [those suggests Mac print drivers, not Adobe Acrobat].

]]> Comment on Long form birth certificate: Turn off image enhancement when you’re trying to make a point by Liudvikas Bukys http://L.Bukys.org/2011/04/27/birth-certificate-long-form/#comment-206967 Liudvikas Bukys Wed, 27 Apr 2011 18:56:13 +0000 http://L.Bukys.org/?p=1315#comment-206967 I really would like to know what scanning/editing suite might result in this kind of contrast enhancement placed in multiple layers. It would also would be interesting to examine the resolutions of all the layers. Comments welcome! I really would like to know what scanning/editing suite might result in this kind of contrast enhancement placed in multiple layers. It would also would be interesting to examine the resolutions of all the layers. Comments welcome!

]]> Comment on APNIC triggers final IPv4 address block distributions by Liudvikas Bukys http://L.Bukys.org/2011/01/31/apnic-triggers-final-ipv4-address-block-distributions/#comment-206903 Liudvikas Bukys Thu, 03 Feb 2011 21:47:21 +0000 http://L.Bukys.org/?p=1277#comment-206903 And Comcast seems to be the first retail ISP to offer IPv4/IPv6 to end users (allocating an IPv6 /64 to each user) http://blog.comcast.com/2011/01/comcast-activates-first-users-with-ipv6-native-dual-stack-over-docsis.html And Comcast seems to be the first retail ISP to offer IPv4/IPv6 to end users (allocating an IPv6 /64 to each user) http://blog.comcast.com/2011/01/comcast-activates-first-users-with-ipv6-native-dual-stack-over-docsis.html

]]> Comment on Survivability of RHEL3 circa Nov 2003 by Dana Epp's ramblings at the Sanctuary http://L.Bukys.org/2004/09/22/survivability-of-rhel3-circa-nov-2003/#comment-49 Dana Epp's ramblings at the Sanctuary Thu, 01 Jan 1970 00:00:00 +0000 http://L.Bukys.org/?p=1225#comment-49 <strong>Survivability of RHEL3</strong> Liudvikas had an interesting post pointing to an entry from a RedHat blog in which Mark Cox points out some compelling evidence in which... "... a full install of a Red Hat Enterprise Linux 3 box that was connected to the internet in November 2003 even... Survivability of RHEL3

Liudvikas had an interesting post pointing to an entry from a RedHat blog in which Mark Cox points out some compelling evidence in which… “… a full install of a Red Hat Enterprise Linux 3 box that was connected to the internet in November 2003 even…

]]> Comment on Survivability of RHEL3 circa Nov 2003 by Dana Epp's ramblings at the Sanctuary http://L.Bukys.org/2004/09/22/survivability-of-rhel3-circa-nov-2003/#comment-48 Dana Epp's ramblings at the Sanctuary Thu, 01 Jan 1970 00:00:00 +0000 http://L.Bukys.org/?p=1225#comment-48 <strong>Survivability of RHEL3</strong> Liudvikas had an interesting post pointing to an entry from a RedHat blog in which Mark Cox points out some compelling evidence in which... "... a full install of a Red Hat Enterprise Linux 3 box that was connected to the internet in November 2003 even... Survivability of RHEL3

Liudvikas had an interesting post pointing to an entry from a RedHat blog in which Mark Cox points out some compelling evidence in which… “… a full install of a Red Hat Enterprise Linux 3 box that was connected to the internet in November 2003 even…

]]> Comment on Survivability of RHEL3 circa Nov 2003 by Chris Walsh http://L.Bukys.org/2004/09/22/survivability-of-rhel3-circa-nov-2003/#comment-47 Chris Walsh Thu, 01 Jan 1970 00:00:00 +0000 http://L.Bukys.org/?p=1225#comment-47 All this says is that RHEL doesn't have an exploitable sshd, and that (at long last) RH doesn't start every service under the sun when you do a full install. It would be interesting to know the survivability of a RH box (excluding sshd) prior to November. I'd offer that it would be measured in weeks. The analogous figure for OpenBSD, by comparison, would be between 6 and 7 YEARS. I do not see how rising to a mediocre standard of reliability after years of opportunity to do so makes an OS praiseworthy. All this says is that RHEL doesn’t have an exploitable sshd, and that (at long last) RH doesn’t start every service under the sun when you do a full install.

It would be interesting to know the survivability of a RH box (excluding sshd) prior to November. I’d offer that it would be measured in weeks. The analogous figure for OpenBSD, by comparison, would be between 6 and 7 YEARS. I do not see how rising to a mediocre standard of reliability after years of opportunity to do so makes an OS praiseworthy.

]]> Comment on Survivability of RHEL3 circa Nov 2003 by Chris Walsh http://L.Bukys.org/2004/09/22/survivability-of-rhel3-circa-nov-2003/#comment-46 Chris Walsh Thu, 01 Jan 1970 00:00:00 +0000 http://L.Bukys.org/?p=1225#comment-46 All this says is that RHEL doesn't have an exploitable sshd, and that (at long last) RH doesn't start every service under the sun when you do a full install. It would be interesting to know the survivability of a RH box (excluding sshd) prior to November. I'd offer that it would be measured in weeks. The analogous figure for OpenBSD, by comparison, would be between 6 and 7 YEARS. I do not see how rising to a mediocre standard of reliability after years of opportunity to do so makes an OS praiseworthy. All this says is that RHEL doesn’t have an exploitable sshd, and that (at long last) RH doesn’t start every service under the sun when you do a full install.

It would be interesting to know the survivability of a RH box (excluding sshd) prior to November. I’d offer that it would be measured in weeks. The analogous figure for OpenBSD, by comparison, would be between 6 and 7 YEARS. I do not see how rising to a mediocre standard of reliability after years of opportunity to do so makes an OS praiseworthy.

]]> Comment on GMail implements “plus addresses” by Yakov Shafranovich http://L.Bukys.org/2004/06/14/gmail-implements-plus-addresses/#comment-45 Yakov Shafranovich Thu, 01 Jan 1970 00:00:00 +0000 http://L.Bukys.org/?p=1210#comment-45 Could be because they are using sendmail and just simply have the feature on for some reason. Could be because they are using sendmail and just simply have the feature on for some reason.

]]>