Unmark this port from being forbidden; the reason by its time was that
the port had been updated to 1.2.27 and ssl-1.48 which simply did not
Now they do exist. Since it builds, installs and runs correctly with
no further changes, and all the other apache-1.2.27-based ports are
back alive again, there's no reason to keep this one forbidden.
Don't be alarmed that the MD5 sum changes: the previous one in
distinfo was actually the checksum from apache_1.3.26+ssl_1.48.tar.gz,
since the last update to that file only changed the name but not the
MD5 sum. Alas, i could not find any authoritative MD5 on
http://www.apache-ssl.org/ to verify against.