When NetworkManager is running, it conflicts with the sytemd-networkd
configurations. Disabling NetworkManager on the internal and external
interfaces allows systemd-networkd to properly configure them.
Fixes: #11
Signed-off-by: John Akre <john.w.akre@intel.com>
Vulnerable versions: < 0.12.3
Patched version: 0.12.3
The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vulnerability appears to have been fixed in 0.12.3.
/etc/nginx/conf.d/pxe.conf wasn't being properly generated due to a
missing shell escape, which made things non functional out of the box.
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
The default configuration of nginx was updated to use a configuration
directory. This allows multiple applications to be hosted on the same
nginx instance/host as long as different port numbers are used.
Updating the install script to use this change so that users can get
going with IPXE without problems.
Fixing install sequencing
Checking return codes and printing messages consistently
Not relying on cached DNS providers
Minimizing network interface changes
Resolving conflicts between systemd and dnsmasq
Dropping IPv6 support, not caching DNS servers anymore
Using the option DNSStubListener=no to disable systemd's DNS stub listener. Also adding support for IPv6 NAT and handling hostnames consistently for all web-based services.
Do not run install scripts if requirements are not met
Using more portable shell conditional expressions
Naming install scripts for a clear entry point
Removing unnecessary firewall dependencies
Properly sequencing startup of servers
Properly limiting servers on interfaces
Defaulting to system-preferred DNS resolver
Systems often have their preferred DNS resolvers (e.g. systemd-resolved, NetworkManager). Configuration is simplified by accomodating this fact and not using the DNS stub provided by dnsmasq.
Passing server domain to PXE configuration
Bug fixes for enabling automated install
These install scripts set up a PXE server with the ICIS service. They automate the configuration of Clear Linux for baremetal installations of Clear Linux. They assume a dedicated machine and a clean install is the starting point. They also assume that a NAT network topology is used for PXE booting. They create parameters which users can modify prior to installation. The built-in parameterized systemd service and socket for uwsgi applications is being used to deploy ICIS on Clear Linux.
static/ister/* all contained localhost:5000 as the location of
ister/icis configs. This would never be the case as to the machine
installing localhost is just a pxe booted installer image which is
definitely not hosting those configs. Based on the network_boot
documentation and the bulk_provisioning documentation this should
instead be http://192.168.1.1/icis/.
Signed-off-by: John Andersen <john.s.andersen@intel.com>
Removed unused modules from requirements.txt
cupshelpers
louis
lxml
pycups
pycurl
pygobject
team
Added nginx.conf as an example of how to configure uwsgi with nginx.
This can be dropped in as a replacement for pxe nginx config file as
it includes both locations.
Added isic_uwsgi.service file to be placed in /etc/systemd/service/
to start the uwsgi app.
Added SUBDIR to settings.py so that the uwsgi app responds to
requests when it is served under the /icis subdirectory.
Signed-off-by: John Andersen <john.s.andersen@intel.com>
Mark D Horn