RU2815924C1 - Method of installing programs which does not require multiple requests for permission, electronic device and computer-readable data medium - Google Patents

Abstract

FIELD: means of installing programs.

SUBSTANCE: executing the first command after launching the first launching program without administrator rights, wherein the first command is configured to run the second launching program with administrator rights. At least one installation module is launched by means of the second command after launching the second launching program, besides, the second command is configured to execute launching programs with administrator rights. Interface of the first launching program is hidden after launching the second launching program, and/or the interface of the second launching program is hidden after launching the installation module.

EFFECT: performing the process of installing different program modules using only a single request for permission.

9 cl, 8 dwg

Description

Field of technology

The present invention relates to the field of software installation technology and, in particular, to a software installation method that does not require multiple permission requests, an electronic device, and a computer-readable storage medium.

Prerequisites for creating the invention

On some operating systems, when different types of feature modules need to be installed in the same software installation process, a system window may need to pop up multiple times to prompt the user for login passwords, which increases operational complexity and reduces the quality of the user experience.

The essence of the invention

The purpose of the present invention is to eliminate the defects of the prior art in that installation of different types of function modules requires multiple permission requests.

According to a first aspect of the present invention, there is provided a method for installing programs that does not require multiple permission requests, which includes: executing a first command after running a first launcher without administrator rights, the first command being used to launch a second launcher with administrator rights; and launching the at least one installation module by a second command after launching the second launcher, the second command being configured to execute the launchers with administrator rights.

Optionally, the installation module includes at least one function selected from installing imaging device drivers, setting up a wireless network of the imaging device, and performing adding the imaging device.

Optionally, the installation method is used on the MacOS system.

Optionally, the first and second commands are API (Application Programming Interface) commands or scripts in the standard library.

Optionally, the first launcher's interface is hidden after the second launcher is launched; and/or the interface of the second launcher is hidden after the installation module is launched.

According to a second aspect of the present invention, there is provided a method for installing programs that does not require multiple permission requests, which includes: repeatedly executing a third command until the installation is completed after running the first launching program without administrator rights, the third command being configured to execute the install command in a file by specified path with administrator rights; and, each time before, the first writing program will execute the third command, clearing the file and writing the installation command corresponding to the next module to be installed to the file by the first writing program.

Optionally, the installation module includes at least one function selected from installing imaging apparatus drivers, configuring a wireless network of the imaging apparatus, and performing adding an imaging apparatus.

Optionally, the installation method is used for MacOS system.

Optionally, the third command is the API or script commands in the standard library.

According to a third aspect of the present invention, there is provided an electronic device that includes:

memory adapted to store a computer program; and a processor communicatably coupled to the memory, and when executing a computer program, the processor is configured to execute a setting method that does not require multiple permission requests according to the first and second aspects of the present invention.

According to a fourth aspect of the present invention, there is provided a computer-readable storage medium containing a computer program that, when executed, causes a processor to execute an installation method that does not require multiple permission requests according to the first or second aspects of the present invention.

The technical result of the present invention is that only a one-time permission request is required to carry out the process of installing different modules.

Other features and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments of the present invention with reference to the accompanying drawings.

Brief description of graphic materials

The accompanying drawings, which are included in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

Fig. 1 is a diagram showing a pop-up window when

permission is requested;

FIG. 2 is a logic block diagram showing an embodiment

implementation of the present invention;

FIG. 3 is a schematic diagram showing an activity monitor interface after launching a second launcher according to an embodiment of the present invention; FIG.

FIG. 4 is a schematic diagram showing signal interconnection between modules according to an embodiment of the present invention; FIG.

FIG. 5 is a logic block diagram of an exemplary application of an embodiment of the present invention; FIG.

FIG. 6 is a logic block diagram showing another

an embodiment of the present invention;

FIG. 7 is a schematic diagram showing signal interconnection between modules according to another embodiment of the invention; FIG.

FIG. 8 is a logic block diagram of an illustrative application of another embodiment of the invention.

Detailed Description of Embodiments

Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that the relative arrangement of elements and steps, numerical expressions and meanings set forth in these embodiments do not limit the scope of the present invention unless otherwise stated.

The following description of illustrative embodiments is for purposes of illustration and explanation only, and in no way limits the application or use of the present invention.

Technologies, methods and devices known to those skilled in the art may not be discussed in detail, however, when appropriate, technologies, methods and devices should be considered part of the present description.

In all examples given and discussed here, any specific values are to be interpreted as illustrative and should not be construed as limitations. Therefore, other examples of illustrative embodiments may have different meanings.

It should be noted that similar signs and letters indicate similar elements that will be presented in the following figures, therefore, after defining an element in one figure, further definition of the element in subsequent figures is not required.

The purpose of embodiments of the present invention is to provide a method for installing programs that does not require the user to repeatedly enter a password to log into the system. For example, when using some typical Unix operating systems (such as Ubuntu or MacOS), when an application program is installed, a window will pop up if the application program needs to modify system files. The pop-up window interface is shown in Figure 1. When the program being installed has several functional modules that need to modify system files, then before installing each module in the system, an interactive interface will pop up asking the user to enter a password; otherwise the installation cannot continue. For example, when installing a printer utility, the driver module, network module, and add device module may all prompt

permissions from the system. When this situation occurs, multiple pop-up windows will appear sequentially, thereby reducing the quality of the user experience.

There are several ways to skip password entry; for example, developer.apple.com provides a way to write the username and password in text form into a command for execution, or to write the username and password into a script for reading. However, these methods undoubtedly pose a security risk; Therefore, to solve the above problem, it is necessary to resort to a safer and more convenient method.

To solve the above problem, a detailed description of two embodiments is provided below.

<Embodiment I>

As shown in FIG. 1, this embodiment, which provides a method for installing programs without requiring multiple permission requests, includes:

Step S101: The first command is executed after startup

the first program to launch without administrator rights.

The first launcher may be a program for receiving user interaction. For example, the user can launch the first launcher by clicking on the first launcher icon, by entering an operating command at the command line, or by using a hotkey. The first launcher can be considered as an interface for the user to carry out the installation process. The first program that launches does not itself contain installation files.

The first command is configured to run the second launcher with administrator rights. For example, on MacOS, the first command might use the function provided in Apple's standard library to obtain permission, and the input parameter to that function might be the path to where the second launcher is located. Given that among the API functions used to run programs with administrative privileges or execute commands, there are some functions that were once widely used but were then officially designated as deprecated functions as the library was updated, specific function names are not provided in this application to prevent users from inadvertently selecting deprecated features. Those skilled in the art can use keywords such as permission to search technical manuals such as developer guides and select features currently recommended for actual use, etc.

Step S102: The second command starts the at least one installation module after starting the second launcher.

Because the first launcher is running with administrator rights this time, the second launcher may not prompt for permissions multiple times when using commands with root privilege again. A diagram of one example embodiment is shown in FIG. 3, where a process with a process ID (PID) of 59439 is the first launcher. As you can see, the first launcher runs without administrator rights (the username is the same as a normal username), and the process with PID 44007 is the second launcher. As you can see, the second launcher has root privileges after running it with the first command, and the second launcher always has root privileges throughout the installation process, meaning the second launcher does not need to enter a password multiple times, no matter how many commands with root privilege will be entered subsequently. For different types of installation modules, specific execution instructions may differ. For example, the names of the installation modules or the modification operations performed may differ. In some embodiments, when the number of installation modules is at least 2, it is satisfied that each installation module needs to request permission, and the permission that each installation module needs to request is different from others.

The second command is configured to execute launch programs with administrator rights. For example, on MacOS, startup instructions can be executed through an API function provided in the Apple standard library or shell script commands. Likewise, those skilled in the art can use appropriate keywords to search the library to select the most recommended functions or scripts to use, and specific function names are not provided herein.

In some embodiments, the differences between the first and second commands may be that the first command's input parameters are executable files (eg, a second launcher), while the second command may be a specific add, delete, change, or check operation.

FIG. 4 is a schematic diagram of a signaling relationship between modules according to an exemplary embodiment. As can be seen, the first launcher launches the second launcher via the first command, and the second launcher launches several installation modules via the second command.

A block diagram of an exemplary application according to this embodiment is shown in FIG. 5. In step S501, the first startup program is started. At this time, the first command is executed immediately. In step S502, the system causes the username/password input window to pop up for the user to input. In step S503, the second startup program is started. In step S504, command 1 is executed with root privilege (ie, the operator in the second command). In subsequent steps S505 to S507, several commands with root privilege are executed by the second launcher. During the processes of steps S504 to S507, the window shown in FIG. 1 may not pop up, that is, in this exemplary embodiment, only a one-time permission request is required throughout the entire process.

It should be noted that this embodiment is not easily constructed based on currently available technical guidance or application specifications for command statements. On the contrary, technical manuals may provide completely opposite instructions. The page "Technical Note TN2065 do shell script in AppleScript" on developer.apple.com mentions that multiple permission requests are not required or provide any additional benefit, and developers are advised to avoid this practice. To some extent, this page may only serve to provide a general understanding to those skilled in the art; that is, you only need to select one of these commands to request permission, and using them together will have the same result without any additional effects. Consequently, there is no incentive for those skilled in the art to reuse commands. The present application has discovered that the combination of the first command and the second command can make the second running program always have root privileges without having to repeatedly request permission. The first and second launchers and the first and second commands are rationally designed herein such that the second launcher, when launched, has root privileges so that when running multiple installation packages, the second launcher will not be required to enter a password, which greatly simplifies the workflow.

In some embodiments, the installation module in step S102 has at least one function selected from performing installation of imaging device drivers, setting up the wireless network of the imaging device, and performing adding of the imaging device. If the installation module includes at least two functions, then using the method according to the present disclosure, it is possible to install drivers of an imaging device (eg, a printer) in one click, without the need for multiple permission requests, and at least two operations from installing drivers , network settings and device additions can be made, which provides convenience for the user to quickly use the imaging device from a computer.

In some embodiments, in step S102, the second command starts the at least one installer after starting the second launcher, which corresponds to, inter alia, starting the installation of the network setup program, then starting the installation of the imaging device drivers, and then The installation begins to add the imaging device to the computer's operating system. The sequence of these three installation processes is not limited. In this regard, according to step 102, it is no longer necessary to enter a password when running multiple installation modules that you want to run, or running installation packages with root privilege, which greatly simplifies the workflow and ensures the effect of completing all installation operations after entering the password once in one cry.

Moreover, in order to make the installation interface simple and clear, according to this embodiment, the interface of the first launcher is hidden after the second launcher is launched and/or the interface of the second launcher is hidden after the installation module is launched. Since the first launcher and second launcher do not have a standard installation interface and only serve as command functions, if the first and second launchers are always displayed, they may interfere with the user's ability to observe the installation process. Therefore, the first launching program can be hidden so that only one program is displayed at a time in the system interface.

<Embodiment II>

According to another embodiment, a method for installing programs is provided that does not require multiple permission requests. As shown in FIG. 6, this method includes steps S201 and S202.

In step S201, the third command is executed repeatedly until the installation is completed after the first startup program is launched without administrator rights. The first launcher may be a program for receiving user interaction. For example, the user may launch the first launcher by clicking on the first launcher icon, by entering an operating instruction at the command line, or by using a hotkey.

The third command is configured to execute installation commands on files in a predefined path with administrative rights, and is also configured to allow the third command process to run with administrative rights.

For example, on MacOS, startup instructions can be executed through the API provided in the Apple standard library or shell script commands. Likewise, those skilled in the art can use appropriate keywords to search the library to select the most recommended functions or scripts, and specific function names are not limited herein.

The third command differs from the first and second commands in that the input parameter of the third command is a path, and it is configured to execute a script along that path. In this embodiment, once permission is granted, the password entry window may not pop up repeatedly to execute the same command multiple times. Based on this, in this embodiment, the first launcher repeatedly executes the third command to avoid multiple requests for permissions. Along with this, in this embodiment, it is also required to implement the process of installing different installation modules using the same command, and this process can be implemented by step S202.

In step S202, whenever before the first launcher executes the third command, the function specified in the first launcher may clear the file and write an installation command corresponding to the next module to be installed into the file. For example, the file may be empty in its original state. Before the third command is executed for the first time, the third command writes to an empty file a command to run the first installation module. After the installation of the first installer is complete, the first writer cleans up the file and then writes a command to run the second installer. After the installation of the second installer is complete, the first writer cleans up the file and then writes a command to run the third installer. This process continues until all installation modules have been launched.

That is, the idea of this embodiment is to repeatedly execute the same script command so that the password input window does not have to pop up multiple times. In addition, in order to actually achieve the effect of performing different operations, another writing module is used to constantly modify the contents of the script in order to achieve this goal.

A schematic diagram of the signal relationship between modules according to this embodiment is shown in FIG. 7. As you can see, the first launcher executes several installation modules by changing the script file over and over again.

A logic block diagram of an exemplary application of this embodiment is shown in FIG. 8. In step S601, the first startup program is started, and then the third instruction is immediately executed. In step S602, an empty script file is created. In step S603, command 1 is written to the script file. In step S604, the script file is executed with root privilege. In step S605, the username/password input window is popped up, and after the user inputs, command 1 is executed. In step S606, the script file is cleared, and command 2 is written to the script file. At step S607 of the file, the script is executed with root privilege. This process is repeated until the writing process of step S608 and the execution process of step S609 corresponding to the last command are completed. In steps S606 to S609, the window shown in FIG. 1 may not pop up again, that is, only a one-time permission request is required throughout the entire process of this embodiment.

It should be noted that this embodiment is not easily constructed based on currently available technical guidance or application specifications for command statements. The technical use cases provided on developer.apple.com do not provide any technical explanation of how to use operator properties to allow multiple programs with different names to run without asking for permission multiple times.

In some embodiments, this application also provides an electronic device that includes one or more processors, a memory, and one or more computer programs stored in the memory. One or more computer programs contain instructions that, when executed by an electronic device, cause the electronic device to perform some or all of the steps in the method of the present disclosure.

Some embodiments of the present application also provide a computer-readable storage medium that can store a program that, when executed, can perform some or all of the steps in the method of the present disclosure. As the above-mentioned computer-readable storage medium, a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), etc. can be used.

In some embodiments of the present application, a computer program product is also provided that contains executable instructions that, when executed on a computer, cause the computer to perform some or all of the steps in the method of the present disclosure.

In embodiments of the present application, “at least one” indicates one or more, and “several” indicates two or more. The expression “and/or” describes a relationship of association, indicating that there can be three types of relationships. For example, A and/or B can express the following situations: A exists separately, A and B exist simultaneously, B exists separately, while A and B can be either singular or plural. The "/" symbol usually indicates that the objects it links have an "or" relationship. Expressions such as “at least one of the following” correspond to any combination of elements, including any combination of single elements or multiple elements. For example, at least one of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c may be single or multiple.

Although certain specific embodiments of the present invention have been described in detail by way of examples, those skilled in the art should understand that the above examples are intended for illustration and understanding only and not to limit the scope of the present invention. Those skilled in the art will understand that changes may be made to the above embodiments without departing from the scope and spirit of the present invention. The scope of the present invention is defined by the appended claims.

Claims (17)

1. A method of installing a program, containing stages in which: executing the first command after launching the first launcher without administrator rights, wherein the first command is configured to launch the second launcher with administrator rights; And launching at least one installation module by means of a second command after launching the second launcher, wherein the second command is configured to execute the launchers with administrator rights, in this case, the interface of the first launcher is hidden after the second launcher is launched, and/or The interface of the second launcher is hidden after the installation module is launched. 2. The method of claim 1, wherein the installation module includes at least one function selected from installing imaging device drivers, setting up a wireless network of the imaging device, and performing adding the imaging device. 3. The method according to claim 1, wherein the installation method is used on the MacOS system. 4. The method of claim 3, wherein the first command and the second command are API (Application Programming Interface) commands or scripts in a standard library. 5. A method of installing a program, containing stages in which: repeatedly executing the third command until the installation is complete, after starting the first launch program without administrator rights, while the third command is configured to execute the installation command in a file at a predetermined path with administrator rights; each time before the first startup program executes the third command, the file is cleared and an installation command corresponding to the next installation module to be installed is written to the file by the first writing program. 6. The method for installing programs according to claim 5, wherein the installation module includes at least one function selected from installing imaging device drivers, setting up a wireless network of the imaging device, and performing adding the imaging device. 7. The method according to claim 5, wherein the installation method is used on a MacOS system, and the first command and the second command are API commands or scripts in the standard library. 8. An electronic device for installing the program, containing: memory adapted to store a computer program; And a processor communicatively coupled to the memory, and when the computer program is executed, the processor is configured to execute the program installation method of any one of claims 1 to 7. 9. A computer-readable storage medium containing a computer program that, when executed, causes the processor to carry out the program installation method according to any one of claims 1 to 7.