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
100
101
102
103
104
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] bug, omission or feature
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%2C%20omission%20or%20feature&In-Reply-To=%3C201206041310.24829.bgmilne%40zarb.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016118.html">
<LINK REL="Next" HREF="016160.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] bug, omission or feature</H1>
<B>Buchan Milne</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%2C%20omission%20or%20feature&In-Reply-To=%3C201206041310.24829.bgmilne%40zarb.org%3E"
TITLE="[Mageia-dev] bug, omission or feature">bgmilne at zarb.org
</A><BR>
<I>Mon Jun 4 13:10:24 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016118.html">[Mageia-dev] bug, omission or feature
</A></li>
<LI>Next message: <A HREF="016160.html">[Mageia-dev] bug, omission or feature
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16149">[ date ]</a>
<a href="thread.html#16149">[ thread ]</a>
<a href="subject.html#16149">[ subject ]</a>
<a href="author.html#16149">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sunday, 3 June 2012 17:52:47 Colin Guthrie wrote:
><i> On the whole, this kind of "security" is basically bullshit anyway.
</I>
You can't make that assessment without understanding the rest of the security
environment.
><i> It
</I>><i> might make things a tiny bit harder, but if you can get into the
</I>><i> bootloader to append a 1 on the command line,
</I>
Maybe you *can't* append anything you like to the command-line. Maybe the
bootloader configuration has a 'boot single' option, which should require
entry of the root password to access the system.
><i> you can also append
</I>><i> init=/bin/bash too which totally bypasses everything too.
</I>
Not if the bootloader configuration is password protected (IOW, you can boot
any configured option, but if you want to modify anything, you need to provide
a password, different from the root password).
><i> So while it's
</I>><i> maybe a nice idea, for all practical purposes, it's not any kind of real
</I>><i> security anyway, so don't rely on it!
</I>
No security implementation relies on a single control being in place. A numebr
of modern security best practices have thousands of controls, and the
requirement for a password to be entered to boot single is almost always one
of them, and a requirement for a bootloader password is usually another.
Regards,
Buchan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/mageia-dev/attachments/20120604/e81fe020/attachment-0001.html>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016118.html">[Mageia-dev] bug, omission or feature
</A></li>
<LI>Next message: <A HREF="016160.html">[Mageia-dev] bug, omission or feature
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16149">[ date ]</a>
<a href="thread.html#16149">[ thread ]</a>
<a href="subject.html#16149">[ subject ]</a>
<a href="author.html#16149">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
