machinery-tool 1.23.1 → 1.24.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +5 -5
- data/.git_revision +1 -1
- data/NEWS +11 -0
- data/export_helpers/kiwi_export_readme.md +3 -3
- data/export_helpers/merge_users_and_groups.pl.erb +1 -1
- data/lib/build_task.rb +5 -3
- data/lib/deploy_task.rb +0 -1
- data/lib/exceptions.rb +13 -0
- data/lib/kiwi_config.rb +3 -9
- data/lib/machinery_helper.rb +15 -1
- data/lib/remote_system.rb +4 -2
- data/lib/system_description.rb +0 -9
- data/lib/version.rb +1 -1
- data/machinery-helper/version.go +1 -1
- data/man/generated/machinery.1.gz +0 -0
- data/manual/docs/index.html +2 -8
- data/manual/docs/machinery.ymp +10 -10
- data/manual/mkdocs.yml +3 -1
- data/manual/site/404.html +145 -0
- data/manual/site/css/base.css +324 -0
- data/manual/site/css/bootstrap-custom.min.css +1 -0
- data/manual/site/css/fixed-positioning.css +0 -0
- data/manual/site/css/font-awesome.min.css +4 -0
- data/manual/site/docs/index.html +25 -70
- data/manual/site/fonts/fontawesome-webfont.eot +0 -0
- data/manual/site/fonts/fontawesome-webfont.svg +2671 -0
- data/manual/site/fonts/fontawesome-webfont.ttf +0 -0
- data/manual/site/fonts/fontawesome-webfont.woff +0 -0
- data/manual/site/fonts/fontawesome-webfont.woff2 +0 -0
- data/manual/site/fonts/glyphicons-halflings-regular.eot +0 -0
- data/manual/site/fonts/glyphicons-halflings-regular.svg +288 -0
- data/manual/site/fonts/glyphicons-halflings-regular.ttf +0 -0
- data/manual/site/fonts/glyphicons-halflings-regular.woff +0 -0
- data/manual/site/fonts/glyphicons-halflings-regular.woff2 +0 -0
- data/manual/site/img/favicon.ico +0 -0
- data/manual/site/img/grid.png +0 -0
- data/manual/site/index.html +135 -396
- data/manual/site/js/base.js +216 -0
- data/manual/site/js/bootstrap-3.0.3.min.js +7 -0
- data/manual/site/js/jquery-1.10.2.min.js +6 -0
- data/manual/site/js/jquery.nicescroll.min.js +0 -0
- data/manual/site/js/jquery.pageslide.min.js +0 -0
- data/manual/site/js/parallaxImg.js +0 -0
- data/manual/site/machinery-analyze.1/index.html +25 -54
- data/manual/site/machinery-build.1/index.html +25 -85
- data/manual/site/machinery-compare.1/index.html +25 -87
- data/manual/site/machinery-config.1/index.html +25 -62
- data/manual/site/machinery-copy.1/index.html +25 -50
- data/manual/site/machinery-deploy.1/index.html +25 -87
- data/manual/site/machinery-export-autoyast.1/index.html +25 -74
- data/manual/site/machinery-export-html.1/index.html +25 -55
- data/manual/site/machinery-export-kiwi.1/index.html +25 -56
- data/manual/site/machinery-inspect-container.1/index.html +25 -129
- data/manual/site/machinery-inspect.1/index.html +25 -172
- data/manual/site/machinery-list.1/index.html +25 -67
- data/manual/site/machinery-man.1/index.html +25 -34
- data/manual/site/machinery-move.1/index.html +25 -49
- data/manual/site/machinery-remove.1/index.html +25 -62
- data/manual/site/machinery-serve.1/index.html +25 -61
- data/manual/site/machinery-show.1/index.html +25 -86
- data/manual/site/machinery-upgrade-format.1/index.html +25 -60
- data/manual/site/machinery-validate.1/index.html +25 -48
- data/manual/site/machinery.ymp +10 -10
- data/manual/site/machinery_main_general.1/index.html +25 -133
- data/manual/site/machinery_main_scopes.1/index.html +25 -129
- data/manual/site/machinery_main_security_implications.1/index.html +25 -108
- data/manual/site/machinery_main_usecases.1/index.html +25 -44
- data/manual/site/search/lunr.js +2986 -0
- data/manual/site/search/main.js +96 -0
- data/manual/site/search/search_index.json +1 -0
- data/manual/site/search/worker.js +128 -0
- data/manual/site/sitemap.xml +48 -87
- data/manual/site/sitemap.xml.gz +0 -0
- data/plugins/os/os_model.rb +0 -29
- data/tools/go.rb +14 -20
- metadata +32 -17
- data/manual/site/mkdocs/js/lunr.min.js +0 -7
- data/manual/site/mkdocs/js/mustache.min.js +0 -1
- data/manual/site/mkdocs/js/require.js +0 -36
- data/manual/site/mkdocs/js/search-results-template.mustache +0 -4
- data/manual/site/mkdocs/js/search.js +0 -88
- data/manual/site/mkdocs/js/text.js +0 -390
- data/manual/site/mkdocs/search_index.json +0 -869
@@ -17,35 +17,35 @@
|
|
17
17
|
|
18
18
|
|
19
19
|
<li class="">
|
20
|
-
<a href="
|
20
|
+
<a href="docs/">Welcome</a>
|
21
21
|
</li>
|
22
22
|
|
23
23
|
|
24
24
|
|
25
25
|
|
26
26
|
<li class="">
|
27
|
-
<a href="
|
27
|
+
<a href="machinery_main_general.1/">General Overview</a>
|
28
28
|
</li>
|
29
29
|
|
30
30
|
|
31
31
|
|
32
32
|
|
33
33
|
<li class="current">
|
34
|
-
<a href="
|
34
|
+
<a href="machinery_main_scopes.1/">Scopes</a>
|
35
35
|
</li>
|
36
36
|
|
37
37
|
|
38
38
|
|
39
39
|
|
40
40
|
<li class="">
|
41
|
-
<a href="
|
41
|
+
<a href="machinery_main_usecases.1/">Use cases</a>
|
42
42
|
</li>
|
43
43
|
|
44
44
|
|
45
45
|
|
46
46
|
|
47
47
|
<li class="">
|
48
|
-
<a href="
|
48
|
+
<a href="machinery_main_security_implications.1/">Security Implications</a>
|
49
49
|
</li>
|
50
50
|
|
51
51
|
|
@@ -55,79 +55,79 @@
|
|
55
55
|
<ul>
|
56
56
|
|
57
57
|
<li class="">
|
58
|
-
<a href="
|
58
|
+
<a href="machinery-analyze.1/">Analyze</a>
|
59
59
|
</li>
|
60
60
|
|
61
61
|
<li class="">
|
62
|
-
<a href="
|
62
|
+
<a href="machinery-build.1/">Build</a>
|
63
63
|
</li>
|
64
64
|
|
65
65
|
<li class="">
|
66
|
-
<a href="
|
66
|
+
<a href="machinery-compare.1/">Compare</a>
|
67
67
|
</li>
|
68
68
|
|
69
69
|
<li class="">
|
70
|
-
<a href="
|
70
|
+
<a href="machinery-config.1/">Config</a>
|
71
71
|
</li>
|
72
72
|
|
73
73
|
<li class="">
|
74
|
-
<a href="
|
74
|
+
<a href="machinery-copy.1/">Copy</a>
|
75
75
|
</li>
|
76
76
|
|
77
77
|
<li class="">
|
78
|
-
<a href="
|
78
|
+
<a href="machinery-deploy.1/">Deploy</a>
|
79
79
|
</li>
|
80
80
|
|
81
81
|
<li class="">
|
82
|
-
<a href="
|
82
|
+
<a href="machinery-export-autoyast.1/">Export AutoYaST</a>
|
83
83
|
</li>
|
84
84
|
|
85
85
|
<li class="">
|
86
|
-
<a href="
|
86
|
+
<a href="machinery-export-kiwi.1/">Export Kiwi</a>
|
87
87
|
</li>
|
88
88
|
|
89
89
|
<li class="">
|
90
|
-
<a href="
|
90
|
+
<a href="machinery-export-html.1/">Export HTML</a>
|
91
91
|
</li>
|
92
92
|
|
93
93
|
<li class="">
|
94
|
-
<a href="
|
94
|
+
<a href="machinery-inspect.1/">Inspect</a>
|
95
95
|
</li>
|
96
96
|
|
97
97
|
<li class="">
|
98
|
-
<a href="
|
98
|
+
<a href="machinery-inspect-container.1/">Inspect Container</a>
|
99
99
|
</li>
|
100
100
|
|
101
101
|
<li class="">
|
102
|
-
<a href="
|
102
|
+
<a href="machinery-list.1/">List</a>
|
103
103
|
</li>
|
104
104
|
|
105
105
|
<li class="">
|
106
|
-
<a href="
|
106
|
+
<a href="machinery-man.1/">Man</a>
|
107
107
|
</li>
|
108
108
|
|
109
109
|
<li class="">
|
110
|
-
<a href="
|
110
|
+
<a href="machinery-move.1/">Move</a>
|
111
111
|
</li>
|
112
112
|
|
113
113
|
<li class="">
|
114
|
-
<a href="
|
114
|
+
<a href="machinery-remove.1/">Remove</a>
|
115
115
|
</li>
|
116
116
|
|
117
117
|
<li class="">
|
118
|
-
<a href="
|
118
|
+
<a href="machinery-serve.1/">Serve</a>
|
119
119
|
</li>
|
120
120
|
|
121
121
|
<li class="">
|
122
|
-
<a href="
|
122
|
+
<a href="machinery-show.1/">Show</a>
|
123
123
|
</li>
|
124
124
|
|
125
125
|
<li class="">
|
126
|
-
<a href="
|
126
|
+
<a href="machinery-upgrade-format.1/">Upgrade Format</a>
|
127
127
|
</li>
|
128
128
|
|
129
129
|
<li class="">
|
130
|
-
<a href="
|
130
|
+
<a href="machinery-validate.1/">Validate</a>
|
131
131
|
</li>
|
132
132
|
|
133
133
|
</ul>
|
@@ -138,111 +138,7 @@
|
|
138
138
|
</ul>
|
139
139
|
</div>
|
140
140
|
<div class="content">
|
141
|
-
|
142
|
-
<ul>
|
143
|
-
<li>os</li>
|
144
|
-
</ul>
|
145
|
-
<p>Contains information about the operating system, name, version, and
|
146
|
-
architecture of the inspected system.</p>
|
147
|
-
<ul>
|
148
|
-
<li>packages</li>
|
149
|
-
</ul>
|
150
|
-
<p>Contains information on all installed packages installed on the
|
151
|
-
inspected system.</p>
|
152
|
-
<ul>
|
153
|
-
<li>patterns</li>
|
154
|
-
</ul>
|
155
|
-
<p>Contains all patterns or tasks installed on the inspected system. A pattern is a
|
156
|
-
collection of software packages, similar to the idea of tasks on Debian/Ubuntu-
|
157
|
-
like systems. The meaning of software patterns depends on the package manager of the
|
158
|
-
distribution.</p>
|
159
|
-
<ul>
|
160
|
-
<li>repositories</li>
|
161
|
-
</ul>
|
162
|
-
<p>Contains all information about software repositories configured on the
|
163
|
-
inspected system. The information about repositories depends on the package
|
164
|
-
manager of the distribution. Machinery collects the following information
|
165
|
-
from each configured repository:</p>
|
166
|
-
<ul>
|
167
|
-
<li>
|
168
|
-
<p>The alias name of the repository.</p>
|
169
|
-
</li>
|
170
|
-
<li>
|
171
|
-
<p>The repository type, rpm-md and YaST types that are used on SUSE systems.</p>
|
172
|
-
</li>
|
173
|
-
<li>
|
174
|
-
<p>The path to the repository. This could be a local path, a remote location,
|
175
|
-
a device, or a file.</p>
|
176
|
-
</li>
|
177
|
-
<li>
|
178
|
-
<p>A boolean flag that indicates if this repository is in use or not.</p>
|
179
|
-
</li>
|
180
|
-
<li>
|
181
|
-
<p>A boolean flag that indicates if this repository should update the locally
|
182
|
-
stored metadata files with metadata files from the origin automatically or
|
183
|
-
not.</p>
|
184
|
-
</li>
|
185
|
-
<li>
|
186
|
-
<p>A boolean flag that indicates if packages which would be installed from
|
187
|
-
this repository should be checked by their gpg key or not.</p>
|
188
|
-
</li>
|
189
|
-
<li>
|
190
|
-
<p>A numeric value for a priority. The priority of a repository is compared
|
191
|
-
to the priorities of all other activated repositories. Values can
|
192
|
-
range from 1 (highest) to 99 (lowest, default).</p>
|
193
|
-
</li>
|
194
|
-
<li>
|
195
|
-
<p>users</p>
|
196
|
-
</li>
|
197
|
-
</ul>
|
198
|
-
<p>Contains information about the system users including user and group ids,
|
199
|
-
login information, such as password hashes and - if available - additional
|
200
|
-
password properties.</p>
|
201
|
-
<ul>
|
202
|
-
<li>groups</li>
|
203
|
-
</ul>
|
204
|
-
<p>Contains information about the system groups such as group attributes and the
|
205
|
-
list of group members.</p>
|
206
|
-
<ul>
|
207
|
-
<li>services</li>
|
208
|
-
</ul>
|
209
|
-
<p>Services are applications running in the background doing continuous work
|
210
|
-
or waiting for requests to do work.
|
211
|
-
The scope determines which services are configured to be started in which
|
212
|
-
runlevel. It uses the <code>chkconfig</code> command to obtain that information.
|
213
|
-
The xinetd services that are also displayed by <code>chkconfig</code> are switched
|
214
|
-
on/off by editing configuration files and are ignored in this context.</p>
|
215
|
-
<ul>
|
216
|
-
<li>changed-config-files</li>
|
217
|
-
</ul>
|
218
|
-
<p>Contains all configuration files which have been changed since they were
|
219
|
-
installed.
|
220
|
-
Changed configuration files are all those files which are marked as such in the
|
221
|
-
package which has installed them. A configuration file change is reported
|
222
|
-
if its content or its attributes like Linux permission bits or ownership
|
223
|
-
have changed.</p>
|
224
|
-
<ul>
|
225
|
-
<li>changed-managed-files</li>
|
226
|
-
</ul>
|
227
|
-
<p>Contains the names and contents of all non-configuration files which have
|
228
|
-
been changed compared to the files in the package. A file change is reported
|
229
|
-
if its content or its attributes like Linux permission bits or ownership
|
230
|
-
have changed.</p>
|
231
|
-
<ul>
|
232
|
-
<li>unmanaged-files</li>
|
233
|
-
</ul>
|
234
|
-
<p>Contains the names and contents of all files which are not part of any package.
|
235
|
-
The list of unmanaged files contains only plain files and
|
236
|
-
directories. Special files like device nodes, named pipes and Unix domain
|
237
|
-
sockets are ignored. The directories <code>/tmp</code>, <code>/var/tmp</code>, <code>/.snapshots/</code>,
|
238
|
-
<code>/var/run</code> and special mounts like procfs and sysfs are ignored, too.
|
239
|
-
If a directory is in this list, no file or directory below it belongs to a
|
240
|
-
package.</p>
|
241
|
-
<p>Meta data information of unmanaged files is only available if the files were
|
242
|
-
extracted during inspection.</p>
|
243
|
-
<p>Using the <code>--extract-unmanaged-files</code> option, the files are transferred from
|
244
|
-
the system and stored in the system description. Depending on the content of
|
245
|
-
the inspected system, the amount of data stored may be huge.</p>
|
141
|
+
|
246
142
|
</div>
|
247
143
|
</div>
|
248
144
|
</body>
|
@@ -17,35 +17,35 @@
|
|
17
17
|
|
18
18
|
|
19
19
|
<li class="">
|
20
|
-
<a href="
|
20
|
+
<a href="docs/">Welcome</a>
|
21
21
|
</li>
|
22
22
|
|
23
23
|
|
24
24
|
|
25
25
|
|
26
26
|
<li class="">
|
27
|
-
<a href="
|
27
|
+
<a href="machinery_main_general.1/">General Overview</a>
|
28
28
|
</li>
|
29
29
|
|
30
30
|
|
31
31
|
|
32
32
|
|
33
33
|
<li class="">
|
34
|
-
<a href="
|
34
|
+
<a href="machinery_main_scopes.1/">Scopes</a>
|
35
35
|
</li>
|
36
36
|
|
37
37
|
|
38
38
|
|
39
39
|
|
40
40
|
<li class="">
|
41
|
-
<a href="
|
41
|
+
<a href="machinery_main_usecases.1/">Use cases</a>
|
42
42
|
</li>
|
43
43
|
|
44
44
|
|
45
45
|
|
46
46
|
|
47
47
|
<li class="current">
|
48
|
-
<a href="
|
48
|
+
<a href="machinery_main_security_implications.1/">Security Implications</a>
|
49
49
|
</li>
|
50
50
|
|
51
51
|
|
@@ -55,79 +55,79 @@
|
|
55
55
|
<ul>
|
56
56
|
|
57
57
|
<li class="">
|
58
|
-
<a href="
|
58
|
+
<a href="machinery-analyze.1/">Analyze</a>
|
59
59
|
</li>
|
60
60
|
|
61
61
|
<li class="">
|
62
|
-
<a href="
|
62
|
+
<a href="machinery-build.1/">Build</a>
|
63
63
|
</li>
|
64
64
|
|
65
65
|
<li class="">
|
66
|
-
<a href="
|
66
|
+
<a href="machinery-compare.1/">Compare</a>
|
67
67
|
</li>
|
68
68
|
|
69
69
|
<li class="">
|
70
|
-
<a href="
|
70
|
+
<a href="machinery-config.1/">Config</a>
|
71
71
|
</li>
|
72
72
|
|
73
73
|
<li class="">
|
74
|
-
<a href="
|
74
|
+
<a href="machinery-copy.1/">Copy</a>
|
75
75
|
</li>
|
76
76
|
|
77
77
|
<li class="">
|
78
|
-
<a href="
|
78
|
+
<a href="machinery-deploy.1/">Deploy</a>
|
79
79
|
</li>
|
80
80
|
|
81
81
|
<li class="">
|
82
|
-
<a href="
|
82
|
+
<a href="machinery-export-autoyast.1/">Export AutoYaST</a>
|
83
83
|
</li>
|
84
84
|
|
85
85
|
<li class="">
|
86
|
-
<a href="
|
86
|
+
<a href="machinery-export-kiwi.1/">Export Kiwi</a>
|
87
87
|
</li>
|
88
88
|
|
89
89
|
<li class="">
|
90
|
-
<a href="
|
90
|
+
<a href="machinery-export-html.1/">Export HTML</a>
|
91
91
|
</li>
|
92
92
|
|
93
93
|
<li class="">
|
94
|
-
<a href="
|
94
|
+
<a href="machinery-inspect.1/">Inspect</a>
|
95
95
|
</li>
|
96
96
|
|
97
97
|
<li class="">
|
98
|
-
<a href="
|
98
|
+
<a href="machinery-inspect-container.1/">Inspect Container</a>
|
99
99
|
</li>
|
100
100
|
|
101
101
|
<li class="">
|
102
|
-
<a href="
|
102
|
+
<a href="machinery-list.1/">List</a>
|
103
103
|
</li>
|
104
104
|
|
105
105
|
<li class="">
|
106
|
-
<a href="
|
106
|
+
<a href="machinery-man.1/">Man</a>
|
107
107
|
</li>
|
108
108
|
|
109
109
|
<li class="">
|
110
|
-
<a href="
|
110
|
+
<a href="machinery-move.1/">Move</a>
|
111
111
|
</li>
|
112
112
|
|
113
113
|
<li class="">
|
114
|
-
<a href="
|
114
|
+
<a href="machinery-remove.1/">Remove</a>
|
115
115
|
</li>
|
116
116
|
|
117
117
|
<li class="">
|
118
|
-
<a href="
|
118
|
+
<a href="machinery-serve.1/">Serve</a>
|
119
119
|
</li>
|
120
120
|
|
121
121
|
<li class="">
|
122
|
-
<a href="
|
122
|
+
<a href="machinery-show.1/">Show</a>
|
123
123
|
</li>
|
124
124
|
|
125
125
|
<li class="">
|
126
|
-
<a href="
|
126
|
+
<a href="machinery-upgrade-format.1/">Upgrade Format</a>
|
127
127
|
</li>
|
128
128
|
|
129
129
|
<li class="">
|
130
|
-
<a href="
|
130
|
+
<a href="machinery-validate.1/">Validate</a>
|
131
131
|
</li>
|
132
132
|
|
133
133
|
</ul>
|
@@ -138,90 +138,7 @@
|
|
138
138
|
</ul>
|
139
139
|
</div>
|
140
140
|
<div class="content">
|
141
|
-
|
142
|
-
<p>This document describes security related issues administrators need to be aware of when using
|
143
|
-
Machinery.</p>
|
144
|
-
<h2 id="inspection">Inspection</h2>
|
145
|
-
<p>Machinery inspects several parts of a system which are covered by Machinery's scopes.
|
146
|
-
Information about scopes is listed <a href="../machinery_main_scopes.1/">here</a>.</p>
|
147
|
-
<p>Users of Machinery who inspect systems need to be aware of the security implications
|
148
|
-
to take the right decisions on how to protect the retrieved data.</p>
|
149
|
-
<h2 id="retrieval-of-data">Retrieval of Data</h2>
|
150
|
-
<p>Machinery transfers data from one end point to another via SSH (Secure Shell, using public key authentication).</p>
|
151
|
-
<p>Depending on the scope, Machinery <a href="../machinery_main_scopes.1/">collects information</a>
|
152
|
-
about files on the system. Additionally, when the <code>--extract-files</code> option is given for the
|
153
|
-
<code>inspect</code> command, not only the meta data about the files (e.g. permission bits, owner, group etc
|
154
|
-
.) but also the file content is extracted. Machinery does not distinguish between sensitive
|
155
|
-
data (such as private keys or password files). That means that everyone with access to the system
|
156
|
-
description has automatically access to <strong>all</strong> extracted files and contained sensitive data.</p>
|
157
|
-
<h4 id="rootsudo-privileges">root/sudo Privileges</h4>
|
158
|
-
<p>An inspection can only be done, when the user on the inspected system is either root or has
|
159
|
-
sudo privileges. Information about the required sudo configuration can be found
|
160
|
-
<a href="../machinery-inspect.1/#prerequisites">here</a>.</p>
|
161
|
-
<h2 id="storage-of-data">Storage of Data</h2>
|
162
|
-
<h4 id="access-restrictions">Access Restrictions</h4>
|
163
|
-
<p>After an inspection has been completed, the directory where the description is stored is made
|
164
|
-
readable only for the user. The data is not encrypted by Machinery.</p>
|
165
|
-
<h4 id="used-permission-bits">Used Permission Bits</h4>
|
166
|
-
<p>When Machinery extracts data, it sets permission bits for files and directories as follows:</p>
|
167
|
-
<table>
|
168
|
-
<thead>
|
169
|
-
<tr>
|
170
|
-
<th>Permission Bits</th>
|
171
|
-
<th>Used for ...</th>
|
172
|
-
</tr>
|
173
|
-
</thead>
|
174
|
-
<tbody>
|
175
|
-
<tr>
|
176
|
-
<td>0700</td>
|
177
|
-
<td>... directories inside the description directory</td>
|
178
|
-
</tr>
|
179
|
-
<tr>
|
180
|
-
<td>0600</td>
|
181
|
-
<td>... for files inside the description directory</td>
|
182
|
-
</tr>
|
183
|
-
</tbody>
|
184
|
-
</table>
|
185
|
-
<h4 id="accessing-system-descriptions">Accessing System Descriptions</h4>
|
186
|
-
<p>By default, all system descriptions are stored in the directory <code>.machinery</code> in the home directory
|
187
|
-
of the user running Machinery. The directory can be redefined by the environment variable
|
188
|
-
<code>$MACHINERY_DIR</code>. Each description has its own subdirectory. There is a <code>manifest.json</code> file in
|
189
|
-
each description directory which contains the data of the inspection. Extracted files are stored in
|
190
|
-
separate subdirectories inside the same description directory.</p>
|
191
|
-
<h2 id="presentation-of-data">Presentation of Data</h2>
|
192
|
-
<p>There are several ways how data can be presented to one or more users. The user has the option to
|
193
|
-
either start a web server and view descriptions or view the descriptions only in the console.</p>
|
194
|
-
<p>The following commands are used to present data to users:</p>
|
195
|
-
<ul>
|
196
|
-
<li>show</li>
|
197
|
-
<li>compare</li>
|
198
|
-
<li>serve</li>
|
199
|
-
<li>list</li>
|
200
|
-
</ul>
|
201
|
-
<p>All of the commands listed above also have a <code>--html</code> option. When this option is used, Machinery
|
202
|
-
starts a web server what will listen on the IP address <code>127.0.0.1</code>. The <code>serve</code> command
|
203
|
-
offers also a <code>--public</code> option which makes the server listen on all configured IP addresses.</p>
|
204
|
-
<p><strong>WARNING:</strong> When making the server reachable from the outside, users can modify the link to
|
205
|
-
access also other descriptions. There is currently no way to restrict the access to only one
|
206
|
-
description.</p>
|
207
|
-
<p>The <code>serve</code> command also allows the user to specify a port via the <code>--port</code> option. When no port
|
208
|
-
is specified, the default port which is configured in the machinery config file in
|
209
|
-
<code>~/.machinery/machinery.config</code>) will be taken.</p>
|
210
|
-
<h2 id="export-of-data">Export of Data</h2>
|
211
|
-
<h4 id="export-autoyast">export-autoyast</h4>
|
212
|
-
<p>The <code>export-autoyast</code> command creates an AutoYaST profile for an automated installation. This will result
|
213
|
-
in tar balls containing the extracted files from the system description. These files
|
214
|
-
potentially contain sensitive data (e.g. passwords). This fact needs to be kept in mind, especially
|
215
|
-
if these files are copied to a web server for an AutoYaST installation via HTTP.</p>
|
216
|
-
<h4 id="export-kiwi">export-kiwi</h4>
|
217
|
-
<p>The program <strong>kiwi</strong> allows you to build OS images for deployment. Machinery gives
|
218
|
-
you the opportunity to export a KIWI description. This description can be used to build an image via Kiwi.
|
219
|
-
The <code>export-kiwi</code> command creates a directory, where it stores the Kiwi configuration and the files
|
220
|
-
of a system description. These files potentially contain sensitive data (e.g. passwords).</p>
|
221
|
-
<h4 id="build">build</h4>
|
222
|
-
<p>The created image potentially contains sensitive data (e.g. passwords) from extracted files.</p>
|
223
|
-
<h4 id="deploy">deploy</h4>
|
224
|
-
<p>The uploaded image potentially contains sensitive data (e.g. passwords) from extracted files.</p>
|
141
|
+
|
225
142
|
</div>
|
226
143
|
</div>
|
227
144
|
</body>
|