Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please allow @@include to include entire directories #38

Closed
Zugschlus opened this issue Jun 4, 2019 · 2 comments
Closed

Please allow @@include to include entire directories #38

Zugschlus opened this issue Jun 4, 2019 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@Zugschlus
Copy link

This is https://sourceforge.net/p/aide/feature-requests/13/

Hi,

it would be great for the Debian packaging if it were
possible to @include entire directories like
/etc/aide/aide.conf.d/.

aide would have to take precautions to avoid including
backup files and other disabled files. In Debian, for
example, it is common to exclude files ending in
.dpkg-*. There are multiple approaches:

  • Insist on a certain extension (.conf, for example)
  • Having a regexp of allowed file names (settable at
    compile time is acceptable, run time of course preferred)
  • Having a regexp of file names to be ignored

This would allow packages to bring their own aide
configuration snippet and to have it enabled
automatically. The Debian aide packages currently
implement this behavior by having aide wrapped and the
real configuration file built just before aide is
invoked, but that's a fragile hack. Would be better to
have that functionality in aide proper.

Thanks for considering.

@Zugschlus
Copy link
Author

argh, duplicate, please close

@hvhaugwitz hvhaugwitz added the duplicate This issue or pull request already exists label Jun 9, 2019
@hvhaugwitz
Copy link
Member

Duplicate of #4

@hvhaugwitz hvhaugwitz marked this as a duplicate of #4 Jun 9, 2019
@hvhaugwitz hvhaugwitz changed the title @@include Please allow @@include to include entire directories Jun 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants