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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] Switching to openssh match instead of using nss ldap
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Switching%20to%20openssh%20match%20instead%20of%20using%20nss%0A%20ldap&In-Reply-To=%3C4DFC3AE7.7060405%40vilarem.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003644.html">
<LINK REL="Next" HREF="003647.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] Switching to openssh match instead of using nss ldap</H1>
<B>Maât</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Switching%20to%20openssh%20match%20instead%20of%20using%20nss%0A%20ldap&In-Reply-To=%3C4DFC3AE7.7060405%40vilarem.net%3E"
TITLE="[Mageia-sysadm] Switching to openssh match instead of using nss ldap">maat-ml at vilarem.net
</A><BR>
<I>Sat Jun 18 07:43:03 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003644.html">[Mageia-sysadm] Switching to openssh match instead of using nss ldap
</A></li>
<LI>Next message: <A HREF="003647.html">[Mageia-sysadm] Puppet Report for alamut.mageia.org
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3648">[ date ]</a>
<a href="thread.html#3648">[ thread ]</a>
<a href="subject.html#3648">[ subject ]</a>
<a href="author.html#3648">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 15/06/2011 23:37, Michael Scherer a écrit :
><i> Hi,
</I>><i>
</I>><i> some months ago, Buchan proposed that we use openssh Match feature to
</I>><i> force the command when connecting to ssh, instead of replacing the shell
</I>><i> with nss ldap. The benefit being that we could then start to log using
</I>><i> our account instead of using root, and use sudo, for auditing purpose.
</I>><i>
</I>><i> While working on setting up a secure sftp server for the artwork team, I
</I>><i> looked on how we could make sure that account are chrooted in the web
</I>><i> root. It seems that unlike svn or git, you cannot force the path except
</I>><i> if you use ChrootDirectory.
</I>><i>
</I>><i> So this seemed the right moment to do the switch.
</I>><i>
</I>><i> I just did a test on a vm, and it still work fine ( at least on my
</I>><i> account ). However, we have to do both at the same time, as forcing the
</I>><i> command in ssh and ldap result in blocking everything.
</I>><i>
</I>><i> So the idea is :
</I>><i> - disable the nss ldap forcing
</I>><i> - add various openssh config for the various type of config we can
</I>><i> have :
</I>><i>
</I>><i> - regular ssh, only for admin ( jonund, ecosse, alamut, friteuse )
</I>><i> - ssh access to svn, git ( valstar )
</I>><i> - sftp chrooted for artwork team AND ssh access for web team
</I>><i> ( champagne )
</I>><i>
</I>><i> But this would requires some lifting in the ssh module before.
</I>><i>
</I>><i> Any comment ?
</I>just one comment : \o/
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003644.html">[Mageia-sysadm] Switching to openssh match instead of using nss ldap
</A></li>
<LI>Next message: <A HREF="003647.html">[Mageia-sysadm] Puppet Report for alamut.mageia.org
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3648">[ date ]</a>
<a href="thread.html#3648">[ thread ]</a>
<a href="subject.html#3648">[ subject ]</a>
<a href="author.html#3648">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
