[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [suse-security] susefirewall2 problem (SuSE 10.1) [solved]



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The Monday 2006-07-24 at 14:43 +0200, Richard Ems wrote:

> >From older messages on this list, I learned that defining a variable
> over multiple lines is not allowed in SuSEfirewall (and probably on all
> configuration files handled by SuSEconfig).
> 
> The error you are seeing is due to an update from SuSEfirewall2 (which
> recreated the conf file) or to a configuration through yast.
> 
> So, forget using
> 
> FOO="                   \
>         1.2.3.4         \
>         5.6.7.8         \
> "
> 
> and type
> 
> FOO="1.2.3.4   5.6.7.8" .

Actually, I had:

FOO=" 1.2.3.4         \
## coment
## coment
      5.6.7.8         \

It was the comments in the middle that were giving problems, not the 
multiline difinition - which must work, it is standard script syntax. What 
I don't understand is how those comments got in there. It could be the 
updated from 9.3 to 10.1 process, or it could be my thick hands.


> Or, don't use yast to edit your FW config 

I never do, I edit the file directly.

> and save/check/restore after a
> SuSEFirewall2 update.

- -- 
Cheers,
       Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFExSugtTMYHG2NR9URAs3WAJ44QJzi6ORV8si5JixCqXE3mXhAnACdEVcb
Pft/NRdH+nhTtdVKwES+CLU=
=95e9
-----END PGP SIGNATURE-----


-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here