I think you misunderstands what macroses are.
Templates are based on macroses.
So "no macros" = "no templates".
By saying '
templates are based' on macros, it could only mean '
some templates depend' on macros (but only those templates that need a macro to work, like, for example, the default template).
However, your latest statement is not entirely accurate, since you can have a template without macros. Otherwise, you would not be able to install or use the templates I've modified in this post HERE, which can be used with macros disabled (obviously, some features are disabled, such as the ability to delete, rename, or upload files, but it's still a template after all). I'm not looking to argue, but
I do have a clear understanding of what macros are and how they work.
For me HFS is just a Home File Server.
I don't really care about security.
All changes are just for fun...
Then, just for fun, you have given me the opportunity to say the following:
"Ladies and gentlemen, we now have..."
- Option D: DRapid version of HFS! (32 bits & 64 bits)
Yeah! this version is good for those who want to use templates while avoiding this vulnerability, and also for those who, based on his own words (not mine): 'don't really care about security'. So, if you feel comfortable with this, you will find this version very interesting.» Seriously speaking, from what I've seen by running the program and conducting some tests (and also after reviewing the
patch in the source code from an older build), it seems to avoid the vulnerability. However, I don't see this as a definitive long-term solution. That being said, I can't provide ANY guarantees, and it's up to the end-user to decide whether this is appropriate to use or not.
what is missing it´s a swtich of templates as exist when we use a computer or smartphones for example, but in this case it´s more simple to have two versions of hfs and run only the one with macros or not
Even better: two HFS versions on two separate computers!