migrate test site to bap main site

Author: dbrumley

404.md

@@ -0,0 +1,12 @@
+---
+layout: center
+permalink: /404.html
+---
+
+# 404
+
+Sorry, we can't seem to find this page.
+
+<div class="mt3">
+  <a href="{{ site.baseurl }}/" class="button button-blue button-big">Home</a>
+</div>

CNAME

@@ -0,0 +1 @@
+dbrumley.github.io

Gemfile

@@ -0,0 +1,2 @@
+source 'https://rubygems.org'
+gem 'github-pages'

_config.yml

@@ -0,0 +1,32 @@
+# Site settings
+title:       The BAP Blog
+# email:       dbrumley@cmu.edu
+author:      David Brumley
+description: "The Binary Analysis Platform Blog"
+baseurl:     ""
+url:         "http://binaryanalysisplatform.github.io"
+
+# Google analytics
+google_analytics:
+
+# Optional features
+animated:           false
+show_related_posts: false
+show_post_footers:  false
+
+# Social icons
+show_social_icons: false
+github_username:
+twitter_username:
+google_plus_id:
+linkedin_username:
+bitcoin_url:
+paypal_url:
+flattr_button:
+
+# Build settings
+markdown:     redcarpet #kramdown
+permalink:    pretty
+paginate:     3
+sass:
+  compressed: true

_drafts/bap-ocaml-tips.md

@@ -0,0 +1,50 @@
+---
+layout: post
+title: BAP Conventions
+---
+
+In this blog post we will give several tips for using BAP on your system.
+
+
+
+# Use baptop
+
+BAP comes with a program called `baptop`, which is an excellent way to
+explore BAP modules.  `baptop` is a
+[`utop`](https://opam.ocaml.org/blog/about-utop/) interface that loads
+the BAP.  `utop` provides a bunch of useful directives, that can help
+you to explore BAP library interactively.  You can find the type of
+any type, module or expression or in `baptop` by using the `#typeof`
+directive followed by the name of the expression in quotes. For
+example, to find the type of `Image.t`, in `baptop` type:
+
+{% highlight ocaml  %}
+(* using a fully-qualified name.  *)
+utop # open Bap.Std;;
+utop # #typeof "image";;
+type Bap.Std.image = Bap.Std.Image.t
+{% endhighlight %}
+
+
+# Module hierarchy management
+
+We have spent quite a bit of time thinking about the BAP module
+hierarchy.  Inside BAP, all types and definitions are belong to a
+`Bap.Std` module hierarchy.  The structure mimics OCaml `Core` library
+quite closely.
+
+Underneath the hood we use somewhat mangled names for actual files
+that are not as clean as the compiled BAP hierarchy. The mangling is
+to overcome some problems with linking and `ocamlfind` that posed a
+challenge to preserving hierarchy purity. As a result, often the name
+of a module (e.g.,
+[`Elf`](https://github.com/BinaryAnalysisPlatform/bap/blob/master/lib/bap_elf/bap_elf.ml))
+does not correspond to a single file of the same name (e.g., there is
+no elf.ml). A BAP developer will have to work their way through the
+file redirection space, but no BAP user should have to.
+
+
+# Setting up your editor
+
+
+

_drafts/why-ocaml.md

@@ -0,0 +1,67 @@
+---
+layout: post
+title: Why ocaml?
+permalink: why_ocaml
+---
+
+BAP is written in OCaml, and I often get asked why. Often the person
+asking has good reasons to prefer another language.  For example,
+Python has more libraries and is quicker to prototype, C is faster,
+and so on.
+
+We do not take this question lightly. BAP has undergone several
+significant rewrites, and for the last three iterations we have chosen
+OCaml.  To understand why, first a little history
+
+## Compilers at CMU
+
+In the mid 2000's I (David Brumley) was a TA for the CMU undergraduate
+compiler course (course number: 15-411). Peter Lee was the instructor.
+(Peter is a former CMU Computer Science Departmet Head, now a Vice
+President at Microsoft, and one of the co-inventors of Proof Carrying
+Code.)  We use the excellent Appel book for compilers, which comes in
+three forms: one for C, one for Java, and one for SML.
+
+At the beginning of semester Peter told all the students that in his
+experience, final grades historically roughly corresponded to the
+language chosen. He also emphasized it didn't matter what language you
+were familiar with now: he had seen many people who had never used ML
+before write the course compiler in SML, and do quite well.
+
+At the end of the semester, Peter's observations seemed quite
+true. Students who programmed in C received a C or lower (often
+fighting with hard-to-debug memory management issues that lead to
+crashing compilers), students in Java received a B (lots of template
+code, unexpected NULL exceptions), and students who wrote in ML got
+As.  I do not remember whether this was true in every case, but it was
+certainly a strong enough sign that I remember it.
+
+## OCaml for Binary Analysis
+
+As a graduate student, I worked with Dawn Song and created Vine, the
+static analysis part of [BitBlaze](http://bitblaze.eecs.berkeley.edu).
+That architecture underwent 3 main revisions. The first was in C, then
+C++, and then OCaml. Just like in compilers, I found C memory safety
+was hard to get right, my C++ relied on a huge amount of template code
+(we tried using the visitor design pattern as specified in the Appel
+compiler book), while OCaml seemed to be a sweet spot.
+
+### Win: Static Type Safety
+
+Others have spoken at length at the benefit of type safety.
+
+
+Type safety is a big deal, not just for correctness but also because
+it makes programs easier to debug.  
+
+### Win: Pattern Matching
+Beyond the well-discussed benefits of type safety covered elsewhere
+(Hello [Jane Street](http://janestreet.com)), the ability to
+**pattern match** ended up being a huge advantage.
+
+Compilers, and most binary analysis platforms, desugar assembly
+statements into an intermediate representation (IR).  The majority of
+code analysis is a pattern match on IR statements. For example, in
+def-use analysis you first match on assignment statements, and then
+set anything on the left-hand side as a definition and on the
+right-hand side as a use.  Pattern matching rules.

_includes/footer.html

@@ -0,0 +1,23 @@
+<footer class="footer">
+  <div class="p2 wrap">
+    <div class="measure mt1 center">
+      <small>
+        BAP has been funded in part by grants from
+        the NSF and DARPA, as well as internal funds.
+      </small>
+    </div>
+  </div>
+</footer>
+
+<!-- {% if site.google_analytics %} -->
+<!-- <script> -->
+<!-- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ -->
+<!-- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), -->
+<!-- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) -->
+<!-- })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); -->
+
+<!-- ga('create', '{{ site.google_analytics }}', 'auto'); -->
+<!-- ga('send', 'pageview'); -->
+
+<!-- </script> -->
+<!-- {% endif %} -->

_includes/head.html

@@ -0,0 +1,29 @@
+<head>
+    <meta charset="utf-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <title>{% if page.title %}{{ page.title }} &#8211; {% endif %}{{ site.title }}</title>
+    <meta name="viewport" content="width=device-width, initial-scale=1">
+    <meta name="description" content="{% if page.summary %}{{ page.summary }}{% else %}{{ site.description }}{% endif %}">
+    <meta name="author" content="{{ site.author }}">
+    {% if page.categories %}<meta name="keywords" content="{{ page.categories | join: ', ' }}">{% endif %}
+    <link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.baseurl | prepend: site.url }}">
+
+    <!-- Custom CSS -->
+    <link rel="stylesheet" href="{{ "/css/pixyll.css" | prepend: site.baseurl }}" type="text/css">
+
+    <!-- Fonts -->
+    <link href='//fonts.googleapis.com/css?family=Merriweather:900,900italic,300,300italic' rel='stylesheet' type='text/css'>
+    <link href='//fonts.googleapis.com/css?family=Lato:900,300' rel='stylesheet' type='text/css'>
+    {% if site.show_social_icons %}
+      <link href="//maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css" rel="stylesheet">
+    {% endif %}
+
+    <!-- Open Graph -->
+    <!-- From: https://github.com/mmistakes/hpstr-jekyll-theme/blob/master/_includes/head.html -->
+    <meta property="og:locale" content="en_US">
+    <meta property="og:type" content="article">
+    <meta property="og:title" content="{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}">
+    <meta property="og:description" content="{% if page.description %}{{ page.description }}{% else %}{{ site.description }}{% endif %}">
+    <meta property="og:url" content="{{ site.url }}{{ page.url }}">
+    <meta property="og:site_name" content="{{ site.title }}">
+</head>

_includes/header.html

@@ -0,0 +1,14 @@
+<header class="site-header px2 px-responsive">
+  <div class="mt2 wrap">
+    <div class="measure">
+      <a href="{{ site.baseurl }}/" class="site-title">{{ site.title }}</a>
+      <nav class="site-nav right">
+        {% include navigation.html %}
+      </nav>
+      <div class="clearfix"></div>
+      {% if site.show_social_icons %}
+        {% include social_links.html %}
+      {% endif %}
+    </div>
+  </div>
+</header>

_includes/navigation.html

@@ -0,0 +1 @@
+<a href="{{ site.baseurl}}/archive/">Archive</a> <a href="{{ site.baseurl }}/about/">About</a>