Warning: Declaration of Jetpack_IXR_Client::query() should be compatible with IXR_Client::query(...$args) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php on line 30 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:0) in /home/httpd/vhosts/it-sicherheit.li/httpdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1794 {"id":185,"date":"2016-09-21T16:46:37","date_gmt":"2016-09-21T14:46:37","guid":{"rendered":"http:\/\/it-sicherheit.li\/?p=185"},"modified":"2016-09-21T16:47:01","modified_gmt":"2016-09-21T14:47:01","slug":"185-2","status":"publish","type":"post","link":"https:\/\/it-sicherheit.li\/185-2\/","title":{"rendered":"Watchguard ver\u00f6ffentlicht neue Fireware Version"},"content":{"rendered":"

$\"photo-1470848051974-964b789cb6fa-2\"$ <\/p>\n

Watchguard hat eine neue Version der Fireware ver\u00f6ffentlicht.<\/p>\n

Untenstehend sind alle \u00c4nderungen und BugFixes aufgelistet.<\/p>\n

General<\/strong><\/p>\n

\n
This release includes a localization update for WatchGuard System Manager and Fireware Web UI to match Fireware v11.11 functionality for our French, Japanese, and Spanish (LA) users.<\/li>\n
This release resolves a kernel crash on Firebox M400 and M500 appliances when using IPSec VPNs.[90930]<\/em><\/li>\n
This release includes multiple updates to the lighttpd service used by the Firebox web server to ensure best cipher suite compatibility with modern web browsers. [91311]<\/em><\/li>\n
This release resolves an issue that prevented changes from saving correctly from Fireware Web UI when using the localized French interface. [92008]<\/em><\/li>\n
Several Fireware Web UI pages have been updated to guard against XSS injection attempts. [86039]<\/em><\/li>\n
The Fireware Web UI\u00a0Configuration Report now correctly displays all ports and protocols for a firewall policy when multiple ports and protocols are configured. [91347]<\/em><\/li>\n<\/ul>\n
Proxies and Security Subscriptions<\/strong><\/p>\n
\n
The SMTP and HTTPS proxy now support Perfect Forward Secrecy (PFS). [82389, 90567]<\/em><\/li>\n
The HTTPS proxy with Content Inspection enabled no longer crashes when an HTTPS request is sent that uses an unsupported cipher. [91455]<\/em><\/li>\n
This release resolves an issue introduced in Fireware v11.11.1 that prevented traffic from passing through a proxy policy if the receiving interface has an MTU set below 1500. [91761]<\/em><\/li>\n
This release resolves an issue that caused some unhandled denied traffic to show as allowed<\/em> in the traffic log message even though the traffic was denied. [91566]<\/em><\/li>\n
Mobile Security trial licenses now work correctly. [91754]<\/em><\/li>\n
The POP3 proxy now provides the ability to detect file extensions inside compressed attachments.[89078]<\/em><\/li>\n
This release improves the proxy detection of Visual Basic Script macros inside of Microsoft Office documents. [91388]<\/em><\/li>\n
This release resolves an issue that occurred when you edit an existing Explicit Proxy action where Content Inspection is not enabled in CONNECT Tunneling. [91887]<\/em><\/li>\n
The SMTP proxy Return-Receipt-To header rule now correctly matches the header field name. [91504]<\/em><\/li>\n
POP3 proxy log messages now correctly include the User<\/strong> field. [91493]<\/em><\/li>\n
HTTP Proxy Exceptions now save correctly from the French localized Fireware Web UI. [92008]<\/em><\/li>\n
The SIP ALG no longer crashes when referencing a pointer to a proxy connection structure that has already been freed and is no longer valid. [91563]<\/em><\/li>\n
This release updates the proxy handling of SSLv2 traffic. SSLv2 traffic will now pass through the HTTPS-Proxy if Allow only SSL compliant traffic<\/strong> is not enabled and Content Inspection is disabled. [91749]<\/em><\/li>\n
SSL unknown protocol event log messages no longer occur when incomplete SSL\u00a0authentication connections are closed by the Firebox. An example of those log messages looks like this: SSL:1 error;140760FC:SSL routines;SSL23_GET_CLIENT_HELLO;unknown protocol<\/em>. [91641]<\/em><\/li>\n
The proxy will now classify documents containing a file description of \u201aMicrosoft OOXML\u2018 as mime-type \u201aapplication\/vnd.openxmlformats-officedocument\u2018 when no definite mime-type exists within the file.[91853]<\/em><\/li>\n
This release resolves an issue that caused the file scanning process (scand) to crash. [89261]<\/em><\/li>\n
APT Blocker notification logging has been improved to more consistently capture the analysis results for files submitted to the Lastline data center\u2019s next-generation sandbox. [91301]<\/em><\/li>\n
The correct set of DLP content rules is now displayed in Policy Manager for Firebox M200 and M300 appliances. [91044]<\/em><\/li>\n
APT Blocker reports no longer include information about clean objects in their summary details. [91628]<\/em><\/li>\n
The Firebox Configuration Report now correctly displays Denied WebBlocker categories when using the Websense Cloud. [91190]<\/em><\/li>\n
New WebBlocker profiles created manually in Policy Manager now have Log this action enabled by default for WebBlocker categories. [89834]<\/em><\/li>\n<\/ul>\n
Networking<\/strong><\/p>\n
\n
This release resolves an issue that prevented DHCP relay from working correctly through a Branch Office Virtual Interface (VIF) tunnel when PPPoE is enabled. [91515]<\/em><\/li>\n
This release resolves an issue that prevented traffic from correctly matching a policy configured with FQDN in the From<\/strong> field when the Terminal Services Agent is also in use. [91583]<\/em><\/li>\n
This release resolves an issue that caused low throughput for Tagged VLAN traffic on Firebox M200 and M300 appliances. [90500]<\/em><\/li>\n
The throughput of the Firebox built-in wireless interfaces is no longer limited to 56 Mbps when Traffic Management and QoS features are enabled. [90954]<\/em><\/li>\n
A Japanese localization issue related to configuring NTP from Policy Manager has been resolved in this release. [72923]<\/em><\/li>\n
An issue has been resolved that caused the error Internal_Error: Unable to set config<\/em> to display when saving a configuration from Policy Manager. [88214]<\/em><\/li>\n
Internet traffic is no longer allowed after you remove the 0.0.0.0\/0 and Any-External entries from Mobile VPN with IPSec policies. [90205]<\/em><\/li>\n
The Firebox no longer requires a restart when you change the dynamic NAT value in a BOVPN tunnel configuration. [82116]<\/em><\/li>\n
Policy Manager no longer accepts invalid SNAT configurations created when you upgrade older configuration files to WSM v11.10.7 or higher. [90874]<\/em><\/li>\n
This release corrects an issue that caused SFP load failures for Olink adapters. [91844]<\/em><\/li>\n
When a configuration is saved that uses many nested aliases, firewall policies no longer take several minutes to correctly handle network traffic. [91078]<\/em><\/li>\n
This release resolves an issue that resulted in the default Unhandled External Packet-00<\/em> policy to be ordered incorrectly in the firewall policy list, denying legitimate traffic. [91514]<\/em><\/li>\n
This release resolves an issue that caused upgrades to fail when DNS\u00a0forwarding is enabled. [91753]<\/em><\/li>\n<\/ul>\n
Authentication<\/strong><\/p>\n
\n
You can now use certificates without IKE\/IPSec extended key usage for certificate authentication of BOVPN tunnels. [81227]<\/em><\/li>\n
This release resolves a crash in the authentication process (admd) that occurred when you disabled the custom logo for hotspot authentication. [91302]<\/em><\/li>\n<\/ul>\n
VPN<\/strong><\/p>\n
\n
WatchGuard System Manager now displays all active SSL VPN Management Tunnels above the section that shows inactive connections. [85587]<\/em><\/li>\n
PPPoE link stage changes no longer affect VIF VPN tunnels. [91272]<\/em><\/li>\n<\/ul>\n
FireCluster<\/strong><\/p>\n
\n
This release resolves a FireCluster process crash in the CCD daemon. [88594]<\/em><\/li>\n
This release resolves an issue that resulted in high CPU usage by the FireCluster CAD daemon when Firebox System Manager is open on a FireCluster. [91089]<\/em><\/li>\n
A\u00a0problem that caused a generic kernel crash on the backup master Firebox in a FireCluster has been resolved in this release. [91791]<\/em><\/li>\n<\/ul>\n
Centralized Management<\/strong><\/p>\n
\n
Firewall policy icons now show correctly in Dimension Command. [91968]<\/em><\/li>\n
The WatchGuard Server Center Setup Wizard now correctly sets up the Log and Report Server components when using a log encryption key that contains special characters. [71687]<\/em><\/li>\n<\/ul>\n
WatchGuard AP Devices and Gateway Wireless Controller<\/strong><\/p>\n
\n
Actions that you can perform on AP devices are now grouped in an Actions<\/strong> drop-down list. [91451]<\/em><\/li>\n
You can now remove AP\u00a0firmware from your Firebox with Gateway Wireless Controller. [91412]<\/em><\/li>\n
A new packet filter template is available for WatchGuard Wi-Fi Cloud AP management. The packet filter template \u201cWG-Cloud-Managed-WiFi“ defines the required ports (TCP 443 and UDP 3851) and destination domains to enable AP devices to communicate with cloud services. [91647]<\/em><\/li>\n
Domain names for WatchGuard Wi-Fi Cloud services are now included by default in the HTTP Proxy Exceptions, and now configured to bypass HTTPS content inspection by default. [91481, 91482]<\/em><\/li>\n<\/ul>\n $\"Facebook\"$ <\/a> $\"twitter\"$ <\/a> $\"google_plus\"$ <\/a> $\"reddit\"$ <\/a> $\"pinterest\"$ <\/a> $\"linkedin\"$ <\/a> $\"mail\"$ <\/a>","protected":false},"excerpt":{"rendered":"
Watchguard hat eine neue Version der Fireware ver\u00f6ffentlicht. Untenstehend sind alle \u00c4nderungen und BugFixes aufgelistet. General This release includes a localization update for WatchGuard System Manager and Fireware Web UI to match Fireware v11.11 functionality for our French, Japanese, and Spanish (LA) users. This release resolves a kernel crash on Firebox M400 and M500 appliances […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/posts\/185"}],"collection":[{"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/comments?post=185"}],"version-history":[{"count":2,"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/posts\/185\/revisions"}],"predecessor-version":[{"id":187,"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/posts\/185\/revisions\/187"}],"wp:attachment":[{"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/media?parent=185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/categories?post=185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it-sicherheit.li\/wp-json\/wp\/v2\/tags?post=185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}