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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
/*
* libpathrs: safe path resolution on Linux
* Copyright (C) 2019, 2020 Aleksa Sarai <cyphar@cyphar.com>
* Copyright (C) 2019, 2020 SUSE LLC
*
* This program is free software: you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
* Software Foundation, either version 3 of the License, or (at your option) any
* later version.
*
* This program is distributed in the hope that it will be useful, but WITHOUT ANY
* WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
* PARTICULAR PURPOSE. See the GNU General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public License along
* with this program. If not, see <https://www.gnu.org/licenses/>.
*/
/*
* WARNING: This file was auto-generated by rust-cbindgen. Don't modify it.
* Instead, re-generate it with:
* % cbindgen -c cbindgen.toml -o include/pathrs.h
*/
/**
* The type of object being passed to "object agnostic" libpathrs functions.
*/
typedef enum pathrs_type_t;
/**
* The backend used for path resolution within a `pathrs_root_t` to get a
* `pathrs_handle_t`. Can be used with `pathrs_configure()` to change the
* resolver for a `pathrs_root_t`.
*/
;
typedef uint64_t pathrs_resolver_t;
/**
* This is only exported to work around a Rust compiler restriction. Consider
* it an implementation detail and don't make use of it.
*/
typedef struct __pathrs_handle_t __pathrs_handle_t;
/**
* This is only exported to work around a Rust compiler restriction. Consider
* it an implementation detail and don't make use of it.
*/
typedef struct __pathrs_root_t __pathrs_root_t;
/**
* Represents a single entry in a Rust backtrace in C. This structure is
* owned by the relevant `pathrs_error_t`.
*/
typedef struct __CBINDGEN_ALIGNED __pathrs_backtrace_entry_t;
/**
* Represents a Rust Vec<T> in an FFI-safe way. It is absolutely critical that
* the FFI user does not modify *any* of these fields.
*/
typedef struct __CBINDGEN_ALIGNED __pathrs_backtrace_t;
/**
* This is only exported to work around a Rust compiler restriction. Consider
* it an implementation detail and don't make use of it.
*/
typedef __pathrs_backtrace_t pathrs_backtrace_t;
/**
* Attempts to represent a Rust Error type in C. This structure must be freed
* using `pathrs_free(PATHRS_ERROR)`.
*/
typedef struct __CBINDGEN_ALIGNED pathrs_error_t;
/**
* A handle to a path within a given Root. This handle references an
* already-resolved path which can be used for only one purpose -- to "re-open"
* the handle and get an actual fs::File which can be used for ordinary
* operations.
*
* It is critical for the safety of users of this library that *at no point* do
* you use interfaces like libc::openat directly on file descriptors you get
* from using this library (or extract the RawFd from a fs::File). You must
* always use operations through a Root.
*/
typedef __pathrs_handle_t pathrs_handle_t;
/**
* A handle to the root of a directory tree to resolve within. The only purpose
* of this "root handle" is to get Handles to inodes within the directory tree.
*
* At the time of writing, it is considered a *VERY BAD IDEA* to open a Root
* inside a possibly-attacker-controlled directory tree. While we do have
* protections that should defend against it (for both drivers), it's far more
* dangerous than just opening a directory tree which is not inside a
* potentially-untrusted directory.
*/
typedef __pathrs_root_t pathrs_root_t;
/**
* Global configuration for pathrs, for use with
* `pathrs_configure(PATHRS_NONE, NULL)`
*/
typedef struct __CBINDGEN_ALIGNED pathrs_config_global_t;
/**
* Configuration for a specific `pathrs_root_t`, for use with
* `pathrs_configure(PATHRS_ROOT, <root>)`
*/
typedef struct __CBINDGEN_ALIGNED pathrs_config_root_t;
/**
* Configure pathrs and its objects and fetch the current configuration.
*
* Given a (ptr_type, ptr) combination the provided @new_ptr configuration will
* be applied, while the previous configuration will be stored in @old_ptr.
*
* If @new_ptr is NULL the active configuration will be unchanged (but @old_ptr
* will be filled with the active configuration). Similarly, if @old_ptr is
* NULL the active configuration will be changed but the old configuration will
* not be stored anywhere. If both are NULL, the operation is a no-op.
*
* Only certain objects can be configured with pathrs_configure():
*
* * PATHRS_NONE (@ptr == NULL), with pathrs_config_global_t.
* * PATHRS_ROOT, with pathrs_config_root_t.
*
* The caller *must* set @cfg_size to the sizeof the configuration type being
* passed. This is used for backwards and forward compatibility (similar to the
* openat2(2) and similar syscalls).
*
* For all other types, a pathrs_error_t will be returned (and as usual, it is
* up to the caller to pathrs_free it).
*/
pathrs_error_t *;
pathrs_handle_t *;
/**
* Duplicate a file-based libpathrs object.
*
* The new object will have a separate lifetime from the original, but will
* refer to the same underlying file (and contain the same configuration, if
* applicable).
*
* Only certain objects can be duplicated with pathrs_duplicate():
*
* * PATHRS_ROOT, with pathrs_root_t.
* * PATHRS_HANDLE, with pathrs_handle_t.
*
* If an error occurs, NULL is returned. The object passed with this request
* will store the error (which can be retrieved with pathrs_error). If the
* object type is not one of the permitted values above, the error is lost.
*/
void *;
/**
* Retrieve the error stored by a pathrs object.
*
* Whenever an error occurs during an operation on a pathrs object, the object
* will store the error for retrieval with pathrs_error(). Note that performing
* any subsequent operations will clear the stored error -- so the error must
* immediately be fetched by the caller.
*
* If there is no error associated with the object, NULL is returned (thus you
* can safely check for whether an error occurred with pathrs_error).
*
* It is critical that the correct pathrs_type_t is provided for the given
* pointer (otherwise memory corruption will almost certainly occur).
*/
pathrs_error_t *;
/**
* Free a libpathrs object.
*
* It is critical that the correct pathrs_type_t is provided for the given
* pointer (otherwise memory corruption will almost certainly occur).
*/
void ;
/**
* Construct a new file-based libpathrs object from a file descriptor.
*
* The main purpose of this interface (combined with pathrs_into_fd) is to
* allow for libpathrs objects to be passed to other processes through Unix
* sockets (with SCM_RIGHTS) or other such tricks. The underlying file
* descriptor of such an object can be thought of as the "serialised" version
* of the object, and this method effectively "de-serialises" it.
*
* Note that libpathrs will duplicate the file descriptor passed to it (in
* order to avoid higher-level language runtimes from accidentally closing the
* file descriptor). The caller must therefore close the file descriptor passed
* if they no longer require it after this call.
*
* Only certain objects can be constructed from file descriptors with
* pathrs_from_fd():
*
* * PATHRS_ROOT, producing a pathrs_root_t.
* (NOTE: The configuration will be the system default.)
* * PATHRS_HANDLE, producing a pathrs_handle_t.
*
* It is critical that the file descriptor provided has the same semantics as
* file descriptors which libpathrs would generate itself. This usually means
* that you should only ever call pathrs_from_fd() with a file descriptor that
* originally came from pathrs_into_fd().
*
* If an error occurs, an object of the requested type is returned containing
* the error (which can be retrieved with pathrs_error) -- as with pathrs_open.
* If the object type requested is not one of the permitted values above, NULL
* is returned.
*/
void *;
int ;
/**
* Unwrap a file-based libpathrs object to obtain its underlying file
* descriptor.
*
* The main purpose of this interface (combined with pathrs_from_fd) is to
* allow for libpathrs objects to be passed to other processes through Unix
* sockets (with SCM_RIGHTS) or other such tricks. The underlying file
* descriptor of such an object can be thought of as the "serialised" version
* of the object.
*
* This consumes the original object, and it is the caller's responsibility to
* close the file descriptor (with close) or otherwise handle its lifetime.
*
* Only certain objects can be converted into file descriptors with
* pathrs_into_fd():
*
* * PATHRS_ROOT, with pathrs_root_t.
* * PATHRS_HANDLE, with pathrs_handle_t.
*
* It is critical that you do not operate on this file descriptor yourself,
* because the security properties of libpathrs depend on users doing all
* relevant filesystem operations through libpathrs.
*
* If an error occurs, -1 is returned. You may retrieve the error by calling
* pathrs_error on the passed object (as long as the object is one of the
* permitted ones listed above).
*
* If an error occurs, -1 is returned. The object passed with this request will
* store the error (which can be retrieved with pathrs_error). If the object
* type is not one of the permitted values above, the error is lost.
*/
int ;
int ;
int ;
/**
* Open a root handle.
*
* The default resolver is automatically chosen based on the running kernel.
* You can switch the resolver used with pathrs_configure() -- though this
* is not strictly recommended unless you have a good reason to do it.
*
* The provided path must be an existing directory.
*
* # Errors
*
* Unlike other libpathrs methods, pathrs_open will *always* return a
* pathrs_root_t (but in the case of an error, the returned root handle will
* be a "dummy" which is just used to store the error encountered during
* setup). Errors during pathrs_open() can only be detected by immediately
* calling pathrs_error() with the returned root handle -- and as with valid
* root handles, the caller must free it with pathrs_free().
*
* This unfortunate API wart is necessary because there is no obvious place to
* store a libpathrs error when first creating an root handle (other than
* using thread-local storage but that opens several other cans of worms).
* This approach was chosen because in principle users could call
* pathrs_error() after every libpathrs API call.
*/
pathrs_root_t *;
/**
* Within the given root's tree, perform the rename (with all symlinks being
* scoped to the root). The flags argument is identical to the renameat2(2)
* flags that are supported on the system.
*/
int ;
/**
* "Upgrade" the handle to a usable fd, suitable for reading and writing. This
* does not consume the original handle (allowing for it to be used many
* times).
*
* It should be noted that the use of O_CREAT *is not* supported (and will
* result in an error). Handles only refer to *existing* files. Instead you
* need to use creat().
*
* In addition, O_NOCTTY is automatically set when opening the path. If you
* want to use the path as a controlling terminal, you will have to do
* ioctl(fd, TIOCSCTTY, 0) yourself.
*/
int ;
/**
* Within the given root's tree, resolve the given path (with all symlinks
* being scoped to the root) and return a handle to that path. The path *must
* already exist*, otherwise an error will occur.
*/
pathrs_handle_t *;
int ;
/* LIBPATHRS_H */