Files
libguestfs/generator
Cole Robinson a2e7dfc73b New API: ntfs_chmod
Add an API to do the equivalent of `chmod [-r] MODE PATH` for
NTFS filesystems.

Files created on a linux ntfs-3g mount can not change permissions
directly. New files and directories are created with rough windows
equivalent of `chmod 777`. These wide open permissions can generate
security warnings on windows after virt-v2v installs bits into
`Program Files\Guestfs`.

Behind the scenes we use `ntfssecaudit(8)` from `ntfsprogs`
which is already part of the appliance. We only expose the chmod-style
feature; the rest of `ntfssecaudit` is concerned reporting and
managing fine grained windows security info which is way more than
we need.

Also note, `ntfssecaudit` needs to run on an unmounted partition
so using this is more complicated than a traditional `chmod` call.

Related: https://issues.redhat.com/browse/RHEL-104352

Signed-off-by: Cole Robinson <crobinso@redhat.com>
2025-09-09 16:29:13 +01:00
..
2025-09-09 16:29:13 +01:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2019-09-10 17:52:16 +02:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-09-09 16:29:13 +01:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2019-07-29 10:28:31 +01:00
2025-04-29 19:05:07 +01:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00
2025-02-16 17:00:46 +00:00

This program generates a large amount of code and documentation for
all the daemon actions.

To add a new action there are only two files you need to change,
'actions_*.ml' to describe the interface, and daemon/<somefile>.c to
write the implementation.

After editing these files, build it (make -C generator) to regenerate
all the output files.  'make' will rerun this automatically when
necessary.

IMPORTANT: This program should NOT print any warnings at compile time
or run time.  If it prints warnings, you should treat them as errors.

OCaml tips:

(1) In emacs, install tuareg-mode to display and format OCaml code
correctly.  'vim' comes with a good OCaml editing mode by default.

(2) Read the resources at http://ocaml.org/learn/

(3) A module called 'Foo' is defined in one or two files called
'foo.mli' and 'foo.ml' (NB: lowercase first letter).  The *.mli file,
if present, defines the public interface for the module.  The *.ml
file is the implementation.  If the *.mli file is missing then
everything is exported.

Some notable files in this directory:

  actions_*.ml        The libguestfs API.
  proc_nr.ml          Procedure numbers associated with each API.
  structs.ml          Structures returned by the API.
  c.ml                Generate C API.
  <lang>.ml           Generate bindings for <lang>.
  main.ml             The main generator program.

Note about long descriptions:

When referring to another action, use the format C<guestfs_other>
(ie. the full name of the C function).  This will be replaced as
appropriate in other language bindings.  Apart from that, long
descriptions are just perldoc paragraphs.

Note about extending functions:

In general you cannot change the name, number of required arguments or
type of required arguments of a function, since this would break
backwards compatibility.

You may add another optional argument, *if* the function has >= 1
optional arguments already.  Add it at the end of the list.

You may add optional arguments to a function that doesn't have any.
However you *must* set the once_had_no_optargs flag to true, so that
the relevant backwards compatibility bindings can be added.