lynx: disable old protocols

classic Classic list List threaded Threaded
64 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

lynx: disable old protocols

Daniel Dickman
Patch below turns off the following ancient protocols built into lynx:
bibp, finger, gopher, and news.

For some urls, lynx will invoke an external command. Turn off telnet,
rlogin and tn3270 urls by defining them to false(1) as documented in the
lynx manual.

Finally, turn off the file editor which can be accessed with "g.<enter>"
using the --disable-dired switch.

ok to commit?

Index: Makefile.bsd-wrapper
===================================================================
RCS file: /home/cvs/src/gnu/usr.bin/lynx/Makefile.bsd-wrapper,v
retrieving revision 1.24
diff -u -p -u -r1.24 Makefile.bsd-wrapper
--- Makefile.bsd-wrapper 15 Apr 2014 20:55:42 -0000 1.24
+++ Makefile.bsd-wrapper 11 Jul 2014 02:47:31 -0000
@@ -5,7 +5,10 @@ CLEANFILES+= lynx.1
 DPADD= ${LIBSSL} ${LIBCRYPTO}
 
 GNUCFLAGS= CC="${CC}" CFLAGS="${CFLAGS} ${COPTS} ${OPT}" LDFLAGS="${LDFLAGS}"
-CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6 --enable-debug
+CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6 --enable-debug \
+ --disable-bibp-urls --disable-finger --disable-gopher --disable-news \
+ --disable-dired
+
 HTMLDIR= /usr/share/doc/html
 HELPFILES= keystrokes/alt_edit_help.html keystrokes/bookmark_help.html \
  keystrokes/cookie_help.html keystrokes/dired_help.html \
@@ -39,12 +42,18 @@ config: .FORCE
  PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
  ${GNUCFLAGS} \
  INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
+ TELNET=/usr/bin/false \
+ RLOGIN=/usr/bin/false \
+ TN3270=/usr/bin/false \
  sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc --disable-color-style ${CONFIGURE_ARGS}
 
 config.status:
  PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
  ${GNUCFLAGS} \
  INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
+ TELNET=/usr/bin/false \
+ RLOGIN=/usr/bin/false \
+ TN3270=/usr/bin/false \
  sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc --disable-color-style ${CONFIGURE_ARGS} ${CF}
 
 lynx.1: ${.CURDIR}/lynx.man

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Shawn K. Quinn-2
On Thu, 2014-07-10 at 23:05 -0400, Daniel Dickman wrote:
> Patch below turns off the following ancient protocols built into lynx:
> bibp, finger, gopher, and news.
>
> For some urls, lynx will invoke an external command. Turn off telnet,
> rlogin and tn3270 urls by defining them to false(1) as documented in the
> lynx manual.

Gopher and NNTP are actually still being used (the former a bit
sparsely, but there are a few servers here and there). The rest I don't
mind seeing disappear (we don't ship the telnet and rlogin programs
anymore AFAIK, I've never heard of bibp, and we have a finger program as
an alternative to the functionality in lynx).

> Finally, turn off the file editor which can be accessed with "g.<enter>"
> using the --disable-dired switch.

I don't see a good reason to get rid of this. What is the rationale?

--
Shawn K. Quinn <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Daniel Dickman
>> For some urls, lynx will invoke an external command. Turn off telnet,
>> rlogin and tn3270 urls by defining them to false(1) as documented in the
>> lynx manual.
>
> Gopher and NNTP are actually still being used (the former a bit
> sparsely, but there are a few servers here and there). The rest I don't
> mind seeing disappear (we don't ship the telnet and rlogin programs
> anymore AFAIK, I've never heard of bibp, and we have a finger program as
> an alternative to the functionality in lynx).

this support does not need to be in base.

>
>> Finally, turn off the file editor which can be accessed with "g.<enter>"
>> using the --disable-dired switch.
>
> I don't see a good reason to get rid of this. What is the rationale?
>

I want a text browser not a file manager.

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Brian Callahan-3

On 07/10/14 23:17, Daniel Dickman wrote:
>>> For some urls, lynx will invoke an external command. Turn off telnet,
>>> rlogin and tn3270 urls by defining them to false(1) as documented in the
>>> lynx manual.
>> Gopher and NNTP are actually still being used (the former a bit
>> sparsely, but there are a few servers here and there). The rest I don't
>> mind seeing disappear (we don't ship the telnet and rlogin programs
>> anymore AFAIK, I've never heard of bibp, and we have a finger program as
>> an alternative to the functionality in lynx).
> this support does not need to be in base.

I very much use lynx for its gopher support. I would be sad to see it go.

>>> Finally, turn off the file editor which can be accessed with "g.<enter>"
>>> using the --disable-dired switch.
>> I don't see a good reason to get rid of this. What is the rationale?
>>
> I want a text browser not a file manager.
>

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Adam Thompson
In reply to this post by Daniel Dickman
As a user, not a developer...
I still use finger, gopher, and news URLs at least once a year each.  As a user, I disagree with turning support for those schemes off completely.
Finger and news I can use another tool, and I'd concede that no-one really *needs* a news reader in base.  (I still find having a finger client of some sort in base useful at one site, however.)
Gopher, however, is not as dead as everyone assumes.
I believe I can re-enable tn3270 and telnet schemes manually, which is fine.  I still use both of those fairly often.
The other protocols are irrelevant to me.
-Adam

On July 10, 2014 10:05:45 PM CDT, Daniel Dickman <[hidden email]> wrote:

>Patch below turns off the following ancient protocols built into lynx:
>bibp, finger, gopher, and news.
>
>For some urls, lynx will invoke an external command. Turn off telnet,
>rlogin and tn3270 urls by defining them to false(1) as documented in
>the
>lynx manual.
>
>Finally, turn off the file editor which can be accessed with
>"g.<enter>"
>using the --disable-dired switch.
>
>ok to commit?
>
>Index: Makefile.bsd-wrapper
>===================================================================
>RCS file: /home/cvs/src/gnu/usr.bin/lynx/Makefile.bsd-wrapper,v
>retrieving revision 1.24
>diff -u -p -u -r1.24 Makefile.bsd-wrapper
>--- Makefile.bsd-wrapper 15 Apr 2014 20:55:42 -0000 1.24
>+++ Makefile.bsd-wrapper 11 Jul 2014 02:47:31 -0000
>@@ -5,7 +5,10 @@ CLEANFILES+= lynx.1
> DPADD= ${LIBSSL} ${LIBCRYPTO}
>
>GNUCFLAGS= CC="${CC}" CFLAGS="${CFLAGS} ${COPTS} ${OPT}"
>LDFLAGS="${LDFLAGS}"
>-CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6
>--enable-debug
>+CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6
>--enable-debug \
>+ --disable-bibp-urls --disable-finger --disable-gopher --disable-news
>\
>+ --disable-dired
>+
> HTMLDIR= /usr/share/doc/html
>HELPFILES= keystrokes/alt_edit_help.html keystrokes/bookmark_help.html
>\
> keystrokes/cookie_help.html keystrokes/dired_help.html \
>@@ -39,12 +42,18 @@ config: .FORCE
> PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
> ${GNUCFLAGS} \
> INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
>+ TELNET=/usr/bin/false \
>+ RLOGIN=/usr/bin/false \
>+ TN3270=/usr/bin/false \
> sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc
>--disable-color-style ${CONFIGURE_ARGS}
>
> config.status:
> PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
> ${GNUCFLAGS} \
> INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
>+ TELNET=/usr/bin/false \
>+ RLOGIN=/usr/bin/false \
>+ TN3270=/usr/bin/false \
> sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc
>--disable-color-style ${CONFIGURE_ARGS} ${CF}
>
> lynx.1: ${.CURDIR}/lynx.man

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

STeve Andre'
In reply to this post by Daniel Dickman
On 07/10/14 23:05, Daniel Dickman wrote:

> Patch below turns off the following ancient protocols built into lynx:
> bibp, finger, gopher, and news.
>
> For some urls, lynx will invoke an external command. Turn off telnet,
> rlogin and tn3270 urls by defining them to false(1) as documented in the
> lynx manual.
>
> Finally, turn off the file editor which can be accessed with "g.<enter>"
> using the --disable-dired switch.
>
> ok to commit?
>
>
No.  Just because it's an older crufty protocol, it shouldn't be
removed 'just because'.  I keep on bumping into gopher.  bibp
is definitely used by others.

--STeve Andre'

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Daniel Dickman
In reply to this post by Adam Thompson

> On Jul 10, 2014, at 11:50 PM, Adam Thompson <[hidden email]> wrote:
>
> As a user, not a developer...
> I still use finger, gopher, and news URLs at least once a year each. As a user, I disagree with turning support for those schemes off completely.
> Finger and news I can use another tool, and I'd concede that no-one really *needs* a news reader in base. (I still find having a finger client of some sort in base useful at one site, however.)

finger(1) is still in base. (for now). do you really need to access a finger client from inside a web browser?

for news, do any of the news packages in ports work as a replacement?

> Gopher, however, is not as dead as everyone assumes.
> I believe I can re-enable tn3270 and telnet schemes manually, which is fine. I still use both of those fairly often.

tn3270 is no longer in base so trying this protocol from lynx already does nothing today. I'm just making it slightly more explicit...

for telnet same thing as finger, do you really need to access this from within lynx? why doesn't using telnet from the command line work for you?

> The other protocols are irrelevant to me.

thanks for your feedback.

> -Adam
>
>> On July 10, 2014 10:05:45 PM CDT, Daniel Dickman <[hidden email]> wrote:
>> Patch below turns off the following ancient protocols built into lynx:
>> bibp, finger, gopher, and news.
>>
>> For some urls, lynx will invoke an external command. Turn off telnet,
>> rlogin and tn3270 urls by defining them to false(1) as documented in the
>> lynx manual.
>>
>> Finally, turn off the file editor which can be accessed with "g.<enter>"
>> using the --disable-dired switch.
>>
>> ok to commit?
>>
>> Index: Makefile.bsd-wrapper
>>
>> RCS file: /home/cvs/src/gnu/usr.bin/lynx/Makefile.bsd-wrapper,v
>> retrieving revision 1.24
>> diff -u -p -u -r1.24 Makefile.bsd-wrapper
>> --- Makefile.bsd-wrapper 15 Apr 2014 20:55:42 -0000 1.24
>> +++ Makefile.bsd-wrapper 11 Jul 2014 02:47:31 -0000
>> @@ -5,7 +5,10 @@ CLEANFILES+= lynx.1
>>  DPADD= ${LIBSSL} ${LIBCRYPTO}
>>  
>>  GNUCFLAGS= CC="${CC}" CFLAGS="${CFLAGS} ${COPTS} ${OPT}" LDFLAGS="${LDFLAGS}"
>> -CONFIGURE_ARGS= --with-ssl=/usr
>> --enable-widec --enable-ipv6 --enable-debug
>> +CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6 --enable-debug \
>> +  --disable-bibp-urls --disable-finger --disable-gopher --disable-news \
>> +  --disable-dired
>> +
>>  HTMLDIR= /usr/share/doc/html
>>  HELPFILES= keystrokes/alt_edit_help.html keystrokes/bookmark_help.html \
>>    keystrokes/cookie_help.html keystrokes/dired_help.html \
>> @@ -39,12 +42,18 @@ config: .FORCE
>>   PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
>>   ${GNUCFLAGS} \
>>   INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
>> + TELNET=/usr/bin/false \
>> + RLOGIN=/usr/bin/false \
>> + TN3270=/usr/bin/false \
>>   sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc --disable-color-style ${CONFIGURE_ARGS}
>>  
>>  config.status:
>>   PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
>>   ${GNUCFLAGS} \
>>   INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
>> + TELNET=/usr/bin/false \
>> +
>> RLOGIN=/usr/bin/false \
>> + TN3270=/usr/bin/false \
>>   sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc --disable-color-style ${CONFIGURE_ARGS} ${CF}
>>  
>>  lynx.1: ${.CURDIR}/lynx.man
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Adam Thompson
Pretty standard thing in several companies I do work for is to have an intranet page with http://, ssh://, telnet:// and finger:// (amazingly) links to various devices on the network.  Having to read the source and escape to a shell would be somewhat worse than what I get on a base install today.
IIRC, finger was how we got a quick status overview from... some piece of ATM switching gear?
And yes, I actually do spend a noticeable amount of time at the text console, with no ports installed, when inside a foreign network.
-Adam
[Original message deleted]
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

William Orr-2
In reply to this post by Daniel Dickman

On Jul 10, 2014, at 8:05 PM, Daniel Dickman <[hidden email]> wrote:

> Patch below turns off the following ancient protocols built into lynx:
> bibp, finger, gopher, and news.
>
> For some urls, lynx will invoke an external command. Turn off telnet,
> rlogin and tn3270 urls by defining them to false(1) as documented in the
> lynx manual.
>
> Finally, turn off the file editor which can be accessed with "g.<enter>"
> using the --disable-dired switch.
>
> ok to commit?
>
> Index: Makefile.bsd-wrapper
> ===================================================================
> RCS file: /home/cvs/src/gnu/usr.bin/lynx/Makefile.bsd-wrapper,v
> retrieving revision 1.24
> diff -u -p -u -r1.24 Makefile.bsd-wrapper
> --- Makefile.bsd-wrapper 15 Apr 2014 20:55:42 -0000 1.24
> +++ Makefile.bsd-wrapper 11 Jul 2014 02:47:31 -0000
> @@ -5,7 +5,10 @@ CLEANFILES+= lynx.1
> DPADD= ${LIBSSL} ${LIBCRYPTO}
>
> GNUCFLAGS= CC="${CC}" CFLAGS="${CFLAGS} ${COPTS} ${OPT}" LDFLAGS="${LDFLAGS}"
> -CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6 --enable-debug
> +CONFIGURE_ARGS= --with-ssl=/usr --enable-widec --enable-ipv6 --enable-debug \
> + --disable-bibp-urls --disable-finger --disable-gopher --disable-news \
> + --disable-dired
> +
> HTMLDIR= /usr/share/doc/html
> HELPFILES= keystrokes/alt_edit_help.html keystrokes/bookmark_help.html \
>   keystrokes/cookie_help.html keystrokes/dired_help.html \
> @@ -39,12 +42,18 @@ config: .FORCE
>   PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
>   ${GNUCFLAGS} \
>   INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
> + TELNET=/usr/bin/false \
> + RLOGIN=/usr/bin/false \
> + TN3270=/usr/bin/false \
>   sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc --disable-color-style ${CONFIGURE_ARGS}
>
> config.status:
>   PATH="/bin:/usr/bin:/sbin:/usr/sbin" \
>   ${GNUCFLAGS} \
>   INSTALL_PROGRAM="${INSTALL} ${INSTALL_COPY} ${INSTALL_STRIP}" \
> + TELNET=/usr/bin/false \
> + RLOGIN=/usr/bin/false \
> + TN3270=/usr/bin/false \
>   sh ${.CURDIR}/configure --prefix=/usr --sysconfdir=/etc --disable-color-style ${CONFIGURE_ARGS} ${CF}
>
> lynx.1: ${.CURDIR}/lynx.man
>
I too use gopher in lynx regularly, and would miss support. There is still a surprisingly active community using gopher. (floodgap, et al.)

signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Rod Whitworth-3
In reply to this post by Daniel Dickman
On Thu, 10 Jul 2014 23:17:44 -0400, Daniel Dickman wrote:

>>> For some urls, lynx will invoke an external command. Turn off telnet,
>>> rlogin and tn3270 urls by defining them to false(1) as documented in the
>>> lynx manual.
>>
>> Gopher and NNTP are actually still being used (the former a bit
>> sparsely, but there are a few servers here and there). The rest I don't
>> mind seeing disappear (we don't ship the telnet and rlogin programs
>> anymore AFAIK, I've never heard of bibp, and we have a finger program as
>> an alternative to the functionality in lynx).
>
>this support does not need to be in base.
>
>>
>>> Finally, turn off the file editor which can be accessed with "g.<enter>"
>>> using the --disable-dired switch.
>>
>> I don't see a good reason to get rid of this. What is the rationale?
>>
>
>I want a text browser not a file manager.
>

And what do you gain by killing the file editor?
Provided it doesn't prevent my use of vi (set up as system editor,
invoked with e) I don't care.

I love that simple e when doing major config changes or pf.conf etc
etc.



*** NOTE *** Please DO NOT CC me. I <am> subscribed to the list.
Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou.

Rod/
---
This life is not the real thing.
It is not even in Beta.
If it was, then OpenBSD would already have a man page for it.


Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Theo de Raadt
In reply to this post by Daniel Dickman
> Pretty standard thing in several companies I do work for is to have an intranet page with http://, ssh://, telnet:// and finger:// (amazingly) links to various devices on the network.  Having to read the source and escape to a shell would be somewhat worse than what I get on a base install today.
> IIRC, finger was how we got a quick status overview from... some piece of ATM switching gear?
> And yes, I actually do spend a noticeable amount of time at the text console, with no ports installed, when inside a foreign network.
> -Adam

This banter is annoying.

Please go read the code in question, carefully.  You only need to spend 30
minutes.  It will change your mind.

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Theo de Raadt
In reply to this post by Daniel Dickman
> I too use gopher in lynx regularly, and would miss support. There is =
> still a surprisingly active community using gopher. (floodgap, et al.)

So install a package.

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Theo de Raadt
In reply to this post by Daniel Dickman
> I don't see a good reason to get rid of this. What is the rationale?

Daniel appears to have made a mistake asking for approval on the wrong
list.  He's new here, take it easy on him.

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Stuart Henderson-6
In reply to this post by Theo de Raadt
On 2014/07/11 01:18, Theo de Raadt wrote:
> > I too use gopher in lynx regularly, and would miss support. There is =
> > still a surprisingly active community using gopher. (floodgap, et al.)
>
> So install a package.

Should we just move lynx to packages?

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Brett Mahar-3
On Fri, 11 Jul 2014 09:48:12 +0100
Stuart Henderson <[hidden email]> wrote:

| On 2014/07/11 01:18, Theo de Raadt wrote:
| > > I too use gopher in lynx regularly, and would miss support. There is =
| > > still a surprisingly active community using gopher. (floodgap, et al.)
| >
| > So install a package.
|
| Should we just move lynx to packages?
|

I find lynx really handy to have in base, e.g. installing on a new machine, users can just go to openbsd.org and cut and paste a pkg_path prior to installing anything, and read the faq.

Using openbsd for the first time would have been a lot more painful without a browser in base.

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Stuart Henderson-6
On 2014/07/11 18:51, Brett Mahar wrote:

> On Fri, 11 Jul 2014 09:48:12 +0100
> Stuart Henderson <[hidden email]> wrote:
>
> | On 2014/07/11 01:18, Theo de Raadt wrote:
> | > > I too use gopher in lynx regularly, and would miss support. There is =
> | > > still a surprisingly active community using gopher. (floodgap, et al.)
> | >
> | > So install a package.
> |
> | Should we just move lynx to packages?
> |
>
> I find lynx really handy to have in base, e.g. installing on a new machine, users can just go to openbsd.org and cut and paste a pkg_path prior to installing anything, and read the faq.
>
> Using openbsd for the first time would have been a lot more painful without a browser in base.
>

Thing is, if we need another version of lynx in packages to support
gopher, having one in base as well just gets confusing..

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Theo de Raadt
In reply to this post by Daniel Dickman
>On 2014/07/11 01:18, Theo de Raadt wrote:
>> > I too use gopher in lynx regularly, and would miss support. There is =
>> > still a surprisingly active community using gopher. (floodgap, et al.)
>>
>> So install a package.
>
>Should we just move lynx to packages?

It is nice to have something in base.  Moving it to packages would create
some strong inconviences in tough spots.

The problem is that there isn't a web client which meets the criteria of

        minimal
        small
        trying to be safe code

Everytime someone (it is Daniel this time) tries to avert risk in even a
minor way, the peanut gallery rises up with "I want the whole pig in base".

Daniel is doing the right thing.  Fully loaded lynx can be in the ports tree
too, and we can keep track of the download statistics to see both users who
download it every year...

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Theo de Raadt
In reply to this post by Daniel Dickman
> I find lynx really handy to have in base, e.g. installing on a new
> machine, users can just go to openbsd.org and cut and paste a pkg_path
> prior to installing anything, and read the faq.

that is why it is in base.

but someone on the list wants to visit the openbsd gopher page to get
that information.  crazy people -- you are bat shit crazy.

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Antoine Jacoutot-7
In reply to this post by Theo de Raadt
> Everytime someone (it is Daniel this time) tries to avert risk in even a
> minor way, the peanut gallery rises up with "I want the whole pig in base".
>
> Daniel is doing the right thing.  Fully loaded lynx can be in the ports tree
> too, and we can keep track of the download statistics to see both users who
> download it every year...

Not to mention there are already alternatives for console-based browsers in ports.
I am all for stripping base lynx to the minimum.

--
Antoine

Reply | Threaded
Open this post in threaded view
|

Re: lynx: disable old protocols

Theo de Raadt
In reply to this post by Daniel Dickman
If lynx was removed from base, and only available in ports... how many of
you would even know of it's existance and use it?

1234