Due to the insanely late ship date of my Pi, I received the v2 model for being patient. (The v2 has 512MB of onboard memory vice 256MB on the v1.) In the first 30 minutes, I was able to load one SD card with RaspBMC (XBMC optimized for the Pi) and another with Raspbian (The project’s build of Debian Wheezy for the Pi). I didn’t get too much time to poke around with it from there.
Here are some of the uses I have in mind:
- Media center to stream content from the movie/TV collection on my NAS. (using RaspBMC)
- Penetration testing platform using PwnPi, Raspberry Pwn, or rolling my own, starting from a base install of Raspbian.
- A replacement for my always on test/dev server that also acts as the gateway for me to SSH into my home network.
- A front end for my audio components using an IR sender and a web GUI accessible from my phone. (Those GPIO pin outs are too tempting.)
Odds are, the first unit will end up being a blend of many of those options. I’m already queued up for 2 more when I make it down the list again.
Because I spend more time at the prompt than consuming media, I think I’ll start with Raspbian and build up the LAMP stack first.
More to come as time allows. I should probably be studying for my CISSP now…
At work, we have oodles of databases containing untold treasures of information. We also have boatloads of fillable PDF’s for just about every possible task. (It’s government work after all.) As I walk around, I see these poor souls listlessly going back and forth between their database apps and their PDF forms, copying and pasting. I finally decided that surely I could help the disenfranchised masses remove ten or twenty Ctl-C/Ctl-V operations out of every form they fill out. Nobody wants to spend their day making “copypasta”. So, I’m secretly (never tip your hand until successful) undertaking this as a side project. (Because apparently I have something against sleeping.)
So, my initial tests look promising, but I haven’t generated a lick of PHP yet, so don’t get excited. Hopefully this will give you an idea as to what I’m doing.
Here’s the gist of it:
The Swiss Army Knife of PDF tools, pdftk, can generate an FDF file from a PDF form like so:
The generated FDF file had a few odd characters (like ^@ and þÿ) that I had to scrub out to make it useful. That could be my environment, your mileage may vary. (CentOS 5.8, pdftk 1.44, BTW) If you have the same, I used the following 2 commands in vim to scrub them out:
Now I had a raw, blank FDF to work with, but all my fields were out of order and had names like “TextField” or “CheckBox5”, which was further made ugly by the fact that the names repeat for each row of fields nested inside the PDF’s table structure. Icky. My first thought was to enter values for every text field like “textField1″ to “textFieldn”, but when I laid the data back over the form, there was no semblance of order and it was going to be a nightmare. I decided to go back and fill out the original PDF with descriptive names, regenerated my FDF, and cleaned it up like above. Now I had an FDF where I could tell up from down, mostly. The pertinent parts of the FDF look like this:
I still can’t discern the checkboxes, so some trial and error will be necessary there. The basics of it are thus: The value is in the “/V” line and the field type/designator is the “/T” line AFTER it. Text values go inside parentheses. For checkboxes, a lone slash means unchecked. The checked value will depend on your form. The PDF spec calls for “(Yes)” for a checked box. The form I was working with uses “/1″. Trial and error. Good luck on that.
If you change some values in the FDF and want to try generating a filled form, you use the following syntax:
If all goes well, you’ll have a neat new filled PDF.
That’s great, you say, but how does this work with PHP? As I see it, you use the FDF file as a template by inserting placeholders in each of the values. You parse and replace them, then merge with the original PDF to get your filled form. (using shell_exec() or similar) I’ll work that part out and write Part II.
If you work it out first, or already have and really like me, post it in the comments.
With the forthcoming shipment of my long-awaited Raspberry Pi, I am adding a new section under the projects category.
I wish I could have gotten my hands on more than one, because I have had way too much time to dream up uses for them.
More to come…
In the meantime, my buddy already received his and is way better about actually updating his blog at gymnophoria.com.
It all started with a whim. “I wonder if anyone has written a choose your own adventure game in PHP?” That landed me on Cal Henderson’s “choose” game. That, in turn, led me to Club-Ubuntu’s fork. I started playing around with the stock version and found myself making quite a few changes, so I decided to dig in a little deeper and make it an official fork. I added support for Google Adsense and Analytics, ReCaptcha on the user forms, and an admin page to manage some of the new features as well as some of the copy throughout the site.
I started going through my wiki and some old folders on my NAS this week. I have several old projects that may be of use to someone. Over the next few weeks, I’m going to try to post a whole slew of stuff. I’m also working on a few new projects that are nearly ready to be put out into the wild. So, in short, stay tuned.
For over a year now, we have been using a samba shared network printer to generate TIFF files from electronic documents so that they can be imported directly in to iPerms. The TIFF printer is simply a script that takes PostScript input from the client machine’s print driver and converts it to an iPerms compatible TIFF image. This is primarily useful for an Army installation, but may be relevant if your site is using some other form of document archiving system that uses TIFF images. I can say that ours has spit out over 30,000 pages.
How it works:
Users setup the printer on their system using a PS print driver. (On Vista, I usually use the HP Color Laserjet 2500 PS driver) When they print a document to the printer, it generate a PDF, converts the PDF to a TIFF file and removes the interim PDF. The completed file is dropped into a share with 0600 file permissions. I use 0600 because I set the share to only display readable files. Thus, while everyone is printing to the same folder, they only see their files when they open the share. Less chance of PII leakage.
First, the goods: http://jeffgeiger.com/cron/ (Source available for download from that page.)
This little app parses your crontab and generates a gantt chart of the task time line. It uses the twzCronChart class. I basically took their example and modified it to:
- Accept input via an html textarea.
- Parse out the comments and blank lines.
- Show a corresponding list of which cron line corresponds to which “Task”.
I’ll update this post if I make more changes.
Over the past few months, one of my “As time allows” projects has been a movie collection cataloguing script. Basically it reads through your collection of digitally stored movies, catalogues them in mySQL, and gives you a PHP interface to your collection. It’s not fancy, it’s not pretty, and it almost certainly doesn’t adhere to any good coding practices.
I will try to keep this updated as I “improve” the script and pages. Also, if by some twist of fate, you’re a skilled bash scripter with some free time, I’m open to suggestions on how this can be improved.