Installer Account Switching for Secure Batch Installation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software installation methods require frequent prompts for administrator credentials, disrupting the objective of batch installation and potentially lowering security by disabling high security modes, especially when switching between user and administrator accounts during installation operations.
Innovation Solution
An information processing method that determines the appropriate account for executing commands within a master installer, allowing commands to be executed under either a user or administrator account based on their specific requirements, ensuring secure operations and maintaining high security modes when necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the installer runs all commands under the administrator account to ensure sufficient privileges for installation operations, then the installation reliability is improved, but the security level deteriorates because high security modes cannot be maintained
Solution Approach 1:
The installer is divided into multiple process instances, each running under different accounts (administrator or user account) depending on the specific command requirements. This segmentation allows commands to be executed with the minimum necessary privileges, maintaining security while ensuring installation reliability.
Solution Approach 2:
The account context is dynamically switched based on the command type and privilege requirements. The system automatically determines whether to run commands under the administrator account or user account, allowing flexible adaptation to different operational contexts while maintaining appropriate security levels.
2Object-affected harmful factors
If the installer frequently prompts for administrator credentials to execute privileged commands, then the security level is improved, but the ease of operation deteriorates due to interrupted batch installation
Solution Approach 1:
The installer pre-determines the account requirements for each command and switches contexts proactively before executing commands. This preliminary action eliminates the need for frequent interactive credential prompts, allowing batch installation to proceed smoothly while maintaining security through appropriate account usage.
Solution Approach 2:
The installer automatically manages account context switching without requiring user intervention. The system self-services by determining when to switch between administrator and user accounts, eliminating the need for users to repeatedly enter credentials while maintaining security protocols.
3Object-affected harmful factors
If the installer switches between user and administrator accounts during batch installation to optimize security, then the security level is improved, but the device complexity increases due to multiple process contexts
Solution Approach 1:
The installer is designed as a universal system capable of operating under multiple account contexts. By incorporating multi-functionality to handle both user account and administrator account operations within a single unified installer framework, the system achieves improved security without proportionally increasing complexity.
4Object-affected harmful factors
If the installer runs commands under the user account to maintain high security mode, then the security level is improved, but the reliability deteriorates because some installation commands require administrator privileges
Solution Approach 1:
The account context is dynamically adjusted based on the specific command requirements. Commands requiring administrator privileges are executed under the administrator account, while other commands run under the user account to maintain security. This dynamic adaptation ensures both security and installation reliability.
Solution Approach 2:
The account parameter (user account vs. administrator account) is changed based on the command type and privilege requirements. This parameter adjustment allows the system to optimize between security and reliability for different operations, running privileged commands under administrator account and non-privileged commands under user account.
Data Source
AI summary
Commands such as installation operation and launch program commands need to be executed after appropriately switching between an administrator account and another account, for each command, when an installer constituting a program for readily performing installation operations collectively for a plurality of pieces of software or the like is launched. When an installer is launched in the present invention, process-to-process communication is secured between the processes of an administrator account and a user account, and an account to execute a command included in the installer is determined in the process of the administrator account. If the determination result indicates that the account to execute the command is the user account, the command is executed in the process of the user account rather than in the process of the administrator account.