IT Questions and Answers :)

Wednesday, November 20, 2019

Which of the following does a hard reset on an iOS-based device NOT do?

Which of the following does a hard reset on an iOS-based device NOT do?

  • Delete data
  • Reset the drivers
  • Reset the OS
  • Stop all apps [Soft rest]


EXPLANATION

Soft Reset iPhone

The simple act of Restarting iPhone by first Turning the iPhone OFF and starting it back again has the potential to fix minor software glitches on your iPhone.
In troubleshooting terms, the act of Restarting an iPhone is commonly referred to as Soft Reset and it is also known as Power Cycling your device.
An iPhone Soft Reset, is known to fix performance issues like iPhone not ringing, iPhone not vibrating, iPhone resetting/rebooting continuously, and also the issue of iPhone getting stuck, freezing or Apps crashing on iPhone.
Since, the Side button (Power Button) on iPhone has been programmed to perform multiple tasks like activating Siri, Accessing Apple Pay or activating SOS, you can no longer use it to Soft Reset iPhone.
Hence, it is time to get used to a new method to Soft Reset iPhone using steps as listed below.

Steps to Soft Reset iPhone

Follow the steps below to Soft Reset iPhone and fix minor software glitches on your iPhone.
1. Press and Hold the Side button and the Volume Up (or the Volume Down) button on your iPhone , until you see “Slide to Power OFF” option on the screen of your iPhone.
3. Wait for your iPhone to completely Power OFF.
4. Wait for 10 seconds, and then Press and Hold on the Side button (Power button) on your iPhone, until you see the Apple logo appearing on the screen of your iPhone.



 


Share:

An application won't close on an Android phone. You've tried to Force Stop, but it doesn't work. What should you do next?

An application won't close on an Android phone. You've tried to Force Stop, but it doesn't work. What should you do next?

  • Soft reset the device
  • Hard reset the device
  • Stop the service in Running Services
  • Bring the device to an authorized service center 
An application won't close on an Android phone. You've tried to Force Stop, but it doesn't work. What should you do next?

EXPLANATION

Soft reset is one of the easiest ways you can rest your Android device. A soft reset means turn off your device and restart, it will shut all functions of your device and start it all over again. Doing this always refreshes your device clearing all running applications, which frees up the random access memory. It often increases functionality and does not affect your data.

Android apps can be stopped in three ways:
  1. Closing the app from the recent list (but this does not stop background services)
  2. Manually going to the 'Running Applications' setting and stopping the app or background process
  3. Force stopping the app
When method 1 and 2 mentioned above are used to end the application the onDestroy() method is called. In simple words, the application is closed with proper care and the programmer can do whatever they want before closing the app. So whenever the app is stopped in this way, the application is informed so that it can prepare itself to close.
But what if you Force Stop the app?
Well.. If you do this, the application is closed in a harsh way. This will immediately stop all processes (background process and foreground process) belonging to the app without informing it. So the application does not know that it will be stopped so it cannot prepare itself.
Example : If you start WhatsApp and then remove it from the recent list you will still receive notifications.
But if you Force Stop it, you will no longer receive notifications.
In simple words
Regular Stop:— 'Hey man i am going to shoot you. Any last wishes?'
Force Stop:— *Shoots

 

Share:

Which of the following is the first Wi-Fi troubleshooting method you can try on a mobile device?

Which of the following is the first Wi-Fi troubleshooting method you can try on a mobile device?

  • Rename the SSID
  • Use a static IP
  • Power cycle the device
  • Restart Bluetooth 
Which of the following is the first Wi-Fi troubleshooting method you can try on a mobile device?

EXPLANATION

Power cycling an electronic device is a technical way of saying "resetting" it. When you power cycle a device, you turn it off and then turn it back on again. Pretty high-tech, huh? Usually, you should let the device sit for a couple seconds after turning it off to make sure the memory in the device is fully cleared before turning it back on.

Any electronic device can be power cycled, but the term is frequently used with cable modems, DSL modems, and routers. This is because small internal errors in these devices can prevent them from functioning correctly. Resetting them typically fixes the errors and allows them to work correctly again.
Share:

Which of the following conditions can yield a "javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure" message?

Which of the following conditions can yield a "javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure" message?

  • Allow all cryptographic protocols/ciphers, including vulnerable ones, to run on the JVM and server
  • Restricting the JVM and server to use only ONE common protocol/cipher
  • A cryptographic protocol/cipher mismatch between the JVM and the JRE
  • A cryptographic protocol/cipher mismatch between the JVM and server 

Which of the following conditions can yield a "javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure" message?

EXPLANATION

The error message "javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure" is notoriously a signal of an issue between the cryptographic protocols and/or ciphers available on both the server and JVM.
Essentially, the error translates to "None of the cryptographic protocols and ciphers on the server and JVM match" thus the initial "Handshake" between the systems fails.

SOURCE

https://dzone.com/articles/troubleshooting-javaxnetsslsslhandshakeexception-r
Share:

Assuming all features are supported, on a *NIX system, what is the best way to protect an existing $file on an Extended Filesystem (ext#) partition from any changes and set maximum access restriction? (Prompts: $ = non-root user; # = root user.)

Assuming all features are supported, on a *NIX system, what is the best way to protect an existing $file on an Extended Filesystem (ext#) partition from any changes and set maximum access restriction? (Prompts: $ = non-root user; # = root user.)

  • $ chmod 000 $file && chown root:root $file
  • $ chmod 1744 $file && chown root:root $file
  • # chown root:root $file && chmod 1000 $file && chattr +iu $file
  • # chmod 400 $file && chown root:root $file && chattr +i $file 

 

EXPLANATION

chown root:root $file sets the user and group "root" as the owner of the file. chmod 1000 $file sets the sticky bit to 1, which means that only the owner can delete the file, and the zeroes mean that the owner, group, and world (other), respectively, have no access permissions on the file.
A component of the e2fsprogs package, chattr +iu sets the file to immutable (+i), so even root cannot change it, and sets the file to undeletable (+u) so that it cannot be deleted.
This answer assumes 1) that the user has permissions to set all flags & 2) that the +u flag in chattr is supported by the Linux kernel and the filesystem on which the file is written.
For documentation, see:
https://docs.oracle.com/cd/E19683-01/816-4883/secfile-69/index.html
http://permissions-calculator.org/
Note: for more realistic (real-world) command-line options, one would allow root to read the file with chmod 1400; and since chattr +i sets the file to immutable, it will not be deletable, so chattr +u is unnecessary.
Share:

Popular Posts