Re: [Lynx-dev] ot: slightly web host ideas?
I'm thinking maybe we should take this to private mail, since it's not really related to lynx development...? >> However, this brings up another possibility. If you have shell >> access on dreamhost, which is what it sounds like to me, there is no >> technical reason you couldn't run a forwarder there that listens on >> a high port and turns the connection around to the local port 22. > I am unsure I understand this idea. > lets use shellworld as I would want to work where I already know > access on a high port functions. A reasonable idea: make sure it works in a known environment first. > I would have a user name and hostname listening on this higher port, I'm not sure what you mean by having "a user name and hostname" listening on a port. I mean just build a program - or build elsewhere and copy in, if they don't have a compiler installed - that creates a listening socket on the high port. When a connection arrives, it just opens a connection to port 22 on the target host (the dreamhost machine, in my suggested scenario) and passes data in both directions between the two. > where is the configuring actually done, is this like a proxy? I suppose you could call it a proxy. I wouldn't, since it doesn't very closely match what people seem to usually use "proxy" for in networking, but in a sense the word fits. As for where the configuring is done, that depends on the details. If it's a one-off program, it could all be wired into the source code. If you're using a stock program, it could be on the command line or in a file or wherever. Using my own nc, for example, it would be something like nc -server "nc whatever.dreamhost.com 22" 12345 & where all the configuration there is is on the command line. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
Hi Chime, I am not interested in reaching our dreamhost shell from within shellworld itself...can already do that actually. Instead for professional reasons I must reach our office shell the same way i reach shellworld from my desktop proper using my desktop ssh telnet client. The port 443 test I just conducted from my desktop resulted in a remote host time out. Which I guess is at least different from the dh key exchange failures I get normally. Kare On Tue, 21 Aug 2018, Chime Hart wrote: Well Karen, an only thing I can say, in a directory here on Shellworld, you probably have some files in dot ssh where specific hosts and ssh kees would be located. As an example, in my case I have a config with an option so an ssh session will not time out. And lastly, I am almost thinking others were suggesting you try-and-connect to Dream Host on port 443 Chime ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
Well Karen, an only thing I can say, in a directory here on Shellworld, you probably have some files in dot ssh where specific hosts and ssh kees would be located. As an example, in my case I have a config with an option so an ssh session will not time out. And lastly, I am almost thinking others were suggesting you try-and-connect to Dream Host on port 443 Chime ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
I am unsure I understand this idea. lets use shellworld as I would want to work where I already know access on a high port functions. I would have a user name and hostname listening on this higher port, but that actually forwards me to my domain shell account hosted on dreamhost? where is the configuring actually done, is this like a proxy? On Tue, 21 Aug 2018, Mouse wrote: First possible solution is to change the ssh port the daemon uses on dreamhost. We have a shared hosting account with dreamhost, and have been told they do not provide this service I wouldn't expect them to, on shared hosting. However, this brings up another possibility. If you have shell access on dreamhost, which is what it sounds like to me, there is no technical reason you couldn't run a forwarder there that listens on a high port and turns the connection around to the local port 22. (Of course, "no technical reason" is not "no reason". I wouldn't do it without first checking with dreamhost to ensure it wouldn't upset them.) /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
>> First possible solution is to change the ssh port the daemon uses on >> dreamhost. > We have a shared hosting account with dreamhost, and have been told > they do not provide this service I wouldn't expect them to, on shared hosting. However, this brings up another possibility. If you have shell access on dreamhost, which is what it sounds like to me, there is no technical reason you couldn't run a forwarder there that listens on a high port and turns the connection around to the local port 22. (Of course, "no technical reason" is not "no reason". I wouldn't do it without first checking with dreamhost to ensure it wouldn't upset them.) /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
Multiple solutions. First possible solution is to change the ssh port the daemon uses on dreamhost. I used to run my ssh daemon on port 443 when I worked for a company in Delaware who blocked outgoing port 22 requests, but since https uses port 443, they kind of had to let that port through, and that allowed me to connect to my home machines without raising any red flags. Second option is to do what I suggested the first time, setup a virtual private server (vps), and host your own site, lots of companies offer this capability, and it's more secure than a shared host like dreamhost, because you own the entire instance on the server, not just the little corner the host gives you. I use linode.com for this purpose, but you can choose any provider you like. Once the VPS is up and running, you can't tell the difference between it and any other supposedly real host machine on the internet, which means, your company will have complete control over their hosting, email, and whatever else they have on the server. Not to mention, it's trivially easy to maintain linux servers these days, what with all the automation the package tools provide now. ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
Hi there, I would not put it past Bell to deliberately corrupt kex for port-22 connections. I have some confirmation that indeed they have done as much. I don't know shellworld, so I don't know what sort of administrative restirctions they might have, but I suspect there is no _technical_ reason you couldn't run a forwarder there on some high port that forwards on to dreamhost port 22. however, this is not my goal. I can ssh to another ssh from within shellworld, it is the only way I can manage office e-mail. But working from my own computer is preferred, cannot manage files any other way for example. Additionally, if shellworld ever has a problem, I would not be able to work. so I prefer another company all together if possible. Karen ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] ot: slightly web host ideas?
> I work for a media nonprofit who currently has a hosting account with > dreamhost. Unfortunately [...] I can no longer reach our Linux shell > from my desktop ssh client. [...] > for the record, [it's] dh key exchanges that are failing, dreamhost > updated what they would allow recently..why other places on port 22 > are failing though I cannot learn, but suspect bell made changes as > well. I would not put it past Bell to deliberately corrupt kex for port-22 connections. I don't know shellworld, so I don't know what sort of administrative restirctions they might have, but I suspect there is no _technical_ reason you couldn't run a forwarder there on some high port that forwards on to dreamhost port 22. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
[Lynx-dev] ot: slightly web host ideas?
Hi folks, I do not think I have asked this question here. I work for a media nonprofit who currently has a hosting account with dreamhost. Unfortunately, perhaps due to Bell my Canadian provider, or perhaps due to something else, I can no longer reach our Linux shell from my desktop ssh client. I can still reach mine at shellworld, but we do not use port 22 here. I can reach some other locations that likewise use nonstandard ports for ssh. my desire is a hosting plan that includes a shell with its offerings, and with a talented tech person for the testing. We do not have the talent for vps work, and I have yet to find anyone able to assist us to create a Linux server here in Toronto. Anyone know of an option, either a large company or someone who retails? I love shellworld personally, but desire keeping our office structure apart from here if I can. for the record, its dh key exchanges that are failing, dreamhost updated what they would allow recently..why other places on port 22 are failing though I cannot learn, but suspect bell made changes as well. Thanks, Karen ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] Why Do I Receive a Gateway Timeout on www.crisisgroup.org
> Normally 504 gateway errors have nothing to do with your personal > setup. Instead they reflect a communications error between the > site's own servers, timing out communications wise. With lynx, I see an immediate (on human timescales) HTTP/1.1 504 GATEWAY_TIMEOUT response. With my own manual fetcher script, I see a redirect to HTTPS. I infer they are playing silly User-Agent: games. Maybe telling lynx to lie in its User-Agent: header would work around whatever is broken? Gateway Timeout _is_ the standard meaning of 504: "The 504 (Gateway Timeout) status code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.". I suppose it's possible that lynx requests get redirected to a backend that's timing out. But the short time before I get the 504 argues against that. Without transparency into the server setup behind it, it's difficult to say more. Possibly relevant tidbit: www.crisisgroup.org is hosted by amazonaws.com; it resolves to 34.204.104.28 and 34.195.245.170 for me, ec2-34-204-104-28.compute-1.amazonaws.com and ec2-34-195-245-170.compute-1.amazonaws.com. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
