blob: 37ac7c3a162ae18097af7a6c0f97295bcdb3cd75 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] password-less ssh
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20password-less%20ssh&In-Reply-To=%3C4E7E22C9.5030205%40unige.ch%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="005471.html">
<LINK REL="Next" HREF="005470.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] password-less ssh</H1>
<B>Juergen Harms</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20password-less%20ssh&In-Reply-To=%3C4E7E22C9.5030205%40unige.ch%3E"
TITLE="[Mageia-discuss] password-less ssh">Juergen.Harms at unige.ch
</A><BR>
<I>Sat Sep 24 20:34:49 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="005471.html">[Mageia-discuss] password-less ssh
</A></li>
<LI>Next message: <A HREF="005470.html">[Mageia-discuss] password-less ssh
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5472">[ date ]</a>
<a href="thread.html#5472">[ thread ]</a>
<a href="subject.html#5472">[ subject ]</a>
<a href="author.html#5472">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 09/24/2011 06:30 PM, Deri James wrote:
><i> It "StrictModes" is turned on in sshd_conf I assume the permissions of the
</I>><i> link itself is checked
</I>
StrictMode no or yes does not make any difference: password still
required if login from the laptop to the server
> Another possibility is to set AuthorizedKeysFile to
> point to your file in /etc
I did not try to put my user data to /etc ..., /etc is not a place for
user-specific data, and is specific to each OS partition. I tried (and
/common is not on my root file-system - the problem might be there)
AuthorizedKeysFile /common/share/home/harms/.ssh/authorized_keys
Result: password is still required; but there is an effect: a plain
/home/harms/.ssh/authorized_keys is not seen any more.
Summary
- ssh does not correctly use an authorized_keys file if the target is a
symbolic link form $HOME/.ssh
- this problem only exists for sessions started from a laptop on a
desktop server, the other way round there is no problem
- this problem has only recently appeared
- using mount --bind for mounting $HOME/.ssh at on a template
directory results in correct behaviour
- twiddling /etc/ssh/sshd_conf (StrictMode, AuthorizedKeysFile) does
not produce satisfactory results.
For me, there is a simple workaround which I now use: rather than
creating a link to my template file, I put a copy of the template data
into $HOME/.ssh/authorized_keys (extremely unfrequent modifications, no
problem to create a new copy in case the template data really change)
The reason why I started this discussion is that there may be a faint
risk that an abnormal behaviour of ssh could create problems in
situations less obvious than a plain remote shell session - many
distributed applications use ssh "hidden" in the application.
But since I am the only one to observe this problem, opening a bug is in
my opinion not justified.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="005471.html">[Mageia-discuss] password-less ssh
</A></li>
<LI>Next message: <A HREF="005470.html">[Mageia-discuss] password-less ssh
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5472">[ date ]</a>
<a href="thread.html#5472">[ thread ]</a>
<a href="subject.html#5472">[ subject ]</a>
<a href="author.html#5472">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
