Files
ioccc/1995/garry
Cody Boone Ferguson 009e1b7522 Link in SECURITY.html to all web pages
The location of the link is in the About menu under the 'Contacting the
IOCCC' and above 'Thanks for the help'. At first I had it at the very
bottom, under 'IOCCC markdown guidelines', but it seemed better to have
it closer to contacting the IOCCC. This is the same location in the no
JavaScript menu (which, for those who do not know or forget, is not a
requirement except for some screen sizes).

The top level Makefile has a new 'security' rule. Updated make help.

Typo fixes in make help.

SECURITY.html has had a few updates as well: change the wording of entry
code is unsupported (it now says 'ALL CODE IN ALL IOCCC ENTRIES IS
UNSUPPORTED!!') and it now links to the mkiocccentry repo and how to
report a possible security vulnerability in that repo; as that IS
supported - and since there was reference to discussing security
concerns is in SECURITY.html - even though the entries will not receive
security updates - it seemed a good idea to have a link to report such
security issues in the mkiocccentry repo. Perhaps the FAQ needs to be
updated for this too.
2024-07-15 08:55:54 -07:00
..
…
2024-01-18 10:51:10 -08:00
2023-07-06 21:49:38 -07:00
2024-03-11 09:09:21 -07:00

To build:

    make all

To use:

    ./garry <input_file >output_file

Try:

    ./try.sh

Alternate code:

While it may not have been the intention of the author, the judges noted that the C pre-processed version (with the #includes left intact) looked very much like a rat "dropping core". See garry.alt.c and judge for yourself!

Alternate build:

    make alt

Alternate use:

    ./garry.alt <input_file >output_file

Alternate try:

    ./try.alt.sh

Judges' remarks:

The author was kind enough to provide a less obfuscated version of the source called garry.fmt.c.

Author's remarks:

This program is a file filter, designed to do environment-expansion and incorporating the ability to create binary from escaped data in the environment variables.

The calling syntax is pretty simple, just use it with stdio-redirection or inside pipelines, e.g.:

    ./garry <file_to_convert >converted_file

or

    cat all_my_files/* | ./garry | lp

The syntax of the conversion of the input file is as follows: To include the value of an environment variable in the output file, place the name of the variable between $-signs in the input, e.g.:

    My Home-Directory is: $HOME$
    I'm using the path: $PATH$

Unknown Env-variables or malformed expressions are ignored and kept intact.

Additionally, the filter replaces escaped octal values in the environment variables by their binary representation, e.g.:

    $ TEST="\110\145\154\154\157"
    $ export TEST
    $ echo '$TEST$' | ./garry
    Hello