CN113806702A - Method and device for opening authority, electronic equipment and storage medium - Google Patents
Method and device for opening authority, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113806702A CN113806702A CN202111372956.0A CN202111372956A CN113806702A CN 113806702 A CN113806702 A CN 113806702A CN 202111372956 A CN202111372956 A CN 202111372956A CN 113806702 A CN113806702 A CN 113806702A
- Authority
- CN
- China
- Prior art keywords
- installation
- login user
- tool plug
- password
- catalog
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method, a device, an electronic device and a storage medium for opening authority, wherein the method comprises the following steps: determining an installation catalog of the tool plug-in; if the current login user does not have the installation authority in the installation directory, acquiring an authentication password input by the current login user; and if the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user so as to install the tool plug-in the installation directory. By the method, the problem of plug-in installation failure caused by the fact that the user does not have Root authority in the target installation position can be solved.
Description
Technical Field
The application relates to the technical field of system security, in particular to a method and a device for opening authority, electronic equipment and a storage medium.
Background
With powerful functions of VS Code software, various platforms and web pages can be developed, the VS Code software is very attractive in the field of development tools, complicated uploading and downloading steps are not needed, the real-time performance is better, and the VS Code software can be instantly synchronized to a remote development machine only by being stored on a Windows operating system.
When the VS Code software is used, various types of plug-ins need to be downloaded, and when the plug-ins are installed through the VS Code software, if a user in an operating system does not have Root authority in a target folder, the problem of plug-in installation failure is caused.
Disclosure of Invention
In view of this, embodiments of the present application provide a method and an apparatus for opening a permission, an electronic device, and a storage medium, so as to solve a problem of a plugin installation failure caused by a user having no Root permission in a target folder.
In a first aspect, an embodiment of the present application provides a method for opening an authority, including:
determining an installation catalog of the tool plug-in;
if the current login user does not have the installation authority in the installation directory, acquiring an authentication password input by the current login user;
and if the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user so as to install the tool plug-in the installation directory.
In one possible embodiment, obtaining the installation right for the current login user includes:
and sending the verification password and a permission acquisition instruction for acquiring the installation permission to a system, so that the system opens the installation permission in the installation directory for the current login user based on the permission acquisition instruction when determining that the verification password is the same as the login password.
In a possible embodiment, before the determining the installation catalog of the tool plug-in, the method further includes:
judging whether a first installation catalogue for installing the tool plug-in exists or not;
if so, determining the first installation catalog as the installation catalog of the tool plug-in;
if not, acquiring a second installation directory input by the current login user, and determining the second installation directory as the installation directory of the tool plug-in.
In one possible embodiment, the method further comprises:
and if the verification password is different from the login password of the current login user, returning the information of refusing to install the tool plug-in.
In a second aspect, an embodiment of the present application further provides an apparatus for opening an authority, including:
the position unit is used for determining an installation catalog of the tool plug-in;
the password unit is used for acquiring the verification password input by the current login user if the current login user does not have the installation authority in the installation directory;
and the opening unit is used for acquiring the installation authority for the current login user if the verification password is the same as the login password of the current login user so as to install the tool plug-in the installation directory.
In a possible embodiment, the opening unit is configured to:
and sending the verification password and a permission acquisition instruction for acquiring the installation permission to a system, so that the system opens the installation permission in the installation directory for the current login user based on the permission acquisition instruction when determining that the verification password is the same as the login password.
In one possible embodiment, the apparatus further comprises:
a judging unit configured to judge whether or not a first installation directory in which the tool plug-in is installed exists before the determination of the installation directory of the tool plug-in;
the first determining unit is used for determining the first installation catalog as the installation catalog of the tool plug-in if the first installation catalog is the installation catalog of the tool plug-in;
and the second determining unit is used for acquiring a second installation catalog input by the current login user if the tool plug-in is not the current installation catalog, and determining the second installation catalog as the installation catalog of the tool plug-in.
In one possible embodiment, the apparatus further comprises:
and the prompting unit is used for returning the information of refusing to install the tool plug-in if the verification password is different from the login password of the current login user.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of the method according to any one of the first aspect.
In a fourth aspect, this application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the method according to any one of the first aspect.
According to the method, the device, the electronic equipment and the storage medium for opening the permission, under the condition that various tool plugins need to be installed by using VS Code software, whether a login user has the installation permission for installing the tool plugins or not in the installation directory can be judged by determining the installation directory of the tool plugins before installing the tool plugins. Meanwhile, if the login user does not have the installation authority in the installation directory, the installation authority is determined to be obtained for the current login user or not by obtaining the verification password input by the current login user according to the comparison between the verification password and the login password of the current login user. And when the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user, so that the user can install the tool plug-in based on the installation authority.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 shows a flowchart of a method for opening permissions according to an embodiment of the present application.
Fig. 2 is a flowchart illustrating a method for determining an installation directory according to an embodiment of the present application.
Fig. 3 shows a schematic structural diagram of a device for opening authority provided in an embodiment of the present application.
Fig. 4 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.
In addition, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that in the embodiments of the present application, the term "comprising" is used to indicate the presence of the features stated hereinafter, but does not exclude the addition of further features.
It should be noted that the apparatuses, electronic devices, and the like according to the embodiments of the present application may be executed on a single server or may be executed in a server group. The server group may be centralized or distributed. In some embodiments, the server may be local or remote to the terminal. For example, the server may access information and/or data stored in the service requester terminal, the service provider terminal, or the database, or any combination thereof, via the network. As another example, the server may be directly connected to at least one of the service requester terminal, the service provider terminal and the database to access the stored information and/or data. In some embodiments, the server may be implemented on a cloud platform; by way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud (community cloud), a distributed cloud, an inter-cloud, a multi-cloud, and the like, or any combination thereof.
When using a VS Code software (a cross-platform source Code editor), various types of plug-ins need to be downloaded, and when installing a plug-in through the VS Code software, if a user in an operating system does not have Root authority (the highest authority of the operating system) in a target folder, a problem of plug-in installation failure is caused.
Based on the above problem, fig. 1 shows a flowchart of a method for opening a right according to an embodiment of the present application, and as shown in fig. 1, the method specifically includes the following steps:
Specifically, the VS Code software is a cross-platform source Code editor running on a Mac OS X operating system, a Windows operating system, and a Linux operating system and aiming at compiling modern Web (World Wide Web) and cloud applications. The tool plug-in is a plug-in for assisting a user in improving development efficiency when the VS Code software is used for development, and for example, a vscode-icons plug-in (for optimally displaying icons in front of files of various file types), a Beautify plug-in (for rapidly formatting Code formats), and the like.
The method for opening the authority in the embodiment of the application is realized through the automatic authorization script, and in the embodiment of the application, the automatic authorization script is installed in VS Code software. The method for using the automatic authorization script is not limited in the embodiment of the application, the automatic authorization script can be directly run on an operating system and can also be packaged in a tool plug-in, so that when the tool plug-in carrying the automatic authorization script is installed, a user can open the installation permission for installing the tool plug-in the installation directory through the method listed in the embodiment of the application.
When the VS Code software is run on the operating system, corresponding plug-ins can be downloaded in a plug-in library provided by the VS Code software according to requirements. After the downloading of the plug-in is finished, a user needs to install the tool plug-in the operating system, and after the user reaches an installation instruction for installing the tool plug-in through the VS Code software, an automatic authorization script running on the VS Code software determines an installation directory of the tool plug-in. The location of the installation directory may be a default installation location of the operating system, an installation location of the VS Code software, an installation location preset by a user, or a default installation location of the tool plugin in the VS Code software.
And 102, if the current login user does not have the installation authority in the installation directory, acquiring the verification password input by the current login user.
Specifically, the login user represents a virtual identity in the operating system, and the virtual identity and the real identity may be in a one-to-one correspondence relationship, or multiple virtual identities may correspond to the same real identity. For example, when a user logs in one account 1 in a current operating system, the account 1 is a login user of the user in the current operating system, and in the embodiment of the present application, the installation authority is a Root authority by default.
The user permissions of different login users in the same operating system are different, and the user permissions of the same login user in different folders of the operating system may also be different. For example, the login user a has access right to the file 1 in the current operating system 1, but does not have access right to the file 2 in the current operating system 1. Alternatively, user a has access rights in file 1 of the current operating system 1, but user B does not have access rights in file 1 of the current operating system 1.
After the installation directory of the tool plug-in is acquired through step 101, whether a login user in the current operating system has Root authority for installing the tool plug-in the installation directory is judged through the automatic authorization script. And if the login user does not have Root authority in the installation directory, displaying a password input control on the display terminal, and acquiring the verification password input by the current login user in the current operating system. The method for judging whether the current login user has the installation authority in the installation directory is not limited in the embodiment of the application, and the method is arbitrary, and for example, the method can be realized by inquiring whether the installation directory has a specific file or not.
And 103, if the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user so as to install the tool plug-in the installation directory.
Specifically, the verification password is a password input by the user and acquired through the password input control. In this embodiment of the application, the login password may be an actual login password of the login user, or may also be a preset password provided for the login user to obtain Root permissions in the target folder. The target folder may or may not include an installation directory. After acquiring the authentication password input by the current login user through step 102, the automatic authorization script determines whether the authentication password is the same as the login password of the current login user.
Whether the verification password and the login password are correct or not can be determined by a method for acquiring the login password in the system, whether the verification password is the same as the login password or not can be determined by a method for sending the verification password and the verification command to the system through a verification result returned by the system, and if the verification password is the same as the login password of the current login user, the current login user is qualified for acquiring Root authority in an installation directory of the current operating system; if the two types of the operation systems are different, the current login user does not have the qualification of obtaining the Root authority in the installation directory of the current operation system. Meanwhile, if the previous login user is qualified for obtaining the Root authority in the installation directory of the current operating system, the authority obtaining instruction is sent to the operating system and is used for verifying the correctness of the authority obtaining instruction, so that the Root authority in the installation directory is opened for the login user through the verification password and the authority obtaining instruction. After the Root authority of the installation directory is opened for the login user, in the embodiment of the application, the tool plug-in can be automatically installed based on the Root authority of the login user.
According to the method for opening the permission, when VS Code software is used and various tool plugins need to be installed, whether a login user has the installation permission for installing the tool plugins or not in the installation directory can be judged by determining the installation directory of the tool plugins before the tool plugins are installed. Meanwhile, if the login user does not have the installation authority in the installation directory, the installation authority is determined to be obtained for the current login user or not by obtaining the verification password input by the current login user according to the comparison between the verification password and the login password of the current login user. And when the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user, so that the user can install the tool plug-in based on the installation authority.
In one possible embodiment, obtaining the installation right for the current login user includes:
and sending the verification password and a permission acquisition instruction for acquiring the installation permission to a system, so that the system opens the installation permission in the installation directory for the current login user based on the permission acquisition instruction when determining that the verification password is the same as the login password.
Specifically, the terminal panel is a control in the VS Code software for sending a permission acquisition instruction to the operating system; when the VS Code software acquires the verification password through the password input control, the terminal panel of the VS Code software is opened and is in a background running state, and the sight of a user is prevented from being obstructed. The authority acquisition instruction comprises a statement or a code which is used for sending to an operating system and contains a Root authority which is opened in the installation directory for the login user; and the VS Code software sends the verification password and the permission acquisition instruction to the operating system according to a preset format through the terminal panel, so that the operating system opens the Root permission of the current login user in the installation directory by executing the permission acquisition instruction after the operating system determines that the verification password is correct.
In a possible embodiment, after obtaining the Root right of the directory at installation, the method further includes: and sending an installation instruction to an operating system through the terminal panel.
Specifically, the installation instruction is sent to the system, so that the system installs the tool plug-in according to the installation instruction after receiving the installation instruction. The permission acquisition instruction and the installation instruction can be sent simultaneously or according to the sequence. For example, when the right acquiring instruction and the installation instruction are sent simultaneously, the right acquiring instruction is executed to acquire the Root right of the login user in the installation directory, and then the installation instruction is executed based on the Root right of the login user in the installation directory to install the tool plug-in the installation directory. Or, the authority acquiring instruction may be sent to the operating system, and after the operating system returns the identifier after the authority is successfully opened, the installation instruction may be sent. And the problem that when the operating system fails to open the authority for the user is avoided, the instruction for installing the tool plug-in is still executed.
In a possible implementation, fig. 2 shows a flowchart of a method for determining an installation directory provided in an embodiment of the present application, and as shown in fig. 2, when determining the installation directory of the tool plug-in step 101, the method includes the following steps:
Specifically, the position of the first installation directory is the installation position which is set by the operating system for the tool plug-in by default; in the embodiment of the application, a first installation directory for installing the tool plug-in is searched in an installation path of VS Code software. In practical applications, the location of the first installation directory may also be an installation location other than the installation location of the VS Code software.
And searching whether a first installation directory for installing the tool plug-in exists in a target folder for installing the VS Code software through an installation path of the VS Code software. Or, in the preset installation rule, searching whether a preferred installation catalog aiming at the tool plug-in exists or not, and determining the preferred installation catalog as a first installation catalog.
If there is a first installation catalog for installing the tool plug-in, then step 202 is entered.
If there is no first installation catalog for installing the tool plug-in, then step 203 is entered directly.
Specifically, when there is an installation catalog preset for the tool plug-in, the first installation catalog is determined as the installation catalog of the tool plug-in.
Specifically, when there is no installation catalog preset for the tool plug-in, which indicates that the installation catalog of the tool plug-in needs to be manually selected, the VS Code software displays a position selection control for selecting a second installation catalog of the tool plug-in on the display terminal, so that the second installation catalog selected or input by the user is obtained through the position selection control, and the second installation catalog selected by the user is determined as the installation catalog for installing the tool plug-in.
From step 202 or step 203, an installation catalog of the tool insert can be determined.
In a possible embodiment, after step 103 is performed, the method further comprises:
and if the verification password is different from the login password of the current login user, returning the information of refusing to install the tool plug-in.
Specifically, if the verification password is different from the login password of the current login user, and it is determined that the login user does not have the qualification of opening the Root authority in the installation directory, displaying information of refusing to install the tool plugin through the display terminal, and ending the installation process of the tool plugin.
In a possible implementation, fig. 3 illustrates a schematic structural diagram of an apparatus for opening a right according to an embodiment of the present application, and as shown in fig. 3, the apparatus includes a location unit 301, a password unit 302, and an opening unit 303.
A location unit 301 for determining an installation catalog of tool inserts.
A password unit 302, configured to obtain an authentication password input by the current login user if the current login user does not have an installation authority in the installation directory.
And the opening unit 303 is configured to obtain the installation authority for the current login user if the verification password is the same as the login password of the current login user, so that the tool plugin is installed in the installation directory.
In a possible embodiment, the opening unit is configured to:
and sending the verification password and a permission acquisition instruction for acquiring the installation permission to a system, so that the system opens the installation permission in the installation directory for the current login user based on the permission acquisition instruction when determining that the verification password is the same as the login password.
In one possible embodiment, the apparatus further comprises:
and the judging unit is used for judging whether a first installation catalogue for installing the tool plug-in exists before the installation catalogue for determining the tool plug-in is determined.
And the first determining unit is used for determining the first installation catalog as the installation catalog of the tool plug-in if the first installation catalog is the installation catalog of the tool plug-in.
And the second determining unit is used for acquiring a second installation catalog input by the current login user if the tool plug-in is not the current installation catalog, and determining the second installation catalog as the installation catalog of the tool plug-in.
In one possible embodiment, the apparatus further comprises:
and the prompting unit is used for returning the information of refusing to install the tool plug-in if the verification password is different from the login password of the current login user.
According to the device for opening the permission, under the condition that various tool plugins need to be installed by using VS Code software, whether a login user has the installation permission for installing the tool plugins or not in the installation directory can be judged by determining the installation directory of the tool plugins before the tool plugins are installed. Meanwhile, if the login user does not have the installation authority in the installation directory, the installation authority is determined to be obtained for the current login user or not by obtaining the verification password input by the current login user according to the comparison between the verification password and the login password of the current login user. And when the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user, so that the user can install the tool plug-in based on the installation authority.
In a possible implementation, fig. 4 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application, including: a processor 401, a storage medium 402 and a bus 403, wherein the storage medium 402 stores machine-readable instructions executable by the processor 401, when the electronic device runs the method of opening the right as in the embodiment, the processor 401 and the storage medium 402 communicate with each other through the bus 403, and the processor 401 executes the machine-readable instructions to perform the steps as in the embodiment.
In an embodiment, the storage medium 402 may further execute other machine-readable instructions to perform other methods as described in the embodiments, and for the method steps and principles of specific execution, reference is made to the description of the embodiments, which is not described in detail herein.
Embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor when the computer program is executed to perform the steps in the embodiments.
In the embodiments of the present application, when being executed by a processor, the computer program may further execute other machine-readable instructions to perform other methods as described in the embodiments, and for the method steps and principles of specific execution, reference is made to the description of the embodiments, and details are not repeated here.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and there may be other divisions in actual implementation, and for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some communication interfaces, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for opening permissions, comprising:
determining an installation catalog of the tool plug-in;
if the current login user does not have the installation authority in the installation directory, acquiring an authentication password input by the current login user;
and if the verification password is the same as the login password of the current login user, acquiring the installation authority for the current login user so as to install the tool plug-in the installation directory.
2. The method of claim 1, wherein obtaining the installation right for a currently logged-in user comprises:
and sending the verification password and a permission acquisition instruction for acquiring the installation permission to a system, so that the system opens the installation permission in the installation directory for the current login user based on the permission acquisition instruction when determining that the verification password is the same as the login password.
3. The method of claim 1, prior to said determining an installation catalog of tool inserts, further comprising:
judging whether a first installation catalogue for installing the tool plug-in exists or not;
if so, determining the first installation catalog as the installation catalog of the tool plug-in;
if not, acquiring a second installation directory input by the current login user, and determining the second installation directory as the installation directory of the tool plug-in.
4. The method of claim 1, further comprising:
and if the verification password is different from the login password of the current login user, returning the information of refusing to install the tool plug-in.
5. An apparatus for opening permissions, comprising:
the position unit is used for determining an installation catalog of the tool plug-in;
the password unit is used for acquiring the verification password input by the current login user if the current login user does not have the installation authority in the installation directory;
and the opening unit is used for acquiring the installation authority for the current login user if the verification password is the same as the login password of the current login user so as to install the tool plug-in the installation directory.
6. The apparatus of claim 5, wherein the provisioning unit is configured to:
and sending the verification password and a permission acquisition instruction for acquiring the installation permission to a system, so that the system opens the installation permission in the installation directory for the current login user based on the permission acquisition instruction when determining that the verification password is the same as the login password.
7. The apparatus of claim 5, further comprising:
a judging unit configured to judge whether or not a first installation directory in which the tool plug-in is installed exists before the determination of the installation directory of the tool plug-in;
the first determining unit is used for determining the first installation catalog as the installation catalog of the tool plug-in if the first installation catalog is the installation catalog of the tool plug-in;
and the second determining unit is used for acquiring a second installation catalog input by the current login user if the tool plug-in is not the current installation catalog, and determining the second installation catalog as the installation catalog of the tool plug-in.
8. The apparatus of claim 5, further comprising:
and the prompting unit is used for returning the information of refusing to install the tool plug-in if the verification password is different from the login password of the current login user.
9. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of the method of opening permissions according to any of claims 1-4.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method for opening rights according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111372956.0A CN113806702A (en) | 2021-11-19 | 2021-11-19 | Method and device for opening authority, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111372956.0A CN113806702A (en) | 2021-11-19 | 2021-11-19 | Method and device for opening authority, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113806702A true CN113806702A (en) | 2021-12-17 |
Family
ID=78938399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111372956.0A Pending CN113806702A (en) | 2021-11-19 | 2021-11-19 | Method and device for opening authority, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113806702A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030018964A1 (en) * | 2001-07-19 | 2003-01-23 | International Business Machines Corporation | Object model and framework for installation of software packages using a distributed directory |
| CN105072183A (en) * | 2015-08-10 | 2015-11-18 | 浪潮(北京)电子信息产业有限公司 | Management method and management device for cloud operation system (OS) software repository |
| CN109343867A (en) * | 2018-10-16 | 2019-02-15 | 平安科技（深圳）有限公司 | The self-service installation method of software, device, computer equipment and storage medium |
| CN109683976A (en) * | 2017-10-17 | 2019-04-26 | 航天信息股份有限公司 | A kind of embedded plug-in loading method and system based on application platform |
| CN112597481A (en) * | 2020-12-29 | 2021-04-02 | 平安银行股份有限公司 | Sensitive data access method and device, computer equipment and storage medium |
-
2021
- 2021-11-19 CN CN202111372956.0A patent/CN113806702A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030018964A1 (en) * | 2001-07-19 | 2003-01-23 | International Business Machines Corporation | Object model and framework for installation of software packages using a distributed directory |
| CN105072183A (en) * | 2015-08-10 | 2015-11-18 | 浪潮(北京)电子信息产业有限公司 | Management method and management device for cloud operation system (OS) software repository |
| CN109683976A (en) * | 2017-10-17 | 2019-04-26 | 航天信息股份有限公司 | A kind of embedded plug-in loading method and system based on application platform |
| CN109343867A (en) * | 2018-10-16 | 2019-02-15 | 平安科技（深圳）有限公司 | The self-service installation method of software, device, computer equipment and storage medium |
| CN112597481A (en) * | 2020-12-29 | 2021-04-02 | 平安银行股份有限公司 | Sensitive data access method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111695156A (en) | Service platform access method, device, equipment and storage medium | |
| CN109033857B (en) | Method, device and equipment for accessing data and readable storage medium | |
| CN111090439B (en) | Mirror image generation method, device and equipment for Linux system of bare metal server | |
| CN109471865A (en) | A kind of off-line data management method, system, server and storage medium | |
| CN112860277B (en) | Software deployment method, device and computer readable storage medium | |
| CN111026723B (en) | Big data cluster management control method and device, computer equipment and storage medium | |
| CN104346184A (en) | Application packaging device and application packaging method | |
| CN105871794A (en) | Distributed file system date storage method and system, client and server | |
| CN112968929B (en) | Server management method and system | |
| CN109614203B (en) | Android application cloud data evidence obtaining and analyzing system and method based on application data simulation | |
| CN113330419B (en) | Equipment application installation method, device, equipment and storage medium | |
| CN117150534B (en) | Trusted DCS upper computer application access control method and system based on authority management | |
| CN112838951A (en) | Operation and maintenance method, device and system of terminal equipment and storage medium | |
| CN111522625A (en) | Cloud data online evidence obtaining system and method | |
| CN114020678B (en) | Server serial console redirection method, device and system and electronic equipment | |
| CN112543109A (en) | Cloud host creation method, system, server and storage medium | |
| CN113806702A (en) | Method and device for opening authority, electronic equipment and storage medium | |
| CN114024978A (en) | Cloud resource synchronization method, device, node and storage medium | |
| US20130246523A1 (en) | Browser based recovery discovery | |
| CN104518871A (en) | Network platform and method for performing self-service authentication on mobile storage equipment | |
| CN111984211A (en) | Screen configuration method, screen configuration device and screen configuration system | |
| CN115114622A (en) | Virus scanning and displaying method and system | |
| Cisco | Installing the IPM Client on Windows NT | |
| CN114462003A (en) | Server user permission control method and device under multi-type test environment | |
| CN111475198B (en) | Mimicry method and device of network server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211217 |
|
| RJ01 | Rejection of invention patent application after publication |