<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title>origami in PDF Blog</title>
    <lastBuildDate>Fri Oct 30 16:24:39 2009</lastBuildDate>
    <link>http://security-labs.org/origami</link>
    <description>Latest news about origami in (malicious) PDF</description>
    <language>en</language>
    <category>origami</category>     
    <atom:link href="http://security-labs.org/origami/rss.xml" rel="self" type="application/rss+xml" />
    <item>
        <title> New version fixing stupid bug</title>
        <pubDate>Oct 30, 2009</pubDate>
        <link>http://security-labs.org/origami/#b2</link>
        <guid>http://security-labs.org/origami/#b2</guid>
        <category>origami</category>
        <description><![CDATA[
        
    We released a new version, 1.0.0-beta1b fixing a bug in some
    samples due to internal changes. Sorry for the mess.
  
        ]]></description>
    </item>
    <item>
        <title> A new version while at HITB</title>
        <pubDate>Oct 6, 2009</pubDate>
        <link>http://security-labs.org/origami/#b2</link>
        <guid>http://security-labs.org/origami/#b2</guid>
        <category>origami</category>
        <description><![CDATA[
        
This <a href="files/origami-1.0.0-beta1.tar.gz">version
1.0.0-beta1</a> while at <a href="http://conference.hackinthebox.org/">HITB</a> comes up with the ability to forge documents with more
graphical contents (such as shapes, colors, gradients...).  However,
graphical contents modifications from existing documents are not
supported. Some templates have been added to quickly create forms
widgets.  Linearized documents might cause issues during recompilation
of existing documents, so a new feature has been added to delinearize
a document. A new flag is also present to (syntactically) obfuscate a
PDF upon saving, which might be useful to confuse a later analysis.
This new version fixes various bugs and slightly improves performance.
  
        ]]></description>
    </item>
    <item>
        <title> Is this PDF malicious?</title>
        <pubDate>Jun 26, 2009</pubDate>
        <link>http://security-labs.org/origami/#b2</link>
        <guid>http://security-labs.org/origami/#b2</guid>
        <category>origami</category>
        <description><![CDATA[
        A new article, <a href="http://esec.fr.sogeti.com/blog/index.php?2009/07/06/70-is-this-pdf-malicious">Is this PDF malicious?</a> dealing with the analysis of a suspicious PDF file.
  
        ]]></description>
    </item>
    <item>
        <title>Origami: release 1.0.0-beta0 </title>
        <pubDate>July 6, 2009</pubDate>
        <link>http://security-labs.org/origami/#b2</link>
        <guid>http://security-labs.org/origami/#b2</guid>
        <category>origami</category>
        <description><![CDATA[
        What's new in this release:
    <ul>
<li>sources/scripts/
      <ul>
<li>scan/pdfscan.rb: a scanner for malicious PDF, or get a
	quickview of what is going to happen when handling
	a given PDF.</li>
<li>antivir/pdfclean.rb: a script to remove all
	dynamic features from a PDF file.</li>
<li>metadata: extract metadata from a PDF, that is author,
	creation date, and some other piece of information.</li>
</ul>
</li>
<li>sources/samples/open/: 4 ways to trigger events when a
      PDF is opened (see <a href="origami/index.html#b1">here</a>).
      
      </li><li>Parser: add support for new objects (XRef streams, Object
      streams, PNG stream predictor functions).
    </li></ul>

        ]]></description>
    </item>
    <item>
        <title>(At least) 4 ways to die opening a PDF</title>
        <pubDate>Jun 26, 2009</pubDate>
        <link>http://security-labs.org/origami/#b1</link>
        <guid>http://security-labs.org/origami/#b1</guid>
        <category>origami</category>
        <description><![CDATA[
        Find our last <a href="http://esec.fr.sogeti.com/blog/index.php?2009/06/26/68-at-least-4-ways-to-die-opening-a-pdf">article</a>. It deals with how to trigger an action when a PDF is opened...
  
        ]]></description>
    </item>
</channel>
</rss>
