View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000776 | bareos-core | documentation | public | 2017-02-08 16:06 | 2017-06-08 12:55 |
Reporter | SvenS | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0000776: some Features are not documented | ||||
Description | 1. Accurate-Options: hits by 'OR' not by 'AND' (m1 => modified-Date OR Sha1-change) 2. Fileset encryption overhaul. (15.2.x) => encryption= fileset option ??? 3. PKI Signer in Client -> What does that? 4. Added prototype of CRL (14.2.x) ? Is this already available? Regards | ||||
Tags | No tags attached. | ||||
1. Accurate-Options: hits by 'OR' not by 'AND' (m1 => modified-Date OR Sha1-change) Yes. Why did you think otherwise? Do you have proposals how to add this to the documentation? 2. Fileset encryption overhaul. (15.2.x) => encryption= fileset option ??? Well, this refers to commit 4b2b7d73e069fd9e6525348b0e32b665729cf64b. While this commits adds a Director configuration FileSet Include option "ForceEncryption", the encryption fileset option refers to the implicit fileset used between Director and File-Daemon. Encryption must be configured on the File-Daemon. 3. PKI Signer in Client -> What does that? I created a patch, adding this information. In short, you can have addition public/private key files, to sign the data. 4. Added prototype of CRL (14.2.x) ? Is this already available? Yes, see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveFdClientTLS%20Certificate%20Revocation%20List |
|
1. Accurate-Options: I have a bug in windows-systems, which change the modified-date from *.eml-files. no user has the files opened/changed. This bug comes only by used the indexed-search. My idea was, i set accurate to 'm1' and bareos hits then, when modified-date AND sha1 changed. Ok, this was not correct. I solved (hopefully) this Problem to add a new Option for this *.eml-files with accurate=1 and for all other files i used accurate=m. 2. is this current implemented? => 16.x.x 3. ok 4. oh, i have this not see, sorry |
|
> 2. is this current implemented? => 16.x.x $ git describe --tags --contains 4b2b7d73e069fd9e6525348b0e32b665729cf64b Release/15.2.1~149 so, yes, it is included in 15.2.1 and higher. |
|
The patch for PKI description is still on the way to be released, however, the rest is clarified and the patch will be published eventually. | |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-02-08 16:06 | SvenS | New Issue | |
2017-02-09 16:03 | joergs | Note Added: 0002555 | |
2017-02-09 16:03 | joergs | Status | new => feedback |
2017-02-09 16:29 | SvenS | Note Added: 0002556 | |
2017-02-09 16:29 | SvenS | Status | feedback => new |
2017-02-16 11:44 | joergs | Note Added: 0002572 | |
2017-02-16 11:46 | joergs | Note Added: 0002573 | |
2017-02-16 11:46 | joergs | Status | new => resolved |
2017-02-16 11:46 | joergs | Resolution | open => fixed |
2017-02-16 11:46 | joergs | Assigned To | => joergs |
2017-06-08 12:55 | joergs | Status | resolved => closed |
2017-06-08 12:55 | joergs | Assigned To | joergs => |