| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Build up th manage log section with options to override the "General Logging Options" settings on an individual log basis.
Remove over exuberant gettext's.
Set/adjust filter form field widths to be better fitting for the field types.
Open/Close filter form based on filtering state.
|
| |
|
|
|
|
| |
user. Reported by grandrivers at https://forum.pfsense.org/index.php?topic=103818.msg579069#msg579069
|
|
|
|
| |
conf
|
|
|
|
| |
we don't break current database. Ticket #5624
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
on factory default boot.
This allows the system to switch interfaces from the newer ones in the
default config (e.g. em0 em1) back to the interfaces used by:
Alix - vr1 vr0
APU - re1 re2
that match the WAN and LAN labels printed on many existing devices.
It means these devices can boot the default config and this will
automatically detect that there is no em0/em1 and will instead select
whatever exists out of vr1/vr0 or re1/re2. This avoids the user having
to use the serial cable to do interface assignment when starting a brand
new image, or when resetting to factory defaults. It could easily be
extended to other common interface combinations.
For me, this (or similar) would be very beneficial. At remote sites it
is really good if it is possible to do reset to factory defaults, or put
a fresh CF/SD card in, and the system boots without needing to connect a
serial cable and do interface assignment.
|
|\ \ |
|
| |/
| |
| |
| | |
Add write_config function option to only write the config. Sometimes syncing firewall is not necessary or desirable. ex: changing log display options.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
This file previously had to have a space after "Do you want to proceed [y|n]?" to make the prompt for user input nice. That made it one of the few exceptions to the code style guide, where lines are not supposed to have blank space at the end.
Might as well have 1 less exception to the rule by internationalizing it, which removes the literal "EOD" echo output stuff.
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
This file previously had to have a space after "Do you want to proceed [y|n]?" to make the prompt for user input nice. That made it one of the few exceptions to the code style guide, where lines are not supposed to have blank space at the end.
Might as well have 1 less exception to the rule by internationalizing it, which removes the literal "EOD" echo output stuff.
|
|\ \ \ |
|
| |/ /
| | |
| | | |
This is another one that was using echo EOD stuff and needed a space after "Do you want to proceed [y|n]?".
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
This code is a whole mix of some palces that use gettext() and other chunks of output that are hardcoded text between "EOD" markers.
I have got rid of the "EOD" blocks where there is a question asked - those needed to have a space at the end of the question. To meet code style guide it is easy if questions are all in their own echo statements and the space " " can be visibly coded in.
|
|\ \ \ |
|
| |/ /
| | |
| | | |
These debug blocks look like they should not be in production. if 'debug' is turned on, then they would always log_error() and return for all log lines, even good ones.
|
|\ \ \ |
|
| | | | |
|
|/ / / |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
dpinger always pass 3 parameters to alert_cmd, what can make pfSctl confuse,
This script will be called by dpinger when alarm goes on or off, then
it's going to call pfSctl
|
|\ \ \ |
|
| | | | |
|
|/ / / |
|
|/ / |
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
two minor enhancements -
1) add a comment for skim-readers, that patterns are allowed (but not arrays?) and that no error is returned
2) use array_map rather than foreach loop
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
case insensitive
Currently the username is compared against the common name using a standard PHP comparison,
this is unsafe because it might do unintended type conversions. So change the != comparison to
an !== comparison to make sure the types match.
Since usernames on Windows sytstems are not case-sensitive and prone to case differences in
user input or auto filled fields we should allow case differences between the username and the
certificate common name.
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | | |
SPDNS is a free DynDNS service from the German company Securepoint
Security Solutions
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
For master.
See https://github.com/pfsense/pfsense/pull/2162 for the RELENG_2_2 change.
|
| | | |
| | | |
| | | |
| | | | |
clear they should be using certificates created as Server certificates for this purpose -- it's still valid to use non-server certs but it's not what most people intend to do. Ticket #5602
|
| | | | |
|
|\ \ \ \ |
|