Authentication with keys: Difference between revisions

From Earlham CS Department
Jump to navigation Jump to search
Craigje (talk | contribs)
Created page with "Name of Task: Auth with keys People Involved: Date Started: Aug 2018 Deadline: Description There are several machines (notably the post-upgrade CentOS machines bronte an..."
 
Update status of task
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
Name of Task: Auth with keys
'''Name of Task:''' Auth with keys


People Involved:  
'''People Involved:''' Laurence Ruberl


Date Started: Aug 2018
'''Date Started:''' 2018


Deadline:
'''Deadline:''' 2018


Description
'''Description'''


There are several machines (notably the post-upgrade CentOS machines bronte and pollock) that do not use an ssh key, only a password, for authentication. This isn't convenient nad needs fixed.
There are several machines (notably the post-upgrade CentOS machines bronte and pollock) that do not use an ssh key, only a password, for authentication. This isn't convenient nad needs fixed.


Status
Description goes here


Date Last Updated:
'''Status''' SELinux seemed to be causing the problem, at least for most users.  It has been set to permissive on both Bronte and Pollock and was already set that way on Whedon.
 
'''Date Last Updated:''' 10/8/18


[[Category:Open Tasks]]
[[Category:Open Tasks]]

Latest revision as of 16:42, 8 October 2018

Name of Task: Auth with keys

People Involved: Laurence Ruberl

Date Started: 2018

Deadline: 2018

Description

There are several machines (notably the post-upgrade CentOS machines bronte and pollock) that do not use an ssh key, only a password, for authentication. This isn't convenient nad needs fixed.

Description goes here

Status SELinux seemed to be causing the problem, at least for most users. It has been set to permissive on both Bronte and Pollock and was already set that way on Whedon.

Date Last Updated: 10/8/18