mkoepke

This note explains the common issue of "notapplicable" results when running openSCAP and SCAP-Security-Guide on CentOS.

SCAP seems like it should be easy because it is "just XML". Then you dig into looking for a test and it gets confusing fast. So it is good to have some background.

SCAP (Security Content Automation Protocol) is actually a set of multiple standards and specifications that are used together to enable automatically testing hundreds of nerd settings. Let me emphasize that: SCAP is not a single XML specification -- SCAP is multiple standards and specs. Whenever you give "SCAP Content" to a scanner to check a system configurations you are giving the scanner multiple XML files representing multiple standards.

mkoepke

#! /bin/bash
#
# Script to deploy from Github to WordPress.org Plugin Repository
# A modification of Dean Clatworthy's deploy script as found here: https://github.com/deanc/wordpress-plugin-git-svn
# The difference is that this script lives in the plugin's git repo & doesn't require an existing SVN repo.

#prompt for plugin slug
echo -e "Plugin Slug: \c"
read PLUGINSLUG

mkoepke

<?php
// specify your css-files and their order here
$cssFiles = array(
  'normalize.css', 'style.css', 'print.css', 'colorbox.css'
);
// the file to write the compressed css to
$minFileName = 'minified.css';

// thats all, just call this file in your browser and it will
// build you a minimized css-file. then just link to this single

mkoepke

<?php
/**
 * @file
 * Simple PHP library for interacting with the v3 BITLY API - using OAuth
 * REQUIREMENTS: PHP, Curl, JSON
 * 
 * @author Andrew Pinzler <ap@bitly.com>
 */
 
 

mkoepke

// Single-line comments start with two slashes.
/* Multiline comments start with slash-star,
   and end with star-slash */

// Statements can be terminated by ;
doStuff();

// ... but they don't have to be, as semicolons are automatically inserted
// wherever there's a newline, except in certain cases.

mkoepke

#!/bin/bash
# cd into the directory
cd ~/gitsync/github-wordpress-sync/;
# Make sure we are not already running
if [ -f .sync-running ];then
	if test ! `find ".sync-running" -mmin +10`;then
		# Currently running, but not stuck
		exit 1;
	fi
fi;