Basic Requirements for MySQL Installation
The following section presents the important steps that has to be considered for installing MySQL(Dev.mysql.com, 2018).
The basic requirements for MySQL installation that has to be considered are discussed in this section. Any operating system will have to consider the following general requirements(Dev.mysql.com, 2018):
- A remote or local MySQL server connection is designed in the MySQL Workbench, so it doesn’t require MySQL server. On the other hand, the data modeling don’t need the connection of MySQL server connection. However, certain features procure the benefits of MySQL server’s features along with its recent versions.
- In MySQL Workbench’s home page, if MySQL Connection is opened, it opens new connection tab. These tabs need a couple of MySQL connections for performing the basic tasks like, schema discovery and SQL execution. On the other hand, even to perform tasks related to management like Server Status needs a couple of extra MySQL connections.
The following requirements are necessary for the Linux operating system(Dev.mysql.com, 2018):
- The respective packages have the Linux requirements embedded in the packages. The packages can be installed by using the platform specific tool like yum or apt.
- The “Save password in keychain” functionality requires gnome-keyring forpasswordstorage. By default it is not possible to start the gnome-keyring daemon on the KDE systems.
- For the feature of MySQL server administration,sudo privileges are necessary for executing various commands in Linux and macOS. Some of the commands which the sudo usersshould execute are listed below:
- Moreover, users of sudoshould ensure the variable of HOME environment while execution ofsystem commands. It refers to including,/etc/sudoers:
For Windows
The following are the least requirements that are required for Windows operating system to install MySQL(Dev.mysql.com, 2018):
- Microsoft .NET Framework 4.5.2
- Visual C++ 2015
The below listed content represent the Command-line options that are present inMySQL Workbench(Dev.mysql.com, 2018):
- –log-level level:The verbosity levels are controlled by using this option, to log the output from the Workbench.
As the verbosity levels increase, the level’s valid values include(Dev.mysql.com, 2018):
- error
- warning
- info
- debug1
- debug2
- debug3
The below table represents some of the log files’ located that is generated.
Table: MySQL Workbench generated log files’ default location
- –open file: It helps to open the provided file. It is suggested to use certain specific types like –script or –model.
- –migration: Migration Wizard tab can be opened.
- –admin instance: The administration tab can be opened, for the named MySQL instance.
- –log-to-stderr: It can help to log to stderr.
- –upgrade-mysql-dbs: Migration Wizard tab can be opened.
- –version: It displays the version number of MySQL Workbench and exits.
- –verbose, -v: It enables the diagnostics output.
- –query [connection|connection_string]:
- Connection_string: It helps to create connection depending on the entered connection string. The string has the following form, [email protected]$HOST:$PORT.
- Connection: Named connection can be opened.
- Empty: It opens a query tab and connection is prompted.
- –script script: In –query parameter it is used for opening the provided SQL file.
- –model modelfile: Provided EER model file can be opened.
- –run-script file: From a filethe provided Python code is executed.
- –run code: For GRT shell, it executes the provided code with the help of default language.
- –run-python script: The provided Python code is executed.
- –quit-when-done: When –script or –run completes, it quits the MySQL Workbench.
For Windows operating system, installation of MySQL Workbench is possible with MySQL Installer. Every single MySQL product will get installed and updated with this installer(MySQL Tutorial, 2018).
Windows-Least Prerequisites
Download the following(MySQL and Workbench installation and use guide, 2010):
- First, Microsoft .NET Framework 4.5.2
- Then, Visual C++ 2015
- Finally download, Microsoft Windows 7.
At the time of executing MySQL Installer, MySQL Workbench can be selected as a product to install. By default his product is selected and it ensures to execute the standalone Installer Package.
Installation with the help of
- Right click on MSI file for installing MySQL Workbench, then from the pop-up menu choose the option Install item, or else double-click on the file.
- For having all the MySQL Workbench features select the option “Complete”, in the Setup Type window. However, the user can even select Custom installation option too (Download.nust.na, 2018).
- Finally, C:%PROGRAMFILES%MySQLMySQL Workbench 6.3 edition_type, is the place where installation of MySQL Workbench is completed. Here, the default directory is referred as %PROGRAMFILES%, which on most of the systems look like “C:Program Files.”
On Windows operating system, MySQL Workbench can be launched by selecting the following(Docs.oracle.com, 2018):
StartàProgramsàMySQLàMySQL Workbench.exe file
It can even be done using the command line option as follows:
The above mentioned figure illustrates the output.
All the options are self-explanatory except for displaying the version number of MySQL Workbench i.e., use -versionoption and the option-swrenderingmust be selected in case the video card fails in supporting OpenGL 1.5.
However, MySQL Notifier could be utilized for starting the MySQL Workbench, from the Notifier context menu.
MySQL Workbench’s uninstallation relies on how it was installed i.e., if installer package was used for installing it, then it cannot be removed using command line. However only certain components can be removed. If the MySQL Workbench directory is removed manually, it doesn’t benefit. Therefore, go to Control PanelàAdd or Remove ProgramsàMySQL Workbench and right click to get the “Remove” option.
If MySQL Installer is used for installing MySQL Workbench, then remove it by following the below step,
For Windows operating system, go to MySQL Installerà select Remove MySQL Productsà select MySQL Workbench.
However, though after MySQL Workbench is uninstalled, the Workbench configuration directory will not be removed. The directory contains configuration settings MySQL connections,SQL snippets and history, cache files, logs, custom modules etc. %AppData% is the directory, where all these files are kept(Dev.mysql.com, 2018).
Necessary Requirements for Linux OS to Install MySQL
The objective of this component revolves around establishing TSF where in a systematic manner, it is tested against the functional specification. The testing can be accomplished by following a corresponding developer analysis, where the testes related to security functions are also considered. However, it is necessary that the analysis provide enough information about the function’s implementation to the evaluator along with the tests and security functions’ correspondence. Because, the extra evaluator tests can be planned based on this information. The developer must take care that all the functions present in functional specifications are tested and for the functions the test should not be intensive (Pagenotes.com, 2018).
The dependencies are listed below:
- 1 Informal functional specification
- 1 Functional testing
Action Elements of the Developer
The action elements of the developer includes the following:
ATE_COV.2.1D: Thetest coverageanalysis will be provided by thedeveloper.
Evidence Element’s Content and Presentation
ATE_COV.2.1C: Like mentioned in thefunctional specification, the determination of correspondence among the detectedtest in the test documentationand TSF,is demonstrated by the test coverageanalysis.
ATE_COV.2.2C: Like mentioned in thefunctional specification, the correspondence between the TSF is demonstrated by the test coverage analysis. Then, the identification test is completed in the test documentations.
Action Elements of the Evaluator
ATE_COV.2.1E: Whether the provided information meets all requirements or not will be confirmed by the evaluator, as an evidence for content and presentation.
Dependencies
The dependencies include the following:
ADV_RCR.1 Informal correspondence demonstration
Action Elements of the Developer
The action elements of the developer includes the following(Pagenotes.com, 2018):
ADV_FSP.1.1D: Functional specifications will be provided by the developer.
Evidence Element’s Content and Presentation
ADV_FSP.1.1C: With the help of the informal style, the TSF and its external interfaces are described by the functional specification.
ADV_FSP.1.2C: The internal reliability will be developed by the functional specification.
ADV_FSP.1.3C: Information likeexceptions and error messages, purpose, method of use foreach of the external TSF interfaces and details of impactwill be described by the functional specification.
ADV_FSP.1.4C: The TSF will be represented completely by the functional specification.
Action Elements of the Evaluator
ADV_FSP.1.1E: Whether the provided information meets all requirements for the evidence for content and presentation will be confirmed by the evaluator.
ADV_FSP.1.2E: Whether the provided information meets all requirements or not will be confirmed by the evaluator, as an evidence for content and presentation.
Dependencies
It has no dependencies.
Action Elements of the Developer
The action elements of the developer includes the (Pagenotes.com, 2018):
ADV_RCR.1.1D: All the provided details of analysis which shows the correspondence between TSF’seach adjacent pair, will be represented by the developer.
Requirements for Windows OS to Install MySQL
ADV_RCR.1.1C: All the TSF’sadjacent pairsand its representationswill be demonstrated by the analysis. It representsthe applicable security functionality which has greater abstract TSF representation and considers it as correctand advanced, when it is compared with the less abstract TSF representation.
ADV_RCR.1.1E: Whether the provided information meets all requirements or not will be confirmed by the evaluator, as an evidence for content and presentation.
Dependencies
It has no dependencies.
Action Elements of the Developer
The action elements of the developer includes the following:
ATE_FUN.1.1D: The results are documented after the developer tests the TSF.
ATE_FUN.1.2D: Test documentation will be provided by the developer.
Content and presentation of evidence elements:
ATE_FUN.1.1C: Test plans, test’s procedure and descriptions, actual and expected test results all are part of the test documentation.
ATE_FUN.1.2C: The security functions are identified by the test plans and it helps to define the test goals.
ATE_FUN.1.3C: The description of test procedure helps to recognize the required tests that must be performed. For every security function, this ensures to clearly explain the testing scenarios. On the other hand, on the other test results, these scenarios might contain dependencies of any order.
ATE_FUN.1.4C: Based on the accomplished test execution, the expected test results could display the awaited outputs.
ATE_FUN.1.5C: According to the developer execution’s test results, the tests could prove the behavior of security function i.e., the functions have behaved exactly like mentioned.
Action Elements of the Evaluator
The following refers to the action elements of the evaluator:
ATE_FUN.1.1E:Whether the provided information meets all requirements are met or not must be confirmed by the evaluator, as an evidence for content and presentation.
Similar information is provided in the chapter CEMfor EAL3 about ATE_COV.2-3 and ATE_DPT.1-3. Functional specification related guidance and high level design is referenced by CEM section 7.9.1.3.This suggests that ATE_COV.2 and ATE_DPT.1 are a segment of Security Target that might not be true. Hence, the provided guidance can mislead if only anyone assurance component is present in Security Target. On the other hand, there are chances of confusion due to similar wok in both the work units. However, section 7.9.1.3 fails to address the difference amongATE_DPT.1 and ATE_COV.2 i.e., ATE_COV.2 has completeness requirements and it is not there in ATE_DPT.1. Similar problem is observed in the considered chapter for EAL4, both CEM section 8.9.1.3, is referenced (Commoncriteriaportal.org, 2018).
It is interpreted that, the evaluator is educated that ATE_COV and ATE_DPT are same, however it must be considered based on work underway.
Command-line Options in MySQL Workbench
The specific change represented for CEM, is described clearly in this section.
The CEM paragraph 1122 is rewritten as follows(Commoncriteriaportal.org, 2018):
“Guidance on this work units, according to the functional specification concern could be attained in the following ways:
In the Application notes,by checking the adequacy of tests the Section 7.9.1.3 states in CEM paragraph 1130 that, “Guidance on this work unit, as it pertains to the high-level design, can be found in:
In the Application notes, by checking the adequacy of tests the Section 7.9.1.3 states in CEM paragraph 1581 that, “Guidance on this work unit, as it pertains to the functional specification, can be found in:
In the Application notes, by checking the adequacy of teststhe Section 8.9.1.3 states in CEM paragraph 1589 that, “Guidance on this work unit, as it pertains to the high-level design, can be found in:
In the Application notes Section 8.9.1.3, checking the adequacy of tests.”
The functional specifications along with high-level design should be addressed in CEM sections 7.9.1.3 and 8.9.1.3,in regards to checking the adequacy of tests. Both the EALs, of EAL3 or EAL4 have assurance requirements, which is currently addressedin CEM’s structure in sections 7.9.1.3 and 8.9.1.3. Therefore, ATE_DPT.1 and ATE_COV.2 are available in both EAL3 and EAL4. Thus, it is not required that CEM sections 7.9.1.3 and 8.9.1.3 must disclose the differences amongATE_DPT.1 and ATE_COV.2.Thus, if the evaluator fails to correspond to sections 7.9.1.3 and 8.9.1.3 in an appropriate context, then he can try all the efforts of performing the required evaluation for work unit ATE_DPT.1-3, while ATE_COV.2-3 is being performed(Commoncriteriaportal.org, 2018).
The objective is represented in the below section.
The TSF is categorized into small parts known as subsystems. This subsystems provides high-level description about TSF’s internal working. The process of testing is undertaken to identify the errors at the subsystem levels. This helps to reassure that the TSF’s TSF subsystems are realized correctly or not.The developer must take care of the activities testing the designs that come underhigh-level category in TSF, in the subsystems. (Pagenotes.com, 2018).
The dependencies are listed below:
- 1 Descriptive high-level design
- 1 Functional testing
ATE_DPT.1.1D: Testing’s depth is analyzed by the developer.
ATE_DPT.1.1C: For evaluating sufficient demonstration of test documentation identified in the tests, the depth analysis will help TSF to operate accordingly with its design which is of high-level.
ATE_DPT.1.1E: Whether the provided information meets all requirements or not will be confirmed by the evaluator, as an evidence for content and presentation.
Verbosity Levels in MySQL Workbench
ATE_DPT.1 depends on design and testing as shown below:
The design depends on the following dependencies:
- 1 Informal functional specification
- 1 Informal correspondence demonstration
Action Elements of the Developer
ADV_HLD.1.1D: TSF’s high-level design will be provided by the developer.
Evidence Element’s Content and Presentation
ADV_HLD.1.1C: High-level design’s presentation will be informal.
ADV_HLD.1.2C: The internal reliability will be developed by the high-level design.
ADV_HLD.1.3C: TSF’sstructure in the subsystem will be defined by the high-level design.
ADV_HLD.1.4C: TSF subsystem’sprovidedsecurity functionality will be described by the high-level design.
ADV_HLD.1.5C: If any core hardware, and then firmware/ software are needed by TSF along with functions’ presentation which is facilitated by the supporting protection mechanisms,will beidentified by the high-level design.
ADV_HLD.1.6C: TSF subsystem’s all the interfaces will be identified by the high-level design.
ADV_HLD.1.7C: TSF subsystem’s interfaces that are available externally will be identified by the high-level design.
Action Elements of the Evaluator
ADV_HLD.1.1E: Whether the provided information meets all requirements or not will be confirmed by the evaluator, as an evidence for content and presentation.
ADV_HLD.1.2E: Whetherthe high-level design is correct and whether as per the functional requirements TOE security have complete instantiation or not,will be determined by the evaluator.
Dependencies
It has no dependencies.
Action Elements of the Developer
The action elements of the developer includes the following:
ATE_FUN.1.1D: The results are documented after the developer tests the TSF.
ATE_FUN.1.2D: Test documentation will be provided by the developer.
Content and Presentation of Evidence Elements
ATE_FUN.1.1C: Test plans, test’s procedure and descriptions, actual and expected test results all are part of the test documentation.
ATE_FUN.1.2C: The security functions are identified by the test plans and it helps to define the test goals.
ATE_FUN.1.3C: The description of test procedure helps to recognize the required tests that must be performed. For every security function, this ensures to clearly explain the testing scenarios. On the other hand, on the other test results, these scenarios might contain dependencies of any order.
ATE_FUN.1.4C: Based on the accomplished test execution, the expected test results could display the awaited outputs.
ATE_FUN.1.5C: According to the developer execution’s test results, the tests could prove the behavior of security function i.e., the functions have behaved exactly like mentioned.
Action Elements of the Evaluator
The following refers to the action elements of the evaluator:
ATE_FUN.1.1E:Whether the provided information meets all requirements or not is confirmed by the evaluator, as an evidence for content and presentation.
The following section represents the objectives(Pagenotes.com, 2018).
The objective refers to the developer for demonstrating that, each security function behaves like mentioned. It is necessary for the developer to undergo testing along with facilitating the test documentation.
Log Files Generated by MySQL Workbench
Dependencies
It has no dependencies.
Action Elements of the Developer
The action elements of the developer includes the following:
ATE_FUN.1.1D: The results are documented after the developer tests the TSF.
ATE_FUN.1.2D: Test documentation will be provided by the developer.
Content and Presentation of Evidence Elements
ATE_FUN.1.1C: Test plans, test’s procedure and descriptions, actual and expected test results all are part of the test documentation.
ATE_FUN.1.2C: The security functions are identified by the test plans and it helps to define the test goals.
ATE_FUN.1.3C: The description of test procedure helps to recognize the required tests that must be performed. For every security function, this ensures to clearly explain the testing scenarios. On the other hand, on the other test results, these scenarios might contain dependencies of any order.
ATE_FUN.1.4C: Based on the accomplished test execution, the expected test results could display the awaited outputs.
ATE_FUN.1.5C: According to the developer execution’s test results, the tests could prove the behavior of security function i.e., the functions hve behaved exactly like mentioned.
Action Elements of the Evaluator
The following refers to the action elements of the evaluator:
ATE_FUN.1.1E:Whether the provided information meets all requirements or not is confirmed by the evaluator, as an evidence for content and presentation.
The TOE Security Assurance Requirements include ATE_FUN.1 Functional Testing. (Security Target for Oracle Database 11g Release 1 (11.1.0) with Oracle Database Vault, 2009).
Query – 1
Here listing the supplier details and sorted the suburb in ascending order. It is shown in below.
Query – 2
Here listing the movie items and their suppliers name, email, phone number and suburb. It is shown in below.
Query – 3
Here listing the Actor details. It is shown below.
Query – 4
Here listing the genre details. It is shown below.
Query – 5
Here listing the Inventory items details. It is shown below.
Query – 6
Here listing the genres details that have no inventory item. It is shown below.
Query – 7
Here delete the all the customers from the postcode 3353. It is shown in below.
Query – 8
Here changes the inventory item name form Wookie figure to Wookie figure-live size. It is shown in below.
Query – 9
Here list the movie titles with their cast and director. It is shown in below (Pallaw, 2010).
Query – 10
Here insert the movie title Solaris. It is shown in below.
References
Commoncriteriaportal.org. (2018). Offline RI Listing. [online] Available at: https://www.commoncriteriaportal.org/files/finalinterpretations/001%20CC%20v2.1/final74.html [Accessed 28 Apr. 2018].
Dev.mysql.com. (2018). MySQL :: MySQL Workbench Manual :: 2.3.1 Installing. [online] Available at: https://dev.mysql.com/doc/workbench/en/wb-installing-windows.html [Accessed 28 Apr. 2018].
Docs.oracle.com. (2018). Chapter 3. Installing and Launching MySQL Workbench. [online] Available at: https://docs.oracle.com/cd/E19078-01/mysql/mysql-workbench/wb-installing.html [Accessed 28 Apr. 2018].
Download.nust.na. (2018). MySQL :: MySQL Workbench :: 3.3.1 Installing MySQL Workbench on Windows. [online] Available at: https://download.nust.na/pub6/mysql/doc/workbench/en/wb-installing-windows.html [Accessed 28 Apr. 2018].
MySQL and Workbench installation and use guide. (2010). Information Systems, Aarhus University. [online] Available at: https://www.cs.au.dk/~ira/MySQLGuide.pdf [Accessed 28 Apr. 2018].
MySQL Tutorial. (2018). Install MySQL on Windows Using MySQL Installer. [online] Available at: https://www.mysqltutorial.org/install-mysql/ [Accessed 28 Apr. 2018].
Pagenotes.com. (2018). ATE_COV.2 Analysis of coverage. [online] Available at: https://pagenotes.com/writings/ccToolbox6f/CCManual/PART3/Part313-1-2.htm [Accessed 28 Apr. 2018].
Security Target for Oracle Database 11g Release 1 (11.1.0) with Oracle Database Vault. (2009). Common Criteria. [online] Available at: https://www.oracle.com/technetwork/topics/security/0588-dbv-st-11gr1-v6-final-131531.pdf [Accessed 28 Apr. 2018].
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
