On 11/14/2014 09:37 PM, Basil Mohamed Gohar wrote:
> On 11/14/2014 08:49 AM, Florian Weimer wrote:
>> On 11/14/2014 02:46 PM, Basil Mohamed Gohar wrote:
>>> The only non-standard thing I can think I'm doing is running SSH on
>>> another port, and I've already gotten SELinux to accept that fact. T
On Fri, Nov 14, 2014 at 7:37 PM, Basil Mohamed Gohar
wrote:
> Thanks for the tip. I'll skim through this and report back if I find
> anything interesting.
I'd be interested in seeing your sshd logs. With the systemd journal,
you can output the sshd related log entries with the following
command
On 11/14/2014 08:49 AM, Florian Weimer wrote:
> On 11/14/2014 02:46 PM, Basil Mohamed Gohar wrote:
> > The only non-standard thing I can think I'm doing is running SSH on
> > another port, and I've already gotten SELinux to accept that fact. The
> > issue is not that it won't even connect. It's t
On 11/14/2014 02:46 PM, Basil Mohamed Gohar wrote:
The only non-standard thing I can think I'm doing is running SSH on
another port, and I've already gotten SELinux to accept that fact. The
issue is not that it won't even connect. It's that it goes down without
any logical explanation. The mos
I have found that in Fedora 20 I've been unable to keep my SSH server at
my home up for long periods of time. I will enable it with systemctl
and start it, and it will work for a time, but then later days (after,
maybe, 3 or so days) it will be unavailable and I'll have to restart it.
The only no
