COMMUNICATION DEVICE, CONTROL METHOD AND PROGRAM FOR COMMUNICATION DEVICE
The communication device allows flexible switching between encrypted and plain text DNS servers based on application and protocol exceptions, addressing the inefficiencies in configuring secure DNS over HTTPS (DoH) across systems and devices.
Patent Information
- Application Number
- JP2020066185
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-04-01
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-04-01
AI Technical Summary
Existing communication devices lack a mechanism to efficiently configure the use of encrypted communication for name resolution across systems and devices, leading to time-consuming or omitted settings, especially when secure DNS over HTTPS (DoH) is required by security policies.
A communication device with settings to enable or disable encrypted communication for name resolution, allowing flexible switching between encrypted and plain text DNS servers based on application and protocol exceptions, using a DNS control unit to manage settings and exceptions.
Enables efficient and secure switching of name resolution destinations based on application and protocol settings, ensuring compliance with security policies without manual errors.
Smart Images

Figure 0007577456000001 
Figure 0007577456000002 
Figure 0007577456000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication device that transmits data to an external device. [Background technology]
[0002] In recent years, a mechanism such as DNS over HTTPS (DoH) has been considered as a technology to prevent eavesdropping, spoofing, and tampering when requesting host name resolution from the Domain Name System (DNS).
[0003] With DoH, queries such as name resolution requests to DNS can be sent over a communication path encrypted by HTTPS, rather than in plain text. Major web browser applications can use DoH by switching the DNS settings of the web browser application from DNS to DoH. This mechanism prevents third parties from eavesdropping on the request content or tampering with the request results by spoofing when the browser application resolves the name of a URL.
[0004] Furthermore, from the viewpoint of security, Patent Document 1 discloses a device that sets whether or not to permit name resolution to a DNS server for each application installed on the device. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2017-139648 A Summary of the Invention [Problem to be solved by the invention]
[0006] As mentioned above, it is known to set up an operation setting for using DoH as a setting for a stand-alone application such as a web browser application.
[0007] Incidentally, in communication devices such as MFPs (Multi Function Peripherals) and PCs, communication may be performed with a communication partner specified by a host name, such as accessing a file server, in addition to a web browser application. In addition, depending on the security policy of an organization or company, it may be recommended to use secure DoH by resolving the host name in the communication device. In this case, it is possible to set whether or not to use DoH as a setting for a single application, or to switch whether or not to use DoH on the application side, but there are problems such as the hassle of setting and the possibility of missing settings. However, in the past, no specific mechanism was considered for setting to use DoH in communication of the entire system or the entire device.
[0008] The present invention has been made in consideration of at least one of the above problems. One aspect of the present invention aims to provide a mechanism that allows the use of encrypted communication for name resolution to be set as an operation setting of the communication device, and allows the communication device to appropriately switch the name resolution request destination. [Means for solving the problem]
[0009] In order to achieve at least one of the above objects, a communication device according to the present invention comprises: before A setting means for setting whether or not encrypted communication is to be used for name resolution as an operation setting of the communication device; a communication control means for controlling, when performing name resolution of a host name requested by an application, to request the first DNS server to resolve the host name via an encrypted communication path established with a first DNS server based at least on the setting means being set to use the encrypted communication, and to request the second DNS server to resolve the host name in plain text based on the setting means being set to not use the encrypted communication; a receiving means for receiving a designation of an application to be excluded from the target of the name resolution using the encrypted communication; a storage means for storing identification information of an application, the designation of which is accepted by the accepting means, the identification information of an application to be excluded from the target of name resolution using the encrypted communication; a determination means for determining whether or not the requesting application is an application that should be subject to name resolution using the encrypted communication based on the identification information stored in the storage means and the type of the requesting application; A sending application that sends scan data to a destination specified by a host name; A web browser application; Have death, When the determination means determines that the requesting application is an application that should not be a target for name resolution using the encrypted communication, the communication control means controls to request the second DNS server to perform name resolution of the host name in plain text even if the setting means has set the encrypted communication to be used; The sending application and the Web browser application can be designated as applications to be excluded by the accepting means. It is characterized by: Effect of the Invention
[0010] According to one aspect of the present invention, by setting whether or not to use encrypted communication for name resolution as an operational setting of the communication device, it becomes possible to appropriately switch the name resolution destination of the communication device. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 illustrates an example of a communication system. [Diagram 2] FIG. 2 is a diagram illustrating an example of the hardware configuration of an MFP 101. [Diagram 3] FIG. 2 is a diagram illustrating an example of the software configuration of an MFP 101. [Figure 4] FIG. 13 is a diagram illustrating an example of a setting screen related to a network. [Diagram 5] FIG. 4 is a diagram showing an example of a setting screen related to a network in the first embodiment. [Figure 6] 5 is a flowchart showing an example of control of the MFP 101 in the first embodiment. [Figure 7] FIG. 11 is a diagram illustrating an example of a setting screen related to a network in the second embodiment. [Figure 8] 10 is a flowchart showing an example of control of the MFP 101 in the second embodiment. [Figure 9] FIG. 13 is a diagram showing an example of a setting screen relating to a security policy in the third embodiment. [Figure 10] 13 is a flowchart showing an example of control of the MFP 101 in the third embodiment. [Figure 11]FIG. 13 is a diagram showing an example of a modified example of a setting screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Hereinafter, the embodiments for carrying out the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and all of the combinations of features described in the embodiments are not necessarily essential to the solution of the invention.
[0013] <First embodiment> First, the configuration of the communication system according to the present invention will be described with reference to FIG. 1. In the communication system according to the present embodiment, an MFP (Multi Function Peripheral) 101, a DNS (Domain Name System) server 102, and a mail server 103 are communicably connected via a network 100. A file server 104 and a print server 105 are communicably connected via the network 100. Host names managed by the DNS server 102 are assigned to the servers 103 to 105. The MFP 101 is communicably connected to a DoH (DNS Over HTTPS) server 107 and a Web server 108 on the Internet 106 via the network 100 and a WAN or the like. The network 100 is, for example, a local zone within a company or organization. The servers 103 to 105 are provided for clients in the local zone. Therefore, name resolution of the host names corresponding to the servers 103 to 105 can only be performed by a DNS server in the local zone. In other words, the DoH server 107 located on the Internet cannot perform name resolution for host names in local zones (host names used within a company or organization).
[0014] MFP101 is an example of a communication terminal. In this embodiment, as an example, an MFP having a printing function and a transmission function of transmitting an image obtained by scanning a document to the outside is illustrated, but it is not limited thereto. It can also be applied to communication devices such as IoT devices, personal computers, and smartphones.
[0015] MFP101 has a transmission function of transmitting data (also referred to as scan data) based on an image obtained by scanning to a file server or attaching it to an email and transmitting it. Hereinafter, the transmission function of performing email transmission or file transmission on the data based on the image is also simply referred to as the SEND function.
[0016] In addition, MFP101 has a pull printing function of accessing print server 105, receiving print data stored in the print server, and printing it. Also, MFP101 has a web browser application, and can display web content obtained from web server 108 or the like on operation unit 116 of MFP101.
[0017] When transmitting data with the SEND function, MFP101 performs transmission using a destination specifying the host name of the server. Also, when MFP101 transmits an email with attached data, it resolves the host name of mail server 103 and acquires the IP address for communicating with the mail server 103. Subsequently, communication is performed with mail server 103 using the IP address to send the email. Also, when displaying web content on MFP101, the URL of a web server (for example, web server 108) is input to specify the acquisition destination server of the web content. The method of name resolution of the host name at this time will be described later.
[0018] <Hardware Configuration of MFP101> Next, the MFP 101 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing the hardware configuration of the MFP 101. The MFP 101 has a reading function for reading an image on a sheet, a file transmission function capable of transmitting the read image to an external communication device, and the like. It also has a printing function for printing an image on a sheet.
[0019] A control unit 110 including a CPU (Central Processing Unit) 111 controls the overall operation of the MFP 101. The CPU 111 reads out a control program stored in a ROM (Read Only Memory) 112 or a storage 114, and performs various controls such as print control and read control. The ROM 112 stores control programs executable by the CPU 111. A RAM (Random Access Memory) 113 is a main memory accessed by the CPU 111, and is used as a work area or a temporary storage area for expanding various control programs. The storage 114 stores print data, image data, various programs, and various setting information. In this way, the hardware such as the CPU 111, the ROM 112, the RAM 113, and the storage 114 constitute a so-called computer.
[0020] In the MFP 101 of this embodiment, one CPU 111 executes each process shown in the flowcharts described later using one memory (RAM 113), but other configurations are also possible. For example, each process shown in the flowcharts described later can be executed by making multiple processors, memories, and storages work together. Also, some of the processes can be executed using hardware circuits.
[0021] A printer I / F (interface) 119 connects a printer 120 (printer engine) and the control unit 110. The printer 120 prints an image on a sheet fed from a paper feed cassette (not shown) based on print data input via the printer I / F 119. The printing method may be an electrophotographic method in which toner is transferred to paper and fixed thereon, or an inkjet method in which ink is ejected onto paper for printing. The printer 120 may also be a 3D printer that generates a three-dimensional output object using a modeling material. In this case, the print data becomes print data indicating a 3D shape, and a three-dimensional output object is generated using a modeling material or a support material instead of color materials such as toner or ink.
[0022] The scanner I / F 117 connects the scanner 118 to the control unit 110. The scanner 118 reads an original placed on a platen (not shown) and generates image data. The image data generated by the scanner 118 is printed by the printer 120, stored in the storage 114, or transmitted to an external device via the network I / F 121.
[0023] The operation unit I / F 115 connects the operation unit 116 and the control unit 110. The operation unit 116 is equipped with a liquid crystal display unit having a touch panel function, various hard keys, and the like. The operation unit 116 functions as a display unit that displays information to the user and a reception unit that receives instructions from the user. The CPU 111 cooperates with the operation unit 116 to control the display of information and the reception of user operations.
[0024] A network cable is connected to the network I / F 121, enabling communication with external devices on the network 100 or the Internet. In this embodiment, it is assumed that the network I / F 121 is a communication interface that performs wired communication compliant with Ethernet (registered trademark), but it is not limited to this. For example, it may be a wireless communication interface compliant with the IEEE802.11 series. Also, both may be wireless communication interfaces. Further, it may be a communication interface that performs mobile communication such as 3G lines like CDMA, 4G lines like LTE, or 5G NR.
[0025] <Software Configuration of MFP101> Subsequently, with reference to FIG. 3, the software configuration of the MFP 101 will be described. Each functional block shown in FIG. 3 is assumed to be realized by the CPU 111 executing a program expanded in the RAM 113.
[0026] The OS (Operating System) 1020 is a program that performs basic control of the computer. The OS 1020 includes a management module that manages processes of applications and middleware, a module function that functions as a TCP / IP protocol stack for network communication, and an OS standard DNS client 1021 for name resolution. Also, the middleware 1030 is a group of modules located in the upper layer of the OS 1020. The middleware 1030 includes a module that manages the operation settings of the MFP 101 and a DoH (DNS over HTTPS) client 1080 for performing name resolution on an encrypted communication path. Also, it is assumed that the MFP 101 also has middleware such as a module that controls printing (not shown in the figure for the sake of simplicity). The application 1010 is a group of applications that realize the functions of the MFP operating on the OS 1020.
[0027] First, the applications of the MFP 101 will be described. The Web browser application 1010a is a Web browser that displays Web content acquired from a Web server on the network. The SEND application 1010b is an application that transmits data based on an image obtained by scanning an original using the scanner 118 via a file server or a mail server. The SEND application 1010b can transmit a file based on an image obtained by reading an original using the scanner 118 to a transmission destination designated by a user. The transmission destination can be specified by a user operation via a transmission setting screen (not shown). The user specifies the destination by inputting the host name of the file server or mail server in the format of an FQDN (Fully Qualified Domain Name). After the transmission destination is set via the transmission setting screen, the SEND application 1010a requests the scanner 118 to read the original according to the selection of a key to start transmission. The SEND application 1010a then transmits data based on an image obtained by reading the original to a transmission destination designated by the user. In this embodiment, file transmission using a transmission protocol such as FTP (File Transfer Protocol) or SFTP (SSH FTP) is assumed as an example of the transmission process. It is also assumed that mail transmission processing is performed using SMTP (Simple Mail Transfer Protocol) via mail server 103. However, this is not limited to this, and the present invention can also be applied to file transmission using a communication protocol such as WebDAV (Web-based Distributed Authoring and Versioning).
[0028] The pull print application 1010b is a print application that receives print jobs stored in the print server 105 and prints them via the printing unit 120. The application 1010b queries the print server 105 on the network 100 about print jobs, and downloads job data specified in URL format from a cloud server or cloud storage and prints the data. These communications also involve communication with a destination specified by a host name or a URL (Uniform Resource Locator). Note that name resolution and data transmission processing when these applications communicate are performed in cooperation with the middleware 1030 and the OS 1020.
[0029] In this way, a communication device such as the MFP 101 may communicate with a communication partner specified by a host name in a manner other than a web browser application, such as accessing a file server. In addition, depending on the security policy of an organization or company, it may be recommended to use secure DoH by resolving the host name in the communication device. In this case, it is possible to set whether or not to use DoH as a setting for a single application, or to switch whether or not to use DoH on the application side, but this may cause problems such as time-consuming configuration and missed settings.
[0030] In this embodiment, whether or not to use encrypted communication for name resolution can be set as an operational setting of the communication device, and a mechanism is provided for appropriately switching the destination to which name resolution is requested in the communication device.
[0031] Returning to the explanation of FIG. 3, the OS 1020 also includes a TCP / IP protocol stack for network communication and an OS standard DNS client 1021 for name resolution. In this embodiment, it is assumed that the DNS client 1021 is a standard DNS client in a Linux (registered trademark) system. When performing name resolution of a domain name using these clients, a DNS server is specified by writing "nameserver "IP address of DNS server"" in a file located in " / etc / resolve.conf". For redundancy, it is also possible to specify multiple DNS servers to be used. In this embodiment, it is assumed that the IP address of the DNS server 102 is set. The DNS client 1021 has a function of requesting name resolution in plain text to a specified DNS server.
[0032] Next, the operation of the middleware group 1030 will be described. The setting value DB 1050 stores the operation settings of the MFP 101, including the communication settings. The communication settings include settings for each communication interface and settings related to DNS. The DoH client 1080 establishes an encrypted communication path with the DoH server 107 that supports DoH, and requests name resolution from the server 107 by HTTP communication via the established communication path.
[0033] The DNS control unit 1040 has a function of displaying a setting screen on the operation unit 116, accepting changes to various network settings from a user such as an administrator, and storing the changes in the setting value DB 1050. The control unit 1040 also has a DNS setting control unit 1040a. The DNS setting control unit 1040a refers to values in the setting value DB 1050 and performs startup control and operation setting control of the DoH client 1080 and the DNS client 1021. The DNS control unit 1040 also has a function of determining whether to request the DNS client 1021 or the DoH client 1080 to resolve a host name received from an application.
[0034] Note that the control unit 1040 can also provide a web page for checking and changing settings related to name resolution in cooperation with a web server function (not shown). In this case, a user such as an administrator can access the web page provided by the MFP 101 from a client such as a PC and change the settings related to name resolution.
[0035] The DNS server automatic acquisition unit 1070 has a function of acquiring the addresses of DNS servers and DoH servers from a DHCP server or an IPv6 router. The control unit 1040 cooperates with the acquisition unit 1070 to acquire the IP address of the DNS server and the host name / IP address of the DoH server from the DHCP server or the IPv6 server and save them as DNS operation settings. When the automatic acquisition of the DNS server is set to be effective in the DNS server automatic acquisition unit 1070, the DNS server settings are acquired from the network. The automatic acquisition unit 1070 includes a DHCP (Dynamic Host Configuration Protocol) client. The DHCP client of the automatic acquisition unit 1070 transmits a request including a DHCP option for inquiring about a name resolution server to the DHCP server on the network to acquire the addresses of the DNS server and the DoH server. Note that when IPv6 is adopted as the protocol stack, the addresses of the DNS server and the DoH server can also be acquired through the exchange of RS (Router Solicitation) and RA (Router Advertisement).
[0036] <DNS-related operation settings in the MFP 101> An example of DNS-related operation settings via the screen provided by the control unit 1040a will be described with reference to FIG. 4. The screen 400 is an example of a screen displayed on the operation unit 116 of the MFP 101.
[0037] Key 401a is a key used when enabling (ON) the operation setting that uses DoH, and key 401b is a key used when disabling (OFF) the operation setting that uses DoH. One of keys 401a and 401b is set to enabled, and the other is set to disabled. Here, an example is shown in which the operation setting that uses DoH for name resolution is set to enabled.
[0038] Key 402a is a key used to enable (ON) the operation setting for automatically obtaining a DoH server address from a DHCP server, RA, etc. On the other hand, key 402b is a key used to disable (OFF) the operation setting for automatically obtaining a DoH server address. One of keys 402a and 402b is set to enabled, and the other is set to disabled. Screen 400 illustrates an example in which the setting for automatic acquisition is configured.
[0039] Area 403 is an area that displays the settings of the DoH server. Area 403 also functions as an area for manually setting the host name and IP address of the DoH server when key 401b is set to be enabled and automatic acquisition is set to be disabled. In this case, the user can manually set the DoH server address by inputting the IP address and host name via a software keyboard (not shown) displayed on operation unit 116.
[0040] The key 404 is a key used when making an exception setting for DoH. Details will be described later. The keys 405a and 405b are keys for switching whether to automatically obtain the IP address of a DNS server that performs name resolution in plain text. In this embodiment, a case where an operation setting for automatic acquisition is made is illustrated. The area 407 is an area for displaying the setting of the DNS server. The area 407 also functions as an area for manually setting the IP address of the DNS server when automatic acquisition is set to disabled. When the control unit 1040a detects that the enter key has been pressed after a setting operation has been made via the screen 400, the control unit 1040a stores the setting made via the screen in the setting value DB 1050 as the operation setting of the MFP 101.
[0041] Next, the DoH exception settings will be described with reference to Fig. 5. Fig. 5(A) is an example of a screen related to the DoH exception settings, and Fig. 5(b) is an example of setting values stored in the setting value DB 1050.
[0042] When the CPU 111 of the MFP 101 detects that the key 404 on the screen 400 is selected, the screen displayed on the operation unit 116 transitions to a setting screen 500. The screen 500 is a screen for setting exceptions to name resolution by the DoH client 1080. By performing a touch operation on the area 501, the user can set an exception application for which name resolution is not performed by DoH for each application included in the MFP 101. The user can specify an application to be excluded from the target of name resolution used from DoH by operating via the screen. In this embodiment, a case in which the SEND application 1010b is set as the exception application is illustrated. For example, an administrator or the like can prevent DoH from being used for an application that communicates exclusively with a server on a local zone, taking into account the user's usage history. Therefore, it is possible to prevent the host name of a server providing a service for the local zone on the Internet from being leaked to the DoH server 107.
[0043] The area 502 is an area used when explicitly specifying a host name that should be an exception to a name resolution request to a DoH server. Hereinafter, a host name that should be an exception to a name resolution request to a DoH server is also simply referred to as an exception host name or the like. An administrator who wants to add an exception host name presses an add key and inputs the exception host name via an input screen not shown. The edit key is a key used when editing an exception host name that has already been registered. The delete key is a key used when deleting one or more registered exception host names selected by a touch operation on the area 502. Note that, when using a screen via the Web, it is also possible to import a csv file or the like that lists exception host names separated by commas, so that the exception host name can be registered. When the control unit 1040a detects that the enter key has been pressed after a setting operation has been performed via the screen 500, the control unit 1040a stores the setting performed via the screen in the setting value DB 1050 as the operation setting of the MFP 101.
[0044] The settings of the exception application and the exception host name made by the user operation via FIG. 5 are stored in the setting value DB 1050 as the operation settings of the MFP 101. FIG. 5(b) is an example of the operation settings related to the name resolution made via FIG. 4 and FIG. 5(A). The settings made via the area 502 are stored as data of a list structure in which the exception host names are listed (hereinafter, also referred to as the exception host name list). The DoH setting is an operation setting indicating whether or not DoH is used. The DNS provider setting is a setting indicating the IP address of the DNS server used by the MFP 101. The DoH provider is a setting indicating the host name or IP address of the DoH server used by the MFP 101. The exception app setting is a setting indicating the name as identification information for identifying the application that is an exception of DoH. Note that the information stored in the setting value DB 1050 may be an ID for identifying the application to specify the application. The settings are appropriately referred to in the flowchart described later.
[0045] Specific control will be described with reference to the flowchart of Fig. 6. Each operation (step) shown in the flowchart of Fig. 6 is realized by CPU 111 calling up into RAM 113 a program for implementing each control module stored in ROM 112 or storage 114 and executing it. Note that data transmission and reception processing and the like are realized in cooperation with network I / F 121. In addition, in cases where it is desired to clarify the subject of processing, the description will be given with the software module executed by CPU 111 as the subject. The flowchart of Fig. 6 is executed when a request for name resolution of a host name or the like is made from various applications.
[0046] In S601, the DNS control unit 1040 refers to the setting value DB 1050 and determines whether or not a setting for using DoH has been made. If the setting value corresponding to the setting item DoH is ON, it is determined that a setting for using DoH has been made, and the process proceeds to S602. If the setting value corresponding to the setting item DoH is OFF, it is determined that a setting for using DoH has not been made, and the process proceeds to S606.
[0047] In S602, the control unit 1040 judges whether or not the host name to be resolved, requested by the application, is included in the exception host name list. If a host name matching the host name requested by the application is registered in the exception host name list, the process proceeds to S606, and if not, the process proceeds to S603.
[0048] In S603, the control unit 1040 identifies the type of the application that has requested the name resolution, and judges whether or not the type of the identified application is designated as an exception application. If the type of the identified application is designated as an exception application, the process proceeds to S606, and if not, the process proceeds to S604. The following method can be adopted as a specific method for identifying the application that has requested the name resolution in S603. For example, the control unit 1040 functioning as the middleware 1030 provides each application with an API function to be called when requesting name resolution. This API function is configured so that identification information for identifying the application can be set as an argument. When each application calls the API function (i.e., when requesting name resolution), it sets identification information for identifying the application as an argument. The control unit 1040 can identify the type of the application that has requested the name resolution by referring to the argument.
[0049] In S604, the control unit 1040 transfers a name resolution request made by the application to the DoH client 1080. Subsequently, in S605, the DoH client 1080 that has accepted the name resolution request requests the DoH server 107 to perform name resolution using encrypted communication. At this time, it is assumed that communication for name resolution is performed over an HTTPS communication path.
[0050] In S608, the control unit 1040 receives the result of the name resolution from the DoH client 1080 and determines whether or not an IP address has been obtained as a result of the name resolution. If an IP address corresponding to the host name has been obtained as a result of the name resolution by the DoH server 107, the process proceeds to S609, and if an IP address corresponding to the host name has not been obtained, the process proceeds to S606. For example, the control unit 1040 determines that an IP address has not been obtained if communication with the DoH server cannot be performed or if the result of the name resolution received from the DoH server indicates that the destination could not be found. The process of S608 is a process for realizing a fallback that transitions to plaintext name resolution when the destination cannot be found in DoH.
[0051] In S606, the control unit 1040 requests the DNS client 1021 to perform name resolution. Then, in S607, the DNS client 1021 transfers the request for name resolution to the DNS server 102. The request for name resolution is made in plain text as described above. If the domain name is one that the DNS server 102 manages, the DNS server 102 responds with an IP address corresponding to the domain, and if not, transfers the query to a higher-level DNS server and performs name resolution.
[0052] Finally, in S609, the control unit 1040 returns a response to the name resolution request sent in S607 or S605 to S609. The above-described series of processes makes it possible to flexibly switch communication control between attempting name resolution using DoH and performing conventional plaintext name resolution without attempting DoH, based on the settings of exception applications and exception host names.
[0053] <Second embodiment> In the first embodiment, a case where whether or not to perform DoH is set for each application is exemplified. In the second embodiment, a case where whether or not to perform DoH is set for each protocol is described. Note that the hardware configuration and software configuration in the second embodiment are the same as those in the first embodiment, and therefore the description is omitted.
[0054] Fig. 7 is a diagram for explaining the exception setting of DoH in the second embodiment. Fig. 7(A) is an example of a screen displayed in place of Fig. 5(A) in the first embodiment. Fig. 7(B) is an example of a setting value stored in the setting value DB 1050 in the second embodiment.
[0055] 4 has been selected, the CPU 111 of the MFP 101 transitions the screen displayed on the operation unit 116 to a setting screen 700. The settings related to the exception host names shown in an area 702 are the same as those in the first embodiment, and therefore will not be described here.
[0056] In the area 701, communication protocols used by the MFP 101 are listed. The user can set communication protocols to be exceptions by performing a touch operation on the area 701. Here, a case where SMB and FTP / SFTP are set as the communication protocols to be exceptions is illustrated. For example, an administrator can set the communication protocols to be used exclusively when communicating with a server on a local zone not to use DoH, taking into account the user's usage history. When the control unit 1040a detects that the enter key is pressed after a setting operation is performed via the screen 500, the control unit 1040a stores the setting performed via the screen in the setting value DB 1050 as the operation setting of the MFP 101. The setting of the exception application and the exception host name performed by the user operation via FIG. 7(A) is stored in the setting value DB 1050 as the operation setting of the MFP 101. FIG. 7(B) is an example of the operation setting related to the name resolution performed via FIG. 4 and FIG. 7(A).
[0057] Specific control in the second embodiment will be described with reference to the flowchart in Fig. 8. Each operation (step) shown in the flowchart in Fig. 8 is realized by CPU 111 calling up to RAM 113 a program for implementing each control module stored in ROM 112 or storage 114 and executing the program. As in the first embodiment, data transmission and reception processing is implemented in cooperation with network I / F 121, and in cases where it is desired to clarify the subject of processing, the description will be given with the software module as the subject.
[0058] Since steps S801 and S802 are similar to steps S601 and S602 in the first embodiment, the description thereof will be omitted.
[0059] In S803, the control unit 1040 identifies a communication protocol corresponding to the host name requested for name resolution, and determines whether or not the communication protocol is designated as an exception protocol. If it is designated as an exception protocol, the process proceeds to S806, and if it is not designated, the process proceeds to S804. The communication protocol is identified in the same manner as in the first embodiment, and the requesting application may be configured to call an API function for name resolution with the type of communication protocol set as an argument, and notify the control unit 1040 of the communication protocol.
[0060] The subsequent name resolution processing using DoH or DNS in S804 to S809 is similar to that in the first embodiment, and therefore a description thereof will be omitted.
[0061] As described above, in the second embodiment, it becomes possible to flexibly switch between attempting name resolution using DoH or performing conventional plaintext name resolution without attempting DoH, based on the settings of the exception protocols and the settings of the exception host names.
[0062] <Third embodiment> In the first and second embodiments, a case where the setting of whether or not to perform name resolution by DoH is performed via a network setting screen has been described as an example. Here, a communication device such as an MFP has a wide variety of settings, and even a user such as a network administrator who is familiar with networks may miss settings or make setting mistakes.
[0063] In view of this, MFP 101 is provided with a function for setting a security policy that collectively changes multiple security-related settings, such as network settings for direct connection and the number of digits in an authenticated user's password and lockout settings. In the third embodiment, in addition to the setting control described in the first and second embodiments, it is possible to change the setting as to whether or not encryption is used for name resolution via a screen for setting a security policy. This will be specifically described below.
[0064] FIG. 9 is an example of a screen 900 for setting a security policy displayed on the operation unit 116. In this embodiment, whether or not encrypted communication is used for name resolution can be set from the screen for setting the operational policy of communication. A check box 901 is a display item selected when encrypted communication is used for name resolution. The user can also set other operational policies via FIG. 9. When a policy is set such that a server certificate must be verified during TLS communication, a setting is made to block TLS communication using a self-signed certificate or an expired certificate. In addition, individual settings of the pull print application 1010c, etc. are also changed to a setting that requires verification of the certificate when communicating with the print server. In addition, when a policy is set to prohibit plaintext authentication in the server function, multiple setting values of the MFP 101 are changed to uniformly prohibit the use of plaintext authentication and server functions that use plaintext authentication.
[0065] A specific control in the third embodiment will be described with reference to the flowchart in Fig. 10. Each operation (step) shown in the flowchart in Fig. 10 is realized by the CPU 111 calling up into the RAM 113 a program for implementing each control module stored in the ROM 112 or the storage 114 and executing the program. Note that, as in the first embodiment, data transmission and reception processing and the like are realized in cooperation with the network I / F 121.
[0066] In S1001, the CPU 111 determines whether or not a user operation to reflect a change in the policy settings has been accepted. If a user operation to reflect a change in the policy settings has been accepted, the process proceeds to S1002, and if not, the process waits for the setting change. A user operation to reflect a change in the policy settings is, for example, a user operation to press the enter key on the screen 900.
[0067] In S1002, the CPU 111 determines whether or not a policy that uses encrypted communication for name resolution is specified. If a policy that uses encrypted communication for name resolution is specified, the process proceeds to S1003, and if not, the process proceeds to S1006.
[0068] In S1003, the CPU 111 changes the setting value stored in the setting value DB 1050 to an operation setting that uses DoH. Specifically, the CPU 111 sets the setting for automatic acquisition of the DoH server address to be enabled, and changes the setting for using DoH to be enabled. The setting for the port filter (not shown) is also changed to a setting that allows communication on port 443, which is necessary for HTTPS communication. Note that, although the case where automatic acquisition is enabled is exemplified in this embodiment, the present invention is not limited to this. If the address of the DoH server has already been manually input, control may be performed to maintain the setting that disables automatic acquisition rather than enabling automatic acquisition.
[0069] Next, in S1004, the CPU 111 determines whether communication with the DoH server is possible with the current operation setting values. Specifically, an attempt is made to establish an encrypted communication path with the DoH server, and whether encrypted communication can be established is confirmed. In addition, an attempt is made to determine whether name resolution can actually be performed by the DoH server, and if name resolution is possible, it may be determined that communication is possible.
[0070] If it is determined that communication is possible, the process proceeds to S1006, and if it is determined that communication is not possible, the process proceeds to S1005. In S1005, the CPU 111 displays an error screen on the operation unit 116. The error screen displays an error message indicating the reason for the error. The error screen may also be configured to display a display item for transitioning the screen displayed on the operation unit 116 to a DNS setting screen. This display item is useful for the user to manually set the DoH server address in cases where the address of the DoH server could not be automatically acquired.
[0071] In S1006, the CPU 111 determines whether or not an operation to designate another policy as valid has been accepted. If an operation to designate another policy as valid has been accepted, the process proceeds to S1007. On the other hand, if an operation to designate another policy as valid has not been accepted, the process ends.
[0072] In S1007, the CPU 111 changes the operation setting values of the MFP 101 based on other policies that have been designated as valid, and ends the series of processes.
[0073] The above-described process makes it easier to switch the DoH setting that affects all the functions of the MFP 101 to enabled.
[0074] <Modification> In addition to the control of the first embodiment, the control of the second embodiment may be performed. In this case, the administrator or the like can set the application, communication protocol, and host name as exception settings. In this case, after the judgment step of S603, the judgment process shown in the judgment step of S803 may be further performed.
[0075] In the first and second embodiments, the case where an exception application or an exception protocol that is an exception to the name resolution by DoH is selected by a user such as an administrator is exemplified. However, the setting method of whether to use the name resolution using DoH or to use the conventional plain text name resolution can be appropriately modified. For example, an application or a communication protocol that should use the name resolution by DoH can be selected. In this case, a target application list that lists applications that should use the name resolution by DoH and a target protocol list that lists communication applications that should use the name resolution by DoH are stored in the setting value DB1050. In this case, instead of the process of S603 in the first embodiment, a process of determining whether the application of the request source is included in the target application list is performed. If the application of the request source is included in the target application list, the process may proceed to S604, and if not, the process may proceed to S606. Similarly, in the second embodiment, instead of the process of S803, a process of determining whether the communication protocol corresponding to the host name is included in the target protocol list is performed.
[0076] Furthermore, the selection method can be modified as illustrated in FIG. 11. FIGS. 11A and 11B show modified examples displayed instead of the screen 500. A setting area 1101 is displayed on the screen 1100 for selecting whether to use DNS or DoH for each application. The user can determine whether to use DoH or DNS for each application that the MFP 101 has via the screen. The control unit 1040 of the MFP 101 generates the above-mentioned exception application list based on the setting made via the screen and stores it in the setting value DB 1050. In the screen 1101, it is clearly indicated in parentheses that DNS is plain text and DoH is encrypted. Therefore, a user such as an administrator can intuitively determine whether to desire plain text name resolution or highly secure name resolution by DoH for each application.
[0077] Furthermore, the selection method can be modified as shown in screen 1110. Area 1111 is a display area in which the main communication partner is selected for each application by one of two options. The administrator can select "Intranet" for an application whose main communication partner is the local zone in which MFP 101 is installed. For example, the administrator can specify the local zone for a pull print application that communicates with print server 105 installed in the local zone. On the other hand, the administrator can select "Internet" for an application whose main communication partner is a server on the Internet.
[0078] Also, screen 1110 displays a message indicating that if intranet is specified as the main use, priority will be given to name resolution using a plaintext DNS server, even if the setting is set to use DoH.
[0079] When this selection method is changed, the control unit 1040 of the MFP 101 generates an exception application list that lists applications whose main communication partner is specified as “intranet” based on the settings made via the screen, and stores the list in the setting value DB 1050.
[0080] The modified example described in Fig. 11 can also be applied to the second embodiment. In this case, the selection method for each communication protocol used in MFP 101 can be modified to the selection method exemplified in Fig. 11. In this case, the method of generating the exception protocol list stored in setting value DB 1050 is similar to the method of generating the exception application list, and therefore description thereof will be omitted.
[0081] Finally, in this embodiment, DoH is exemplified as an example of a method using encrypted communication for name resolution, but the present invention is not limited to this. It can also be applied to a case where DoT (DNS Over TLS) is used, in which only the communication path is encrypted with TLS and plaintext DNS packets are transmitted over the communication path.
[0082] <Other embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of each of the above-mentioned embodiments to a system or device via a network or a storage medium, and having one or more processors in a computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC or FPGA) that realizes one or more functions. [Explanation of symbols]
[0083] 101 MFP 111 CPU 121 Network Interface
Claims
1. 1. A communication device, comprising: a setting means for setting whether or not encrypted communication is to be used for name resolution as an operation setting of the communication device; a communication control means for controlling, when performing name resolution of a host name requested by an application, to request the first DNS server to resolve the host name via an encrypted communication path established with a first DNS server based at least on the setting means being set to use the encrypted communication, and to request the second DNS server to resolve the host name in plain text based on the setting means being set to not use the encrypted communication; a receiving means for receiving a designation of an application to be excluded from the target of the name resolution using the encrypted communication; a storage means for storing identification information of an application, the designation of which is accepted by the accepting means, the identification information of an application to be excluded from the target of name resolution using the encrypted communication; a determination means for determining whether or not the requesting application is an application that should be subject to name resolution using the encrypted communication based on the identification information stored in the storage means and the type of the requesting application; A sending application that sends scan data to a destination specified by a host name; A web browser application; having When the determination means determines that the requesting application is an application that should not be a target for name resolution using the encrypted communication, the communication control means controls to request the second DNS server to perform name resolution of the host name in plain text even if the setting means has set the encrypted communication to be used; The communication device according to claim 1, wherein the sending application and the Web browser application can be designated as applications to be excluded by the accepting means.
2. 1. A communication device, comprising: a setting means for setting whether or not encrypted communication is to be used for name resolution as an operation setting of the communication device; a communication control means for controlling, when performing name resolution of a host name requested by an application, to request the first DNS server to resolve the host name via an encrypted communication path established with a first DNS server based at least on the setting means being set to use the encrypted communication, and to request the second DNS server to resolve the host name in plain text based on the setting means being set to not use the encrypted communication; a storage means for storing identification information of a communication protocol to be excluded from the target of the name resolution using the encrypted communication; a determination means for determining whether or not the communication protocol of the requesting application should be the target of the name resolution using the encrypted communication based on the identification information stored in the storage means and the type of the communication protocol used for communication with the other party specified by the host name; having A communication device characterized in that, when the determination means determines that the requesting application is a communication protocol that should not be subject to name resolution using encrypted communication, the communication control means controls the second DNS server to request name resolution of the host name in plain text, even if the setting means is set to use encrypted communication.
3. The method further includes a receiving unit for receiving a designation of a communication protocol to be excluded from the target of the name resolution using the encrypted communication, 3. The communication device according to claim 2, wherein said storage means stores identification information of a communication protocol designated and accepted by said acceptance means.
4. 4. The communication device according to claim 3, wherein the accepting means is capable of designating at least FTP (File Transfer Protocol) as the communication protocol to be excluded.
5. the storage means further stores a list of host names to be excluded from targets of name resolution using the encrypted communication, The communication device according to any one of claims 1 to 4, characterized in that, when the host name requested for name resolution is included in the list of excluded host names stored in the storage means, the communication control means controls the second DNS server to request name resolution of the host name in plain text, regardless of the settings made by the setting means.
6. A method for controlling a communication device, comprising: a setting step of setting whether or not encrypted communication is to be used for name resolution as an operation setting of the communication device; a communication control step of, when performing name resolution of a host name requested by an application, changing whether to request the first DNS server to resolve the host name via an encrypted communication path established with the first DNS server or to request the second DNS server to resolve the host name in plain text, based on the setting made in the setting step; a receiving step of receiving a designation of an application to be excluded from the target of the name resolution using the encrypted communication; a storage step of storing in a storage means identification information of the application whose designation has been accepted in the accepting step, the identification information of the application to be excluded from the target of the name resolution using the encrypted communication; a determination step of determining whether or not the requesting application is an application that should be subject to name resolution using the encrypted communication based on the identification information stored in the storage means and the type of the requesting application; having When it is determined by the determination step that the requesting application is an application that should not be a target for name resolution using the encrypted communication, the communication control step controls to request the second DNS server to perform name resolution of the host name in plain text even if the setting step has been set to use the encrypted communication; A control method characterized in that a transmission application that transmits scan data to a destination specified by a host name and a web browser application, which are applications that can be operated on the communication device, can be specified as applications to be excluded in the reception process.
7. A method for controlling a communication device, comprising: a setting step of setting whether or not encrypted communication is to be used for name resolution as an operation setting of the communication device; a communication control step of controlling, when performing name resolution of a host name requested by an application, to request the first DNS server to resolve the host name via an encrypted communication path established with a first DNS server based at least on the setting that the encrypted communication is used in the setting step, and to request the second DNS server to resolve the host name in plain text based on the setting that the encrypted communication is not used in the setting step; a storage step of storing, in a storage means, identification information of a communication protocol to be excluded from the target of the name resolution using the encrypted communication; a determination step of determining whether or not the communication protocol of the requesting application should be the target of the name resolution using the encrypted communication based on the identification information stored in the storage means and the type of the communication protocol used for communication with the other party specified by the host name; having A communication device characterized in that, when the determination process determines that the requesting application is a communication protocol that should not be subject to name resolution using encrypted communication, the communication control process controls the second DNS server to request name resolution of the host name in plain text, even if the setting process has been set to use encrypted communication.
8. A program for causing at least one computer to function as each of the means of a communication device described in any one of claims 1 to 5.
Citation Information
Patent Citations
Communication apparatus, DNS processing method and program
JP2017139648A
Encrypted communication method
WO2005069532A1
