public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] core 130: Remove snort settings dir after convert has run.
Date: Mon, 18 Mar 2019 19:05:43 +0000	[thread overview]
Message-ID: <064B3B73-4F78-44CF-AC18-1160635FFB23@ipfire.org> (raw)
In-Reply-To: <dc612a13b49e0de9ac4b0bea70c6f9b9b05489c5.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]

Hi,

I do not see why the converter does not take care of the removal. That would only be one place.

But I will merge this if you want me to.

-Michael

> On 18 Mar 2019, at 19:04, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
>> Almost?
> 
> As long as the files are present, the settings will be converted. May
> in special cases if a user does something really weird may the
> converter will fail, but in this case I think it even would be better
> start a new clean IPS configuration.
> 
>> 
>> How is this directory removed when a backup was restored?
>> 
> 
> By the backup.pl script. It checks if after the backup a snort settings
> dir (/var/ipfire/snort) exists, launches the converter and afterwards
> deletes the directory.
> 
> See:
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=8c27372438dd267648cba48b86d85a594f14be1c
> 
>> -Michael
>> 
>>> On 18 Mar 2019, at 18:56, Stefan Schantl <stefan.schantl(a)ipfire.org
>>>> wrote:
>>> 
>>> Hello Michael,
>>>> Hi,
>>>> 
>>>> What happens when the converter has failed? Is that a
>>>> possibility?
>>> 
>>> There is almost no risk, that this would be happened.
>>> 
>>> It contains checks if all corresponding files are present and will
>>> contain the settings from them - I do not see a case where any
>>> problems
>>> can be happen.
>>> 
>>> Best regards,
>>> 
>>> -Stefan
>>> 
>>>> -Michael
>>>> 
>>>>> On 18 Mar 2019, at 18:46, Stefan Schantl <
>>>>> stefan.schantl(a)ipfire.org
>>>>>> wrote:
>>>>> 
>>>>> When all settings have been converted, the files and directory
>>>>> are
>>>>> not
>>>>> needed anymore.
>>>>> 
>>>>> If they will be left and at a later time an backup will be
>>>>> restored, the
>>>>> converter will be started by the backup script again and would
>>>>> be
>>>>> restore those
>>>>> old snort settings and replace the current IPS settings.
>>>>> 
>>>>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>>>>> ---
>>>>> config/rootfiles/core/130/update.sh | 3 +++
>>>>> 1 file changed, 3 insertions(+)
>>>>> 
>>>>> diff --git a/config/rootfiles/core/130/update.sh
>>>>> b/config/rootfiles/core/130/update.sh
>>>>> index d33321c32..f3dc0d85a 100644
>>>>> --- a/config/rootfiles/core/130/update.sh
>>>>> +++ b/config/rootfiles/core/130/update.sh
>>>>> @@ -74,6 +74,9 @@ ldconfig
>>>>> # Migrate snort configuration to suricata
>>>>> /usr/sbin/convert-snort
>>>>> 
>>>>> +# Remove snort settings
>>>>> +rm -rvf /var/ipfire/snort
>>>>> +
>>>>> # Start services
>>>>> /etc/init.d/collectd restart
>>>>> /etc/init.d/firewall restart
>>>>> -- 
>>>>> 2.20.1
>>>>> 


  reply	other threads:[~2019-03-18 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 18:46 Stefan Schantl
2019-03-18 18:47 ` Michael Tremer
2019-03-18 18:56   ` Stefan Schantl
2019-03-18 18:57     ` Michael Tremer
2019-03-18 19:04       ` Stefan Schantl
2019-03-18 19:05         ` Michael Tremer [this message]
2019-03-18 19:11           ` Stefan Schantl
2019-03-18 19:12             ` Michael Tremer
2019-03-18 19:15               ` Stefan Schantl
2019-03-18 19:15                 ` Michael Tremer
2019-03-18 19:20               ` Horace Michael
2019-03-18 19:22                 ` Michael Tremer
2019-03-18 19:31                 ` Stefan Schantl
2019-03-18 19:33               ` [PATCH] Core 130: Remove files after convert-snort has been launched Stefan Schantl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=064B3B73-4F78-44CF-AC18-1160635FFB23@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox