| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: syncterm |
Re: Re: syncterm
By: Michiel Broek to R.J. Clay on Tue Mar 21 2006 10:09 pm
> Hi Jame,
>
> R.J. Clay wrote to Michiel Broek:
> RJC> On Mon, 20 Mar 2006 17:27:15 -0500, Michiel Broek wrote:
> RJC>
> RJC> > I got some things figured out. Your bbs puts the telnet
connection in
> RJC> > binary mode.
> RJC> > My bbs runs from inetd and doesn't put the telnet connection into
> RJC> > binary mode.
> RJC>
> RJC> But it can, can it not? At least, according to the man page for
> RJC> in.telnetd on my system (Debian Sarge), it can when it receives the
> RJC> proper telnet options... ("WILL BINARY", I think
it is from the
> client...
>
> RJC> "DO BINARY" is what in.telnetd sends...)
>
> Yes it does. Terminal programs that send the will and do binary have to
> problems with downloads. Syncterm doesn't do that and depends on the server
> side. But in.telnetd will not do that on it's own, it only sets binary mode
> if the clients asks for it.
>
>
> RJC> > I tried to put the connection into binary mode but that
doesn't work
> RJC> > because in.telnetd sits between mbsebbs and the internet.
> RJC>
> RJC> That would be up to in.telnetd, wouldn't it? Need to figure a way
> to
>
> RJC> capture debug info on the session start up... I only did some simple
> RJC> testing; I can't tell for sure if, for instance, the telnet session
> RJC> is accepting the "-8" option I used when I telneted
that way to the
> system
>
> RJC> where mbse is... (does look like the ssl session was accepted
> though...)
>
>
> On my system (Slackware) there is no option to force telnetd into 8 bit
> binary mode.
>
> With telnet mailer sessions mbcico is started directly from inetd. With
> human telnet on port 23, in.telnetd handles the connection and starts a
> login process, and that will finally start mbsebbs.
>
> So I depend on the client terminal to put the connection into binary mode.
> It's not perfect I know, but from the linux clients syncterm is the first
> one I see that doesn't set it.
>
> Short term solution is to change syncterm. At least I want to try that just
> to be sure that it can work.
> For the longer solution mbse needs it's own telnetd for login, but that can
> then be made also to handle incoming mailer sessions on port 23 like some
> other systems can do.
That change to SyncTerm has been made. Did you get my last message on this
topic?
> I also found that it doesn't harm that both the server and the client put
> the connection into binary mode.
That's correct. And for clarification a Telnet connection can have binary mode
enabled in either (or both) directions.
digital man
Snapple "Real Fact" #125:
Pigeons have been trained by the U.S. Coast Guard to spot people lost at sea.
Norco, CA WX: 69.8øF, 36% humidity, 6 mph SW wind, 0.28 inches rain/24hrs
--- SBBSecho 2.11-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)SEEN-BY: 633/267 270 5030/786 @PATH: 103/705 218/903 261/38 140/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.