Experimental Physics and Industrial Control System
Looking at the YACC code for parsing access control files, I see
that "name lists" consist of comma separated "names":
uag_user_list: uag_user_list ',' uag_user_list_name
| uag_user_list_name
;
uag_user_list_name: tokenNAME
Looking at the LEX code, I see that names consist of the
following characters:
name [a-zA-Z0-9_\-:\.\[\]<>;]+
That works fine for the user name I was assigned on my LINUX
box, but it does not work well for the user name I was assigned on
my Windows box, which has an embedded space (' ').
The expedient solution is to change the space to another
semi-invisible character on my Windows box. However, I was wondering
whether others have run into this, and/or perceive this as an issue
worth trying to address, or whether there are additional problem
associated with supporting a space character in access control.
-- Larry
P.S. I *suspect* that there are no issues with supporting embedded
spaces in user names (other than readability issues), since the user
name string is treated as a string once it has been read in, and that
it is no less readable than other strings with embedded spaces, such
as scan rates of "1 second".
- Navigate by Date:
- Prev:
open post at DESY in the cryogenic control group Matthias Clausen
- Next:
Definitions of RELEASE_ variables Chris Mayer
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
open post at DESY in the cryogenic control group Matthias Clausen
- Next:
Definitions of RELEASE_ variables Chris Mayer
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025