| dim14a.zip |
Disk
IMage archiver. This DOS program allows you to clone floppy
disks by imaging them. Advanced features allow transfering of
data from variously sized disks, mass cloning, etc. which was perfect
for user groups that needed to mass produce floppies, etc. It
also allows you to create self extracting disk images (also DOS
executables) which when run would prompt you for a blank floppy. Surprisingly, it still works under Windows NT/2000, however, you need to specify a force size parameter: i.e: -fs:1440 in order for it to work. This is no longer supported, so please don't bother with the shareware fee. :) |
| wns210.zip |
White
Noise Storm. (C source code) This was one of my projects for my
cryptography
course at Polytechnic University about ten years ago. It's a very
different cypher system than most. It's in some ways a stream
cypher, and in other ways a block cypher and has been designed for
steganography use. There is documentation as to the theory
of how it works inside the ZIP file, but to give you a good idea of
what you're in for: WNS works in a similar way to frequency hopping or spread spectrum. Since this has to be adapted to computer use, it uses the concepts of variable sized output data windows for each byte of plaintext, encrypting the plaintext, and setting only some of the bits in the output window to the cyphertext - the rest are filled with either random noise (hence the name) or from the LSB's of the source data when used for stego. It attempts to preserve the statistics of the original noise. If for instance it sets a bit that was a 1 to a 0, it will try to set another unused noise bit that is a 0 to a 1. This has not been formally cryptoanalyzed, you're welcome to do so and let me know the results. (A cypher writer should not break his own cyphers.) The first version of this is extinct. It worked on nibbles (4 bit chunks) instead of bits, thus making it easier for an attacker. |
| setvncpasswd.c |
(C Source code.) A small C
program that will let you recover or set VNC passwords by building
registry files. You will need the VNC server/viewer source
code which it requires to compile (via a couple of #include's.)
Just run gcc on this and ignore all warnings. :) Note that the password a VNC server stores in the Windows Registry (or int he .vncpasswd) is not stored securely. It is encrypted with the same key. So if someone has access to an NT/Win2K machine and can run the registry editor, they can copy the encrypted VNC key, and decrypt it - this is certainly a security risk. This program can be used to recover that password or create .REG files as well as .VNC files for the viewer. I'm not sure if this will work with TightVNC or newer vnc_server distributions - they may have fixed this vulnerability. [I wrote this program so that we could use it to push unique VNC passwords for all the desktops in our company, that way the helpdesk guys could take cover a trader's machine when they called and repair whatever was wrong - saving a trip to the floor. By using IPC network logins and the AT service, I was able to push the .REG files that set passwords to all of the NT workstations on the network. It proved useful when we opened a London office and had no actual IT guys there.] |
| MLIST.ZIP |
Mouse List (DOS).
Small mouse controlled program to browse and view through text files. |
| Mac Binary Tools |
Source code to my MBTOOLS
(DOS)programs. These were used to help my friend Nick
Sklavounakis' BBS NEO. It was a Macintosh BBS, but it ran on DOS,
so he needed tools to manipulate MacBinary encoded files. I
seemed to have misplaed the binary versions of these, so here's the
source code instead - this code is hereby released under the terms of
the GNU GPL license. They should compile with Turbo C 3.1, I understand this is available at the Borland museum. :) |
| NYCETERM |
This was a Commodore 128
terminal program I wrote many, many years ago (perhaps 14-15 years
ago.) There were plenty of Commodore 64 terminal programs which
the C128 could run in C64 mode, but this was one of the few that took
advantage of the 80 column CGA text output of the C128 supporting full
ANSI. It used a PC font so it could display ANSI graphics
properly and even included a font editor. Because of the
video controller in the C128, it wasn't possible to do background
colors - though it was able to do underlines instead. (I don't
recall, but I think later versions of this had the 80x50 text mode -
though it flickered a bit.) It was written half in machine code,
half in compiled basic. The machine code was written by hand without an assembler - I used the built in MONITOR (debugger) program of the C128. I think I have a copy of this somewhere in a shoebox on a 5.25" floppy if the bits haven't been demagnetized off the media, but alas, I don't have it in a form I can put online, nor does it seem to be available anywhere online... If you run across it online, let me know. |
| ROT_13.sit |
A ROT13 file translator for the Mac. Just drop a text file on top of it, and it'll produce a copy of it named 13-filename that has been ROT13 encrypted/decrypted. There is a Clipboard translation, but it doesn't always work on newer Mac OS versions. |
| ANSIViewer.sit |
This is an ANSI viewer for the Macintosh. I wouldn't expect this to work properly on a modern Mac. Back in the old BBS days, people would build small animated files called ANSI art - which is quite similar to today's ASCII art (aalib anyone?), but these relied on the IBM PC's graphic font characters to draw lines, etc. This is a viewer for the Macintosh to play those .ANS files. I wrote this as part of the SB7 BBS below. |
| StarBase7 BBS.sit |
Apple Macintosh BBS for old 68k Macs. Likely won't run on modern Macintosh Machines. Extract it with StuffIt Expander to a folder, then run it from that folder. You can also run the Installer application to wipe all the message boards, and start over, etc. A very long time ago (circa 1989-1993) worked on a Macintosh BBS called StarBase7, but was never released. It was built on an Apple Lisa running Mac OS 4 under MacWorks. I wrote it for a guy who was running a BBS on an Apple II with a 5meg profile drive. Though I had a 286 PC at the time and could have written one on the PC, he didn't have one, but he did have a Mac. So I was able to write code on the Lisa that would run on a Mac. Unfortunately, the only programming environment for the Mac I had at the time was Zedcor Corp's ZBasic. It was a hell of an ugly environment, but it was replaced by FutureBASIC which supported functions, procedures, and to a very limited extent data structures... But by this time most of the code was already written, and it was all filled with GOSUBs and GOTOs. So I spent a long time cleaning it up, and even writing tools to automate the conversion from subroutines to functions, and even tried to write a Basic to C converter to get it ported to C. (I guess that would be a perfect example of throwing more good programming effort after bad code?) :) In terms of the BBS itself, it was quite advanced despite these limitations... It didn't support RIP script yet, but it did do ANSI+PC fonts for line graphics very well and even featured a full screen based message editor with full scrolling, word wrap, etc. It even had a form of hypertext scripting, and tags to set color coding, underlining, etc. You could even write a message to everyone, but include paragraphs that would only be visible to either certain users/groups based on an access level/group memberships... It had built in support for fortune cookies, "On this day" files, one line scrolling board messages, even had a built in mini script language which the sysop could use to write doors, games, etc... In contrast, most Macintosh BBS's at that time were primitive text only beasts. This had a very nice UI system. The user could even select the type of UI he/she wanted - there was one that looked somewhat like Searchlight's. Another that would let you see a text menu, another that would just accept two keystrokes - for experts, etc... Back in those days, most people had 2400bps modems, so the less text you displayed, the faster it responded. The idea was to start them off with full GUI menus, then, as they discovered the features of the BBS, they could opt for the faster terse UI. At it's core was a tree/threaded style message structure which very few BBS's had - even in the PC world... By the time I had stopped work on it, the World Wide Web had begun to take off, and BBS's faded... well that, and I got a full time job as a Novell Netware admin, which ate all time, so the project fell by the wayside. I intended to work on it again, but never did. There was simply too much to do, and too little time, and pretty soon, I lost interest in BBS's... I remember that the last things I was working on was trying to getting it to run multiuser, trying to change some of the internal message database structures to use a B-Tree for faster searching and to get rid of some of the message structure limitations... |