Forwarded from UNDERCODE NEWS
For clients to exert more power over their voice data, Microsoft offers new setting options.
#Updates
#Updates
Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Android Activity life cycle analysis under non-abnormal circumstances :
1. OnCreate(): Indicates that the Activity is being created. This is the first method of the life cycle. This method is only called once. In this method, variables are generally initialized, such as binding the Id of a Button control.
2. onRestart(): Indicates that the Activity is restarting. Under normal circumstances, if the foremost Activity changes from invisible to visible, the onRestart() method will be called. Generally, it is caused by user operations; For example, the current Activity is called A, and the user starts a new Activity called B, then A will be suspended, that is, onPause() and onStop() are called, and then when the user returns to this A, it will appear This situation.
3. onStart(): Indicates that the Activity is being started and is about to start. At this time, the Activity is visible, but it is not displayed to the foreground, and it is not able to interact with the user. In fact, the Activity has been displayed, but we canβt see it. That's it
4. onResume(): Indicates that the Activity is already visible, that is, it is presented on the foreground, that is, it can be seen by our naked eyes. We should pay attention to the difference between onResume() and onStart(). Both onStart() and onResume() represent the visible state of Activity, but when the onStart() method is called, the Activity is in the background, and when the onResume() method is called, the Activity is At the front desk.
5. onPause(): Indicates that the Activity is stopping. At this time, the status of the Activity is invisible, but it is still displayed in the foreground; in general, the method onStop() of the next life cycle will be called. Some data storage operations can be done here, but not too time-consuming, because it will affect the effect of the Activity display.
6. onStop(): Indicates that the Activity is about to stop. At this time, the status of the Activity is not visible, nor is it displayed on the foreground. You can do some heavyweight recycling work here, and it can't be too time-consuming.
7. onDestroy(): Indicates that the Activity is about to be destroyed. This is the last method of the Activity's life cycle, where you can release some resources.
π¦Android Activity life cycle analysis under non-abnormal circumstances :
1. OnCreate(): Indicates that the Activity is being created. This is the first method of the life cycle. This method is only called once. In this method, variables are generally initialized, such as binding the Id of a Button control.
2. onRestart(): Indicates that the Activity is restarting. Under normal circumstances, if the foremost Activity changes from invisible to visible, the onRestart() method will be called. Generally, it is caused by user operations; For example, the current Activity is called A, and the user starts a new Activity called B, then A will be suspended, that is, onPause() and onStop() are called, and then when the user returns to this A, it will appear This situation.
3. onStart(): Indicates that the Activity is being started and is about to start. At this time, the Activity is visible, but it is not displayed to the foreground, and it is not able to interact with the user. In fact, the Activity has been displayed, but we canβt see it. That's it
4. onResume(): Indicates that the Activity is already visible, that is, it is presented on the foreground, that is, it can be seen by our naked eyes. We should pay attention to the difference between onResume() and onStart(). Both onStart() and onResume() represent the visible state of Activity, but when the onStart() method is called, the Activity is in the background, and when the onResume() method is called, the Activity is At the front desk.
5. onPause(): Indicates that the Activity is stopping. At this time, the status of the Activity is invisible, but it is still displayed in the foreground; in general, the method onStop() of the next life cycle will be called. Some data storage operations can be done here, but not too time-consuming, because it will affect the effect of the Activity display.
6. onStop(): Indicates that the Activity is about to stop. At this time, the status of the Activity is not visible, nor is it displayed on the foreground. You can do some heavyweight recycling work here, and it can't be too time-consuming.
7. onDestroy(): Indicates that the Activity is about to be destroyed. This is the last method of the Activity's life cycle, where you can release some resources.
(don't clone any tutorial fro here, you can forward as well)β β β Uππ»βΊπ«Δπ¬πβ β β β
Forwarded from UNDERCODE TESTING
π΅Prestashop'id_product' SQL injection vulnerability (DC: 195-2021)
https://dailycve.com/prestashopidproduct-sql-injection-vulnerability
https://dailycve.com/prestashopidproduct-sql-injection-vulnerability
Dailycve
Prestashop'id_product' SQL injection vulnerability | CVE
Details:
PrestaShop is a free open source e-commerce solution, fully featured and cross-platform, built for web2.0.0.
SQL injection vulnerability of Prestashop'id product '. Vulnerabilities may be exploited by attackers to access personal informationβ¦
Forwarded from UNDERCODE TESTING
π΅Combodo iTop cross-site scripting vulnerability (DC- 194-2021):
https://dailycve.com/combodo-itop-cross-site-scripting-vulnerability
https://dailycve.com/combodo-itop-cross-site-scripting-vulnerability
Dailycve
Combodo iTop cross-site scripting vulnerability | CVE
Details:
Combodo iTop is free software for hardware, software and associated resources management.
Combodo iTop 2.7.2 and releases previous to 3.0.0 have bugs around cross-site scripting. This vulnerability can be abused by attackers to execute crossβ¦
Forwarded from UNDERCODE NEWS
The first digital bank in Japan, everybody's bank opening in May, the "insane" of finance.
#International
#International
Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦ The principle of gesture operation
First of all, in the Android system, each gesture interaction will be executed in the following order.
1. The moment the touch screen is touched, a MotionEvent event is triggered.
2. The event is monitored by OnTouchListener, and the MotionEvent object is obtained in its onTouch() method.
3. Forward the MotionEvent object to OnGestureListener through GestureDetector (gesture recognizer).
4. OnGestureListener obtains the object, listens to the information encapsulated by the object, and makes appropriate feedback.
This sequence can be said to be the principle of gesture operation.
Gesture operation class and interface
Let's take a look at MotionEvent, GestureDetector and OnGestureListener together .
MotionEvent: This class is used to encapsulate motion events such as gestures, touch pens, trackballs, etc. Two important attributes X and Y are encapsulated inside, which are used to record the coordinates of the horizontal axis and the vertical axis respectively.
GestureDetector: Recognize various gestures.
OnGestureListener: This is a gesture interaction monitoring interface, which provides multiple abstract methods, and calls the corresponding method according to the gesture recognition result of GestureDetector.
Gesture operation example
Next, I will demonstrate the implementation of gesture interaction through a code example of switching beautiful pictures, so that everyone has a deeper understanding and memory of the execution sequence above and the distinction between gestures.
First, provide a layout file with only ImageView-main.xml.
π΅XML/HTML code
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent">
<ImageView android:id="@+id/image" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_gravity="center"/>
</LinearLayout>
(don't clone any tutorial fro here, you can forward as well)
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦ The principle of gesture operation
First of all, in the Android system, each gesture interaction will be executed in the following order.
1. The moment the touch screen is touched, a MotionEvent event is triggered.
2. The event is monitored by OnTouchListener, and the MotionEvent object is obtained in its onTouch() method.
3. Forward the MotionEvent object to OnGestureListener through GestureDetector (gesture recognizer).
4. OnGestureListener obtains the object, listens to the information encapsulated by the object, and makes appropriate feedback.
This sequence can be said to be the principle of gesture operation.
Gesture operation class and interface
Let's take a look at MotionEvent, GestureDetector and OnGestureListener together .
MotionEvent: This class is used to encapsulate motion events such as gestures, touch pens, trackballs, etc. Two important attributes X and Y are encapsulated inside, which are used to record the coordinates of the horizontal axis and the vertical axis respectively.
GestureDetector: Recognize various gestures.
OnGestureListener: This is a gesture interaction monitoring interface, which provides multiple abstract methods, and calls the corresponding method according to the gesture recognition result of GestureDetector.
Gesture operation example
Next, I will demonstrate the implementation of gesture interaction through a code example of switching beautiful pictures, so that everyone has a deeper understanding and memory of the execution sequence above and the distinction between gestures.
First, provide a layout file with only ImageView-main.xml.
π΅XML/HTML code
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent">
<ImageView android:id="@+id/image" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_gravity="center"/>
</LinearLayout>
(don't clone any tutorial fro here, you can forward as well)
β β β Uππ»βΊπ«Δπ¬πβ β β β
Forwarded from DailyCVE
π΅Nagios XI remote code execution vulnerability:
https://dailycve.com/nagios-xi-remote-code-execution-vulnerability
https://dailycve.com/nagios-xi-remote-code-execution-vulnerability
Dailycve
Nagios XI remote code execution vulnerability | CVE
Details:
Nagios XI, including dashboards, web-based setup, advanced reporting and rich data visualization, is a market monitoring solution built on Nagios Core.
The "Manage Plug-in" page in Nagios XI 5.8.0 or earlier has a remote code execution flaw.β¦
Forwarded from DailyCVE
π΅IBM Security Guardium Insights Information Disclosure Vulnerability:
https://dailycve.com/ibm-security-guardium-insights-information-disclosure-vulnerability
https://dailycve.com/ibm-security-guardium-insights-information-disclosure-vulnerability
Dailycve
IBM Security Guardium Insights Information Disclosure Vulnerability | CVE
Details:
IBM Security Guardium Insights is a digital data security hybrid cloud center developed to offer a reliable view of the data security and enforcement status of an enterprise.
IBM Encryption Guardium Insights 2.0.2 has a flaw in privacy disclosure.β¦
Forwarded from UNDERCODE NEWS
It's not possible to charge MacBook Pro, netizens collectively fry pot, Apple responds: device issue.
#Bugs
#Bugs
Forwarded from UNDERCODE NEWS
Microsoft patches odd defects in the successful execution of malware in Windows Defender.
#Vulnerabilities
#Vulnerabilities
Forwarded from DailyCVE
π΅Unpatched weak password vulnerability exists in the firewall gateway management system:
https://dailycve.com/unpatched-weak-password-vulnerability-exists-firewall-gateway-management-system
https://dailycve.com/unpatched-weak-password-vulnerability-exists-firewall-gateway-management-system
Dailycve
Unpatched weak password vulnerability exists in the firewall gateway management system | CVE
Details:
Youyou is a registered trademark of Shenzhen Hechen Technology Communication Co., Ltd. In 1998, the company was founded. Mailgard Youyou series mail server, mail archive, spam filtering gateway, mail gateway, global mail gateway, gateway forβ¦
Forwarded from DailyCVE
π΅Unpatched Information disclosure vulnerability exists in DedeCMSV6:
https://dailycve.com/unpatched-information-disclosure-vulnerability-exists-dedecmsv6
https://dailycve.com/unpatched-information-disclosure-vulnerability-exists-dedecmsv6
Dailycve
Unpatched Information disclosure vulnerability exists in DedeCMSV6 | CVE
Details:
DedeCMSV6 is developed based on PHP7.x, is extensible, and is completely open source.
DedeCMSV6 has an information disclosure vulnerability. Attackers can use vulnerabilities to obtain sensitive information
Affected Version:
DEDECMSV6 6.0.2β¦
Forwarded from UNDERCODE NEWS
The Russian authorities want licenses to be enforced for calls via Skype, Viber, WhatsApp
#International
#International
Forwarded from UNDERCODE NEWS
In the US, Xiaomi has fallen out of favour. Now, along with Huawei, she is on the "black list"
#Technologies
#Technologies