Cody Boone Ferguson
084a311418
Though this will not work as is I have changed the code to scan for
https as well (it exited before). This is so if someone comes up with a
clever command line to make it work it can. A secure connection has to
be established before http commands can be given but now it at least can
connect (though it's been a while since I've played with sockets so
maybe I'm forgetting some detail - one does have to specify the port but
I gave an example in the README.md file for that).
In the README.md I pointed out that one has to specify http:// (or else
https though with the caveat noted above). I also explained how to
specify an alternative port.
I also noted the https issue in the bugs.md file in the INABIAF section
('it's not a bug it's a feature').
As well I changed the try command in the entry README.md file to refer
to a page that does not use https as trying it on the ioccc website
(what it used to) will just return a 301 error.
2.3 KiB
Best use of the www
Anthony Howe
Snert
42 av. Isola Bella
06400 Cannes,
France
achowe@snert.com
To build:
make
To run:
./mynx http://<domain>
You can specify a port by appending to the domain :port. See notes below on
the issue of https.
Try:
./mynx http://www.textfiles.com
Cody Boone Ferguson pointed out that this
will not work for https initially for two reasons. First it scanned for http://.
Cody changed it to scan for both http:// and https:// but the problem is a
secure connection needs to be set up before http commands can be sent. One would
also have to specify a port in the URL. Fortunately or unfortunately many more
websites use https nowadays so this entry will not work as well as it used to.
If one were to try and connect to http://www.ioccc.org with this entry they'll
just get a 301 error. Perhaps someone can come up with a pipeline that will make
this work with the change made. Otherwise just enjoy it for what it was.
Judges' comments
This little mynx will give any Fiery Fox a run for its money. A nice complement to last years winning hibachi. The judges double dare any eager Obfuscationalists to submit the missing pieces to get a functioning LAMP stack.
Author's comments:
I was rather impressed by last year's mini web server. So much so that it inspired me to try my hand at writing the client side complement.
A typical build would be command would be:
cc -omynx mynx.c
While some others like to be a little different:
cc -omynx mynx.c -lnsl -lsocket
I even managed to figure out a basic configure script, given last year's example, which is kinda of useful when you consider how many OSes put all the network functions in a variety of places. So a simpler build command sequence would be:
./configure
make
After which, the rest of the documentation can be read by saying:
./mynx manual.html
Manifest:
mynx.c
makefile pre-built generic Un*x
README.TXT
manual.html
makefile.in makefile template
entities.txt ISO 8859-1 entites
configure.in configure script description
configure pre-built configure script