IT Questions and Answers :)

Saturday, February 22, 2020

Which of the following are based on public key cryptography?

Which of the following are based on public key cryptography?

  • Hybrid keys
  • Key escrow
  • Digital signatures
  • Diffusion 
Which of the following are based on public key cryptography?

EXPLANATION

Public-key cryptography, or asymmetric cryptography, is a cryptographic system that uses pairs of keys: public keys which may be disseminated widely, and private keys which are known only to the owner. The generation of such keys depends on cryptographic algorithms based on mathematical problems to produce one-way functions. Effective security only requires keeping the private key private; the public key can be openly distributed without compromising security.[1]
In such a system, any person can encrypt a message using the receiver's public key, but that encrypted message can only be decrypted with the receiver's private key.
Robust authentication is also possible. A sender can combine a message with a private key to create a short digital signature on the message. Anyone with the sender's corresponding public key can combine the same message and the supposed digital signature associated with it to verify whether the signature was valid, i.e. made by the owner of the corresponding private key.[2][3]
Public key algorithms are fundamental security ingredients in modern cryptosystems, applications and protocols assuring the confidentiality, authenticity and non-repudiability of electronic communications and data storage. They underpin various Internet standards, such as Transport Layer Security (TLS), S/MIME, PGP, and GPG. Some public key algorithms provide key distribution and secrecy (e.g., Diffie–Hellman key exchange), some provide digital signatures (e.g., Digital Signature Algorithm), and some provide both (e.g., RSA).


Share:

What was the first configuration file to be parsed by MS-DOS during a boot up operation?

What was the first configuration file to be parsed by MS-DOS during a boot up operation?

  • CONFIG.SYS
  • STARTUP.CMD
  • MSDOS.SYS
  • AUTOEXEC.BAT 

EXPLANATION

AUTOEXEC.BAT is a system file that was originally on DOS-type operating systems. It is a plain-text batch file in the root directory of the boot device. The name of the file is an abbreviation of "automatic execution", which describes its function in automatically executing commands on system startup; the filename was coined in response to the 8.3 filename limitations of the FAT file system family.  

AUTOEXEC.BAT is read upon startup by all versions of DOS, including MS-DOS version 7.x as used in Windows 95 and Windows 98. Windows ME only parses environment variables as part of its attempts to reduce legacy dependencies,[1] but this can be worked around.[2]
The filename was also used by Disk Control Program [de] (DCP), an MS-DOS derivative by the former East-German VEB Robotron.[3]
In Korean versions of MS-DOS/PC DOS 4.01 and higher (except for PC DOS 7 and 2000), if the current country code is set to 82 (for Korea) and no /P:filename is given and no default AUTOEXEC.BAT is found, COMMAND.COM will look for a file named KAUTOEXE.BAT instead in order to ensure that the DBCS frontend drivers will be loaded even without properly set up CONFIG.SYS and AUTOEXEC.BAT files.[4]
Under DOS, the file is executed by the primary copy of the command-line processor (typically COMMAND.COM) once the operating system has booted and the CONFIG.SYS file processing has finished. While DOS by itself provides no means to pass batch file parameters to COMMAND.COM for AUTOEXEC.BAT processing, the alternative command-line processor 4DOS supports a 4DOS.INI AutoExecParams directive and //AutoExecParams= startup option to define such parameters.[5] Under Concurrent DOS, Multiuser DOS and REAL/32, three initial parameters will be passed to either the corresponding STARTxxy.BAT (if it exists) or the generic AUTOEXEC.BAT startup file, %1 holds the virtual console number,[6] %2 the 2-digit terminal number (xx) (with 00 being the main console) and %3 the 1-digit session number (y).[7]
Windows NT and its descendants Windows XP and Windows Vista parse AUTOEXEC.BAT when a user logs on. As with Windows ME, anything other than setting environment variables is ignored.[8] Unlike CONFIG.SYS, the commands in AUTOEXEC.BAT can be entered at the interactive command line interpreter. They are just standard commands that the computer operator wants to be executed automatically whenever the computer is started, and can include other batch files.
AUTOEXEC.BAT is most often used to set environment variables such as keyboard, soundcard, printer, and temporary file locations. It is also used to initiate low level system utilities, such as the following:
  • Virus scanners
  • Disk caching software
  • Mouse drivers
  • Keyboard drivers
  • CD drivers
  • Miscellaneous other drivers

 


Share:

Which MS-DOS command allows you to shut down a user remotely?

Which MS-DOS command allows you to shut down a user remotely?

  • shutdown -i
  • @echo on shutdown -i -s
  • shutdown -s
  • shutdown -s -t 
Which MS-DOS command allows you to shut down a user remotely?

EXPLANATION

Enables you to shut down or restart local or remote computers one at a time.
For examples of how to use this command, see Examples.

Syntax

shutdown [/i | /l | /s | /r | /a | /p | /h | /e] [/f] [/m \\<ComputerName>] [/t <XXX>] [/d [p|u:]<XX>:<YY> [/c "comment"]] 

Parameters

Parameter Description
/i Displays the Remote Shutdown Dialog box. The /i option must be the first parameter following the command. If /i is specified, all other options are ignored.
/l Logs off the current user immediately, with no time-out period. You cannot use /l with /m or /t.
/s Shuts down the computer.
/r Restarts the computer after shutdown.
/a Aborts a system shutdown. Effective only during the timeout period. To use /a, you must also use the /m option.
/p Turns off the local computer only (not a remote computer)—with no time-out period or warning. You can use /p only with /d or /f. If your computer does not support power-off functionality, it will shut down when you use /p, but the power to the computer will remain on.
/h Puts the local computer into hibernation, if hibernation is enabled. You can use /h only with /f.
/e Enables you to document the reason for the unexpected shutdown on the target computer.
/f Forces running applications to close without warning users.
Caution: Using the /f option might result in loss of unsaved data.
/m \\<ComputerName> Specifies the target computer. Cannot be used with the /l option.
/t <XXX> Sets the time-out period or delay to XXX seconds before a restart or shutdown. This causes a warning to display on the local console. You can specify 0-600 seconds. If you do not use /t, the time-out period is 30 seconds by default.
/d [p|u:]<XX>:<YY> Lists the reason for the system restart or shutdown. The following are the parameter values:
p Indicates that the restart or shutdown is planned.
u Indicates that the reason is user defined.
Note: If p or u are not specified, the restart or shutdown is unplanned.
XX Specifies the major reason number (positive integer less than 256).
YY Specifies the minor reason number (positive integer less than 65536).
/c "<Comment>" Enables you to comment in detail about the reason for the shutdown. You must first provide a reason by using the /d option. You must enclose comments in quotation marks. You can use a maximum of 511 characters.
/? Displays help at the command prompt, including a list of the major and minor reasons that are defined on your local computer.


Share:

Which is the oldest version of Windows in this list?

Which is the oldest version of Windows in this list?

  • Windows NT 3.1
  • Windows XP
  • Windows ME
  • Windows 98 
Which is the oldest version of Windows in this list?

EXPLANATION

In May 1990, Microsoft released Windows 3.0, a new version of its MS-DOS-based Windows desktop environment. Windows 3.0 sold well, and the resulting shift in Microsoft's marketing strategy eroded their partnership with IBM—who wanted Microsoft to concentrate solely on developing OS/2 as its primary platform as opposed to building their future business around Windows.[20] Users and developers were unsure of whether to adopt Windows or OS/2 due to these uncertainties (a situation magnified by the fact that the operating systems were incompatible with each other at the API level), while Microsoft's resources were also being drained by the simultaneous development of multiple operating systems.[21][22]
In August 1990, as a response to the popularity of Windows 3.0, the NT OS/2 team decided to re-work the operating system to use an extended 32-bit port of the Windows API known as Win32. Win32 maintained the familiar structure of the 16-bit APIs used by Windows, which would allow developers to easily adapt their software for the new platform while maintaining a level of compatibility with existing software for Windows.[23] With the shift to a Windows-like architecture, the operating system's shell was also changed from OS/2's Presentation Manager to Windows' Program Manager.[24][25][26]
Due to these changes, NT was not presented at COMDEX 1990 as was originally planned.[24] Neither the general public nor IBM knew about the transformation of NT OS/2 into Windows NT at the time.[27] Although the companies did agree to a revised partnership where IBM and Microsoft would alternate developing major versions of OS/2 instead of collaborating on each version,[28] IBM eventually learned of Microsoft's Windows NT plans in January 1991, and immediately ended the OS/2 partnership. IBM would solely develop OS/2 2.0 (as was planned under the amended version) and all future versions, without any further involvement from Microsoft.[23][29]
In October 1991, Windows NT received its first public demonstration at COMDEX. In an effort to ensure software taking advantage of Windows NT was available upon its release (scheduled for late-1992), Microsoft also distributed a 32-bit software development kit to selected developers in attendance.[30][31] The demonstration was positively received; PC Magazine called Windows NT "the modern reinvention of the operating system", but at the same time claimed that it was unlikely that the promised backward compatibility would be kept for the final release.[32][33] In March 1992, Microsoft also released Win32s, which would allow Windows 3.1 to have partial compatibility with Windows NT programs for the purposes of developing software optimized for the platform.[34]
At Microsoft's Win32 Professional Developers Conference in June 1992, Windows NT was demonstrated running on x86 and MIPS processors, while a beta version of Windows NT and an updated development kit were also made available.[35] Concurrently, Microsoft announced a new version of its SQL Server product for Windows NT; Unix vendors feared that the software could be a killer app that would affect the market share of Unix systems.[36][37] Concerns were also raised over NT's memory usage; while most computers of the era shipped with 4 megabytes of RAM, 16 MB was recommended for NTs. Due to the high cost of RAM at the time, critics thought that its high system requirements could affect the sales and adoption of Windows NT. Steps were taken to reduce its memory usage through methods such as paging.[38][39][40][41]
Microsoft began releasing public beta builds of NT in October 1992, and a month later at COMDEX, a presentation focusing on third-party software for Windows NT was held.[42][43][44] The final pre-release version of NT was released in March 1993, alongside the unveiling of the server version, Windows NT with LAN Manager. Although its stability and performance had improved, there were still fears that the OS could be released in an unfinished state or delayed further into 1993.[45][46]

 

 


Share:

On an Apache webserver, what is the name of the file used to configure access to the web site?

On an Apache webserver, what is the name of the file used to configure access to the web site?

  • .htaccess
  • htaccess.txt
  • htaccess.cfg
  • htaccess
On an Apache webserver, what is the name of the file used to configure access to the web site?

EXPLANATION

An .htaccess file also known as an hypertext access file is a directory-level configuration file supported by several web servers, used for configuration of site-access issues, such as URL redirection, URL shortening and Access-security control.
An .htaccess file provides various options for website owners to control the server environment variables and other parameters to enhance functionality of their websites. It is placed in the directories and sub-directories of the Apache document root. When you place an .htaccess file in the apache document root, the .htaccess file is detected and executed by the Apache Web Server.
These .htaccess files can be used to alter the configuration of the Apache Web Server to enable and disable additional functionality and features that the Apache Web Server software has to offer. When you are developing a PHP website and working with PHP and Apache, then you can use an .htaccess file for directory level configuration of Apache web server.
You should only use .htaccess files when you don't have root access to the main Apache server configuration file. An .htaccess file provides many features Some of these features include basic redirects, locking outside access to particular files, or more advanced functions such as content password protection or preventing image hotlinking.
However, use of .htaccess files should be avoided when possible. There are two main reasons to avoid the use of .htaccess files.
The first of these is server performance. When AllowOverride is set to allow the use of .htaccess files, httpd will look in every directory for .htaccess files. Thus, permitting .htaccess files causes a performance issue, whether or not you actually even use them! Also, the .htaccess file is loaded every time a document is requested.
Share:

Popular Posts