Hmm, it doesn't matter about anything you just said.
First tenet of security: If physical security cannot be maintained, all
security is immediately compromised. Period.
This server I am renting may not be under the control of whom I think I
am paying. How could I possibly know?
This server is
On 16 September 2018 at 00:45, Chris Bennett
wrote:
> I get the same internal NAT'ed IP4 address every time, but my public IP4
> address differs over time.
>
> I don't like the idea at all of keeping an open ssh session going on
> without having my equipment on and me nearby.
I don't think you
On Sun, Sep 16, 2018 at 2:50 AM Chris Bennett
wrote:
> See, I'm a US citizen in a country that has these nasty FISA courts and
> a variety of new-ish unconstitutional laws that allow the President and
> others to plant fake content on my server, snatch me up, deny me a
> lawyer, detain me forever
I get the same internal NAT'ed IP4 address every time, but my public IP4
address differs over time.
I don't like the idea at all of keeping an open ssh session going on
without having my equipment on and me nearby.
See, I'm a US citizen in a country that has these nasty FISA courts and
a variety
You can also just set client keepalives. Set TCPKeepAlive in ~/.ssh/config.
This has solved a bunch of random timeout problems due to carrier NAT or
similar.
On Sat, Sep 15, 2018 at 15:36 Constantine A. Murenin
wrote:
> On 15 September 2018 at 09:50, Chris Bennett <
>
On 15 September 2018 at 09:50, Chris Bennett <
cpb_m...@bennettconstruction.us> wrote:
> I am using my phone's hotspot, which may or may not be secure, but is
> not censoring my choice of sites to visit. Public WiFi in the USA does
> so all over the place. Worse, when I lived in Washington State,
On Sat, Sep 15, 2018 at 08:38:26PM +, Stuart Henderson wrote:
> Perhaps your carrier's NAT has a quick timeout.
>
> Try these sysctls:
>
> net.inet.tcp.always_keepalive=1
> net.inet.tcp.keepidle=60
>
> There are ssh-specific keepalives too, but I bet it affects other
> protocols too (ftp
On 2018-09-15, Chris Bennett wrote:
> I am using my phone's hotspot, which may or may not be secure, but is
> not censoring my choice of sites to visit. Public WiFi in the USA does
> so all over the place. Worse, when I lived in Washington State, I was
> next to a Naval Air Station, which
On 9/15/18, Dimitris Papastamos wrote:
[snip]
> Maybe worth lowering ServerAliveInterval in ssh_config and see if that
> helps.
ServerAliveInterval also needs to be set to non-zero because the
default of zero is to not send the messages.
Also in the event of a disconnection anyway, you can use
On Sat, Sep 15, 2018 at 08:50:36AM -0700, Chris Bennett wrote:
> I cannot maintain an SSH connection unattended long enough to go to the
> bathroom and get a cup of coffee without the connection being dropped
> halfway through reading my email.
Maybe worth lowering ServerAliveInterval in
I am using my phone's hotspot, which may or may not be secure, but is
not censoring my choice of sites to visit. Public WiFi in the USA does
so all over the place. Worse, when I lived in Washington State, I was
next to a Naval Air Station, which certainly eavesdrops, not OK, but
this is the land
11 matches
Mail list logo
