Deep Security 10.0 Update 19 ã®ã¢ã¸ã¥ã¼ã«ãå ¬éãããã¾ããã
â å ¬ééå§æ¥2019 å¹´ 5 æ 28 æ¥ (ç«)
â 対象ã¢ã¸ã¥ã¼ã«
Deep Security Manager
Linux ç Deep Security Agent
Unix ç Deep Security Agent
Windows ç Deep Security Agent
Windows ç Deep Security Notifier
â 追å æ©è½/ä¿®æ£å 容追å æ©è½ãä¿®æ£å 容ã¯ä»å±ã® Readme ãã覧ãã ããã
â»æ¥æ¬èªã®Readmeã¯ä¸ãæ以å ãç®å®ã«å ¬éãããã¾ããâ å ¥ææ¹æ³
Deep Securityãã«ãã»ã³ã¿ã¼ãããã¦ã³ãã¼ãã§ãã¾ãã
サポート情報 : トレンドマイクロ
ãDeep Securityãã«ãã»ã³ã¿ã¼ã
ã¾ãã以ä¸ã®è£½å Q&A ãåããã¦ãåç §ãã ããã
Update ããã°ã©ã ã¨ã¯
Deep Security Manager
2. What's New ======================================================================== 2.1 Enhancements ===================================================================== The following enhancement(s) are included in this release: Enhancement 1: [DSSEG-3779] Updated JRE to the latest Critical Patch Update (8.0.212). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 2: [DSSEG-3750] For AWS connector full synchronization, synchronization errors have been isolated from different regions so that the errors will not affect the synchronization of other regions. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 3: [DSSEG-3730] Added the ability to enable or disable Common Scan Cache for each agent through a CLI command. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2.2 Resolved Known Issues ===================================================================== This release resolves the following issue(s): Issue 1: [DSSEG-3622/SEG-47711/01816620] The Log Source Identifier field of syslog configurations was changed when upgrading Deep Security Manager. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |<< **Linux ç Deep Security Agent >|| 2. What's New ======================================================================== 2.1 Enhancements ===================================================================== There are no enhancements in this release. 2.2 Resolved Known Issues ===================================================================== This release resolves the following issue(s): Issue 1: [DSSEG-3831/SEG-34751/SF01137463] Kernel panic occurred because of redirfs. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-3718/SEG-43481/SF01423970] Certain data structures in the Deep Security Agent packet engine were cleaned up prematurely, leading to a kernel panic and system crash. Solution 2: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-3715] Using a default system language to set the locale on a Linux computer sometimes caused Anti-Malware to not function correctly. Solution 3: This issue is fixed in this release.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 4: [DSSEG-3706/SEG-48947/01929085] The ds_agent process in Deep Security Virtual Appliance sometimes crashed during vMotion due to a race condition. Solution 4: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 5: [DSSEG-3654/SEG-46912/01746052] Anti-Malware events displayed a blank file path with invalid Unicode encoding. Solution 5: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 6: [DSSEG-3620] An invalid printf() format when printing logs indicated that a hash calculation was skipped due to the file size being over the maximum hash calculation size. Solution 6: The printf() format has been updated. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 7: [DSSEG-3594/SEG-47425/SF01804378] Deep Security Agent did not add Python extension module (PYD) files to the inventory of Application Control. Solution 7: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unix ç Deep Security Agent
2. What's New ======================================================================== 2.1 Enhancements ===================================================================== There are no enhancements in this release. 2.2 Resolved Known Issues ===================================================================== This release resolves the following issue(s): Issue 1: [DSSEG-3718/SEG-43481/SF01423970] Certain data structures in the Deep Security Agent packet engine were cleaned up prematurely, leading to a kernel panic and system crash. Solution 1: The code has been modified to address the premature data structure clean up. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-3706/SEG-48947/01929085] The ds_agent process in Deep Security Virtual Appliance sometimes crashed during vMotion due to a race condition. Solution 2: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-3594/SEG-47425/SF01804378] Deep Security Agent did not add Python extension module (PYD) files to the inventory of Application Control. Solution 3: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Windows ç Deep Security Agent
Windows ç Deep Security Notifier
2. What's New ======================================================================== 2.1 Enhancements ===================================================================== There are no enhancements in this release. 2.2 Resolved Known Issues ===================================================================== This release resolves the following issue(s): Issue 1: [DSSEG-3718/SEG-43481/SF01423970] Certain data structures in the Deep Security Agent packet engine were cleaned up prematurely, leading to a kernel panic and system crash. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-3706/SEG-48947/01929085] The ds_agent process in Deep Security Virtual Appliance sometimes crashed during vMotion due to a race condition. Solution 2: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-3594/SEG-47425/SF01804378] Deep Security Agent did not add Python extension module (PYD) files to the inventory of Application Control. Solution 3: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
åãã¢ãªããã®è±åº å人ã§å§ããåãæ¹æ¹é©
- ä½è : è¶å·æ å¸
- åºç社/ã¡ã¼ã«ã¼: éè±ç¤¾
- çºå£²æ¥: 2018/12/14
- ã¡ãã£ã¢: åè¡æ¬
- ãã®ååãå«ãããã°ãè¦ã