Follow-up Comment #4, bug #64612 (project groff):
I was not aware that a change proposed to forbid paths in .fp third parameter
and the "name" written by afmtodit, had also (unintentionally) prevented paths
in the grops download file, with no diagnostic message.
The proposed "fix" seems to be addition of a diagnostic message and a
discussion on what to call a new environment variable! My preference would be
to find a safe way to restore the previous behaviour re. download paths, given
the change is unintentional in the first place. If the download file
containing the path to the postscript font is only writeable by root I think
we can trust the path. Further, for the users safety, it would make sense to
always search for a groff font in the system directories first before
directories provided by the user, this would prevent masking a system font
with a nefarious font from somewhere else. Fortunately, the bug only affects
grops, not gropdf, so paths are not forbidden in the its own download file.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64612>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
