fwiw, I added that to the port(and to W3C httpd). It must be matter of
removing one patch( you can probably check the history of the port in
freshports.org). I'm not sure the port is worth it anymore though.
Pedro
> nah because it would limited access for my lan only (3 pcs)... anyway the compilation failed because it couldn't get freewais... oh well
> > But now maybe someone will break into your computer when you use gopher
> > !!!
> >> Man I should have played around before posting here... removed the FORBIDDEN = "Remote exploits" in the Makefile
> >> > I'd like to setup a gopher server on my internal lan just for the heck of it...
> >> > The only port I could find about gopher is /usr/ports/net/gopher
> >> > I get "===> gopher-2.3.1 is forbidden: Remote exploits." when I try to "make" it
> >> > Why is it there if I can't build it?
> > Maybe in case one day somebody fixes it and they don't have to make the
> > whole port over again. Or so that someone can remove the FORBIDDEN line
> > like you did and risk using the software.
> --
> Martin Lefebvre, Unix Administrator, Technologies DigiNex
> ---------------------------------------------------------
> FreeBSD 4.2-RELEASE
> 9:10AM up 11:32, 4 users, load averages: 0.11, 0.07, 0.02
> "If Microsoft was the answer, then it must have been a really
> stupid question"
by