The original motivation for this was a mistake I made with my home Samba server: I commented out a section header without commenting out its settings. They therefore overrode the settings of the previous section, and caused all sorts of bizarre behaviour until I diagnosed the problem with {cs testparm}. If I’d had SMB Mode then, one touch of the TAB key would have shown me the problem.

Features

Currently smb-mode can do the following:

Auto-indent smb.conf (using TAB, “=” or “]”) and auto-pad the “=” sign.

Perform editing operations on sections (e.g. kill-section, comment-section, etc. – do a C-h m for full details)

Use outline-minor-mode appropriately to get an overview of the file.

Look up a parameter in the {cs smb.conf} manual page.

Perform parameter completion.

Toggle a yes/no parameter.

Set certain yes/no parameters explicitly (like read only) whether they exist in the current section or not.

Run the buffer through {cs testparm}.

Colour things nicely using font-lock-mode (thanks to Johnny Weare)

A list of parameters for completion is obtained from the manual page. Thus, on the first completion attempt, you will wait several seconds until the manpage is ready. You can avoid this by creating a “clean” version of the manual in a text file and setting the {cs smb-manual-file} variable; see {a href=#config Configure} below. In fact, if you are not running Emacs on a Unix system on which Samba is installed, you must do this or completion and manual lookup won’t work.

By default, SMB Mode makes the following assumptions about the format of smb.conf :

[section headers] jam left (not configurable)

options indent 3 spaces (or whatever you set {cs smb-indent} to)

comments start with ; or # and indent the same as the previous line (not configurable)

the “=” in settings always has at least one space on either side of it (set smb-pad-equal to nil to disable)

Download and Install

Download the file below, and save it somewhere in your load-path , as described below.

Download

If you have administrator privileges on your machine, or at least have access to the location where Emacs is installed, save the file in Emacs’ site-lisp directory.

Configure

Place the following lines in your .emacs :

(autoload ‘smb-mode “smb-mode” “SMB Major Mode” t)
(setq auto-mode-alist
(cons ‘(“smb\\.conf$” . smb-mode) auto-mode-alist))

This instructs Emacs that whenever a file ending in smb.conf is edited, smb-mode should be used. It also causes smb-mode.el to be automatically loaded when required, assuming that you installed it correctly as above.

Some aspects of SMB Mode’s behaviour is configurable; here are some examples of what you can put in your .emacs :

Change the automatic parameter indent to 5 (default is 3):

(setq smb-indent 5)

Change the string used to comment a line (default is [this should probably be ; or #]:

(setq smb-comment-str “#”)

Stop the automatic padding of = characters:

(setq smb-pad-equal nil)}

Use a text file as the source of the smb.conf manual page, rather than invoking smb.conf :

(setq smb-manual-file “~/smb-manual”)

Automatically enter Outline minor mode with appropriate things defined so that outlines work properly. TAB key hides and unhides sections, as well as indenting. Not recommended until you get used to things without it.

(setq smb-use-outline-mode t)

If in outline mode as above, automatically hide all bodies and just show the headers initially. Again, not recommended until you have more experience.

(setq smb-hide-immediate t)

PLEASE NOTE: Although cddump works, the code has become messy and unmaintainable. I still use it, but do not intend to develop it any further in its present form.

Banner’s primary goals are:

a simple, single-script backup
intended for user data rather than system data – disaster recovery first requires re-install of original operating system
no special tools required for restore, once OS has been recovered (currently cddump just requires that you be able to mount the CDs, but any other tools normally available on OS may be required in future, e.g. gunzip, unzip, tar, etc.); in particular, cddump itself is *not* required, since it is presumed to have been lost in the failure

cddump is not:

useful for backing up system directories or special files (such as /dev – although it can currently create a cpio archive of such files)
useful for very large quantities of data
useful for unattended backups
cddump requires Perl version 5 (probably preinstalled on most Linux machines, with packages available for everything else).

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

Bug reports and constructive comments are welcomed.

To use, go to Buttons in Preferences and assign SBL to one of the application buttons, for example, the Memopad button. Press this button. When the SBL screen appears, assign Memopad to the first button, then any other applications of your choice to the remaining buttons.

Now if the Memopad button is pressed in the normal way, SBL will immediately start Memopad. Other applications can be started by holding the button down; simple as that. I told you it only used a single button. Unassigned slots are ignored and skipped.

SBL’s overriding ecommerce web design principle is speed; for this reason it does not read the application icons, and does not verify the existence of the applications it is launching until actual launch time. If an application turns out not to exist when launch is attempted, SBL returns to configuration mode. It has no built-in help, “About” screen, or menu options. This ensures that it starts and gets out of the way as quickly as possible, and should not crash when applications are no longer available (unlike some launchers we could mention). It also uses only 6K of memory.

FAQ:

Q: There are already other button launchers out there, why did you waste time making a new one?

A: Because they crashed in various circumstances, or because they were difficult to use with one hand, or because they were just too damn slow.

Q: SBL cycles through applications too fast or too slow!

A: The rate is just perfect (for me) using Handspring Visor hardware. Depending on your PalmOS device’s speed and button hardware, your milage may vary. If you complain vociferously enough, I may add a speed selection option.

Single Button Launcher is released under the Gnu General Public License. You must read the file license.txt (supplied in the download file) before using this software.

Version 0.2 is now available, with many of the features most requested by users of 0.1. Several users have reported interesting and unusual things they use Banner for; if you have one, I’d love to hear from you.

Change Log

0.1 2-Sep-2001

FIRST RELEASE

0.2 26-Sep-2001

bugfix: incorrect handling of non-ASCII chars at end of string caused fatal exception;

bugfix: international characters did not display;

completely reorganised GUI and increased message field screen size;

added menus for cut/copy/paste/about;

added repeat/continuous/looping option;

added start delay;

added optional beep after each message loop (since screen is usually not visible to holder)

Building

The font included in the PRC file in this distribution (“Fairfax Station”) is copyright (C) 1997-2001 Nick Curtis http://www.nicksfonts.com, and is used with permission. This font is not licensed under the GPL, and is not included in the source distribution. To build this program yourself, you must find your own font and use the supplied Perl scripts to generate the “bannerfont.rcp” file. If you do this, you must seek the permission of the font copyright owner before distributing your build.

Banner is released under the Gnu General Public License. You must read the file license.txt (supplied in both download files below) before using this software.

Why Is This Useful?

The PalmOS SysRandom() call is a weak pseudo-random number generator. It combines an initial “seed” (often the system clock or some value derived from it is used; this is under application control) with a mathematical algorithm to generate a sequence of numbers that appear to be random. For most purposes this is fine, however in certain cases (such as encryption or password generation) it is not good enough.

For example, suppose you use your Palm to generate passwords, and also suppose that you maintain the physical security of your Palm, that is, it is kept completely separate from the systems it generates passwords for. If you generate passwords of 8 characters with a mix of upper or lower case letters and digits, you get 2.2E14 combinations, equivalent to roughly 47 bits.

HOWEVER, if an attacker knows that you generate your passwords on your Palm, and also knows which application you use to do it, your passwords may be of much poorer quality. If the application uses the SysRandom() function, it likely seeds it first. The seed value is 32 bits, so that immediately reduces your password quality to 32 bits even though it appears to be 47 bits, since the algorithm generating it is based on a 32-bit starting value. With modern desktop processors, a 32-bit quality password could be cracked in a matter of hours. Even worse, if the application derives the seed from the system clock and the attacker knows roughly when the password was generated, then he has a better idea of the seed. Knowing that the password was generated in a given 12 month period further reduces the quality to 24 bits, in a given month to 21 bits, and a week to 19 bits.

So, if you can bypass these weak algorithmic values entirely, your passwords should be of much better quality. If you still do not understand why this hack is useful, then you don’t need it.

Will Existing Applications Be Affected?

If the applications seed SysRandom using something like the system clock, in order to get as good quality randomness as possible, they will work fine, except that they should receive better quality randomness. If they seed it in a particular way they will not get the sequence they expected. An example of this is the game Shisensho. Each game is assigned a “code” which is just the seed for the system generator. Same code = same game. With Entropy Hack loaded, same code = different game.

How Does Entropy Hack Gather Entropy?

Entropy Hack traps user-initiated events such as character entry and pen taps and shovels data associated with each event plus an existing entropy pool through the MD5 secure one-way hash function to generate a new entropy pool. Random numbers are generated similarly – the random pool and a counter is shoveled through MD5 to give random values. Since MD5 is computationally infeasible to reverse, there is no way for an attacker to predict either previous or subsequent values based on current values, without access to the PalmOS device.

The Entropy Hack requires X-Master. It may also work with the original HackMaster, but this has not been tested.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. A copy of the version 2 license can be found in the file “license.txt” in this distribution.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the file license.txt (supplied with this program) for more details.

If Entropy Hack is useful to you or especially if it misbehaves or crashes, please let me know: joat@joat.ca. In the case of a crash, a reproducible test case will be very helpful.

Be sure to read the help menu on the Edit Place screen for tips, since there is some “hidden” functionality for copying times, and for hours that stretch over midnight.

English version by me (open-en.prc)

Deutsche Übersetzung von Jan de Cuveland (open-de.prc)

Tlumaczenie na jezyk polski – Tomasz Zielinski (open-pl.prc)

Open is released under the Gnu General Public License. You must read the file license.txt (supplied in both download files below) before using this software.

There are lots of versions of this software floating around the ‘net. This is an update of the most recent Linux version converting it to command-line options instead of text menus, and incorporating support for later microcontroller models.

Downloads:

GZipped source (see subdirectory “hardware”)
RPM (Redhat 8.0) (see “docs/hardware”)
Source RPM (see “docs/hardware” after installation)

The following devices should be supported:
Device Status
P16C84
P16F84 Tested
P16F83
P16F873
P16F874
P16F628 Tested
P16C73
P16C74
P16F876
P16F877

New PICs that are pin-compatible with these may also work, and explicit support should be easy to add to the table near the top of noppp.c.

To program a PIC with the contents of code.hex, remove (yes, remove) the PIC from the programmer socket, remove power from the programmer, connect the programmer to your parallel port, then run a command like this:

noppp -d pic-type -w code.hex

…and follow the instructions. Make sure you select the correct PIC model, matching the model the code was assembled for. Verify the code like this:

noppp -d pic-type -v code.hex

To completely erase a PIC with flash memory (all the “F” models):

noppp -d pic-type -e

This does not securely erase a PIC, in the sense that the CIA could probably recover the data if they wanted. If that is a problem, you need to completely destroy it with a combination of high temperature and crushing force. This is not supported in software, nor do I necessarily recommend it.

To test your programmer hardware, fetch a voltmeter and do this:

noppp -t

For other options, such as non-default parallel port settings, use this:

noppp -h

A build-and-program in a single line for a 16F84 might look something like this:

gpasm code.asm && noppp -d pic16f84 -w -P code.hex

Using this software while the parallel port driver is loaded by the kernel may cause unexpected operation.

The tools required to write code for PIC microcontrollers (such as assemblers, simulators and information), can be found here.

Not counting prototyping boards, soldering irons and other tools, the NoPPP can easily be built for less than US$20 in parts. Individual PICs can be purchased for between US$2.50 and US$10, depending on model. At the time of writing the 16F628 probably gives you the most bang for your buck, having internal and external clock options, two analog comparators, a USART and three timers for around US$3. To purchase them, the following websites are useful. I am in no way associated with any of them, nor am I attempting to endorse them:

BG Micro
eBay Canada
Digikey Canada

This might seem obvious, but here are the stages:

• The operator enters commands into a unit on the ground.
• The ground unit transmits the commands via some medium to the flight unit which holds the camera.
• The flight unit receives the commands, positions the camera and takes pictures.

s on the ground and parabolic reflectors at the camera, like those on flashlights.

Flight Unit Controller

Our signalling is likely to be digital in form, so the ideal method is to use a Microcontroller. Microcontrollers are basically tiny single-chip computers, with small amounts of program and data memory, capable of interfacing directly to other electronics. I have used Microchip PIC-series microcontrollers in the past for other projects, and have already build a simple programmer for them.

They can easily be interfaced to DTMF chips and IR receivers, as well as standard radio-control servos, so they should allow us to build a camera control system mechanically identical to a radio-controlled one, but without the radio receiver:

One great advantage of microcontrollers is that once the interface to the other hardware is in place and working, functionality can be changed just by changing the software in flash memory.

Ground Unit

This is the easy part. The easiest ground unit to construct would probably use something like a telephone keypad. Easy to interface to other logic to send digital signals in any form. Not as easy to use as a normal RC transmitter, but it would offer more sophisticated command-input possibilities. With a microcontroller at the other end, the sophistication of the commands is limited only by the software.