| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~epics-core/epics-base/+git/asLib:as-hostname into epics-base:7.0 |
| From: | mdavidsaver via Core-talk <[email protected]> |
| To: | mdavidsaver <[email protected]> |
| Date: | Mon, 26 Aug 2019 20:52:00 -0000 |
I'm planning to go ahead and merge with a default of asCheckClientIP=0. Changing this can be a separate discussion. > Why are you (consistently) allocating 24? Force of habit? I can't recall. > default value of asCheckClientIP Can we agree that the desired final solution is defaulting to asCheckClientIP=1 ? > Admittedly this is an unusual situation Yup, given the number of sites not using ACF at all. Is it worth my arguing that any site bothering with access control would likely welcome stronger authentication? > canonical hostname ... a secondary network interface with a different DNS name > ... it could ... How could this be done? I can't think of a way. > has better things to do Granted. It would still be nice to document a possible course of action in case someone is motivated. -- https://code.launchpad.net/~epics-core/epics-base/+git/asLib/+merge/358822 Your team EPICS Core Developers is subscribed to branch epics-base:7.0.