Re: [Sikuli-driver] [Question #699868]: High-risk vulnerability in Log4j 2.x --- not used with SikuliX
Question #699868 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/699868 Status: Answered => Open Kunal Gajbhiye is still having a problem: Hi, I am using sikulixapi-2.0.5.jar wherein I can see that log4j is being used which is of 1.2.17 version. So i just want to know whether log4j vulnerability issue will impact or not? I have gone thru above answered question but still i am not getting clarity from it so please assist me. -- You received this question notification because your team Sikuli Drivers is an answer contact for SikuliX. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #699868]: High-risk vulnerability in Log4j !!!
New question #699868 on SikuliX: https://answers.launchpad.net/sikuli/+question/699868 High-risk vulnerability in Log4j which is being used in sikulixapi 2.0.5 package. Do we have any solution on this or we are safe to use the Sikuli version 2.0.5 ? For reference please check the url - https://www.veracode.com/blog/security-news/urgent-analysis-and-remediation-guidance-log4j-zero-day-rce-cve-2021-44228 Requesting to provide the solution as soon as possible. -- You received this question notification because your team Sikuli Drivers is an answer contact for SikuliX. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1890138] Re: Facing issue with Sikuli 2.0.4 version for find() function.
Thanks RaiMan for very quick response this is what we need to know once again thanks for great product. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1890138 Title: Facing issue with Sikuli 2.0.4 version for find() function. Status in Sikuli: Won't Fix Bug description: Our objective is to be able to specify the timeout for the location of a bitmap. In early version of Sikuli i.e. 1.1.1 find() function internally calls autoWaitTimeout() which wait's for stipulated time like if we overrides the autoWaitTime by placing below code, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1890138/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1890138] [NEW] Facing issue with Sikuli 2.0.4 version for find() function.
Public bug reported: Our objective is to be able to specify the timeout for the location of a bitmap. In early version of Sikuli i.e. 1.1.1 find() function internally calls autoWaitTimeout() which wait's for stipulated time like if we overrides the autoWaitTime by placing below code, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. ** Affects: sikuli Importance: Undecided Status: New -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1890138 Title: Facing issue with Sikuli 2.0.4 version for find() function. Status in Sikuli: New Bug description: Our objective is to be able to specify the timeout for the location of a bitmap. In early version of Sikuli i.e. 1.1.1 find() function internally calls autoWaitTimeout() which wait's for stipulated time like if we overrides the autoWaitTime by placing below code, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1890138/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
