×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
James Rich wrote:
The problems I see with this are:
1. What happens if the file is deleted between print jobs?
2. What security implications are there? Specifically, how do we avoid
creating a file that someone has cleverly linked to an important system
file, ownerships, etc.
By that logic, nobody should ever use files for any reason.
What happens if someone deletes ANY file on your system? Wouldn't that
cause a problem? Surely users know better than to delete random files.
Those that don't shouldn't be given access to important files --
including the stuff that lp5250d saves.
How do you prevent lp5250d from overwriting an important system file
thanks to some clever link? Well... uhh... you don't run lp5250d as
root, do you?
I suppose if you're really worried about it, only have lp5250d open a
file if it doesn't exist. That way, you know it can't be pointing to a
system file -- since system files already exist :) Have it use the file
to remember the settings while lp5250d is active, and when lp5250d ends,
have it delete the file. This will also serve to protect you from
having multiple lp5250d jobs trying to use the same file (which probably
wouldn't be good.)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
