US8566582B2 - System and method for searching and retrieving certificates - Google Patents

System and method for searching and retrieving certificates Download PDF

Info

Publication number
US8566582B2
US8566582B2 US13/483,216 US201213483216A US8566582B2 US 8566582 B2 US8566582 B2 US 8566582B2 US 201213483216 A US201213483216 A US 201213483216A US 8566582 B2 US8566582 B2 US 8566582B2
Authority
US
United States
Prior art keywords
certificate
mobile device
certificates
already stored
servers
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.)
Active
Application number
US13/483,216
Other versions
US20120239927A1 (en
Inventor
Neil Patrick Adams
Michael Stephen Brown
Herbert Anthony Little
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Malikie Innovations Ltd
Original Assignee
BlackBerry Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by BlackBerry Ltd filed Critical BlackBerry Ltd
Priority to US13/483,216 priority Critical patent/US8566582B2/en
Assigned to RESEARCH IN MOTION LIMITED reassignment RESEARCH IN MOTION LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ADAMS, NEIL P., LITTLE, HERBERT A., BROWN, MICHAEL S.
Publication of US20120239927A1 publication Critical patent/US20120239927A1/en
Assigned to BLACKBERRY LIMITED reassignment BLACKBERRY LIMITED CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: RESEARCH IN MOTION LIMITED
Application granted granted Critical
Publication of US8566582B2 publication Critical patent/US8566582B2/en
Assigned to MALIKIE INNOVATIONS LIMITED reassignment MALIKIE INNOVATIONS LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BLACKBERRY LIMITED
Assigned to MALIKIE INNOVATIONS LIMITED reassignment MALIKIE INNOVATIONS LIMITED NUNC PRO TUNC ASSIGNMENT (SEE DOCUMENT FOR DETAILS). Assignors: BLACKBERRY LIMITED
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823Network architectures or network communication protocols for network security for authentication of entities using certificates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3263Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
    • H04L9/3265Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate chains, trees or paths; Hierarchical trust model
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80Wireless

Definitions

  • the invention relates generally to the processing of messages, such as e-mail messages, and more specifically to a system and method for searching and retrieving certificates used in the processing of encoded messages.
  • Electronic mail (“e-mail”) messages may be encoded using one of a number of known protocols. Some of these protocols, such as Secure Multiple Internet Mail Extensions (“S/MIME”) for example, rely on public and private encryption keys to provide confidentiality and integrity, and on a Public Key Infrastructure (PKI) to communicate information that provides authentication and authorization. Data encrypted using a private key of a private key/public key pair can only be decrypted using the corresponding public key of the pair, and vice-versa. The authenticity of public keys used in the encoding of messages is validated using certificates. In particular, if a user of a computing device wishes to encrypt a message before the message is sent to a particular individual, the user will require a certificate for that individual. That certificate will typically comprise the public key of the individual, as well as other identification-related information.
  • S/MIME Secure Multiple Internet Mail Extensions
  • PKI Public Key Infrastructure
  • Searching for and retrieving a certificate for a specific recipient is a process that generally involves querying a certificate server by having the user manually enter the name and/or e-mail address of the intended recipient in a search form displayed on the computing device.
  • certificates located in the search are then temporarily downloaded to the computing device for consideration, and a list of located certificates may then be displayed to the user. Selected certificates in the list may then be manually identified by a user for storage in a non-volatile store of the computing device, for potential future use.
  • only certain data needed to generate a list of certificates located in the search may be initially downloaded to the computing device.
  • the list is displayed to a user, typically identifying each located certificate using the common name and e-mail address of the individual to whom the respective certificate has been issued. Only after the user selects specific certificates from the list to be stored for future use are the certificates downloaded to the computing device for storage.
  • the computing device is a mobile device, deferring the downloading of certificates to the mobile device, and only downloading the user-selected certificates, can significantly minimize waste of resources.
  • Embodiments of the invention are generally directed to a system and method for more efficiently searching certificates on a computing device and retrieving certificates for storage on the computing device.
  • a method of searching and retrieving certificates comprising the steps of: receiving a certificate search request; performing a search on one or more certificate servers, wherein at least one query is submitted to the one or more certificate servers to request retrieval of certificates satisfying the certificate search request; retrieving at least one certificate from the one or more certificate servers; processing each certificate retrieved at a first computing device to determine search result data, wherein the search result data comprises data that uniquely identifies the respective certificate; and for each certificate retrieved, communicating search result data associated therewith to a second device from the first computing device, for use in determining whether the respective certificate is stored on the second device.
  • the data that uniquely identifies each respective certificate comprises serial number and issuer data for the respective certificate
  • the processing step comprises parsing each certificate retrieved to obtain the respective serial number and issuer data
  • the data that uniquely identifies each respective certificate comprises a hash of at least a part of the respective certificate
  • the processing step comprises applying a hash algorithm to each certificate retrieved to obtain the respective hash
  • a system for searching and retrieving certificates comprising at least a first computing device and a second device, wherein the first computing device is adapted to: receive a certificate search request; perform a search on one or more certificate servers by submitting at least one query thereto to request retrieval of certificates satisfying the certificate search request; retrieve at least one certificate from the one or more certificate servers; process each certificate retrieved to determine search result data, wherein the search result data comprises data that uniquely identifies the respective certificate; and for each certificate retrieved, communicate search result data associated therewith to a second device for use in determining whether the respective certificate is stored on the second device.
  • FIG. 1 is a block diagram of a mobile device in one example implementation
  • FIG. 2 is a block diagram of a communication subsystem component of the mobile device of FIG. 1 ;
  • FIG. 3 is a block diagram of a node of a wireless network
  • FIG. 4 is a block diagram illustrating components of a host system in one example configuration
  • FIG. 5 is a block diagram showing an example of a certificate chain
  • FIG. 6 is a block diagram illustrating components of an example of an encoded message
  • FIG. 7A is a flowchart illustrating steps in a method of searching and retrieving certificates in an embodiment of the invention.
  • FIG. 7B is a flowchart illustrating steps in a method of searching and retrieving certificates in another embodiment of the invention.
  • a mobile station is a two-way communication device with advanced data communication capabilities having the capability to communicate with other computer systems, and is also referred to herein generally as a mobile device.
  • a mobile device may also include the capability for voice communications.
  • it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities).
  • a mobile device communicates with other devices through a network of transceiver stations.
  • FIGS. 1 through 3 To aid the reader in understanding the structure of a mobile device and how it communicates with other devices, reference is made to FIGS. 1 through 3 .
  • Mobile device 100 comprises a number of components, the controlling component being microprocessor 102 .
  • Microprocessor 102 controls the overall operation of mobile device 100 .
  • Communication functions, including data and voice communications, are performed through communication subsystem 104 .
  • Communication subsystem 104 receives messages from and sends messages to a wireless network 200 .
  • communication subsystem 104 is configured in accordance with the Global System for Mobile Communication (GSM) and General Packet Radio Services (GPRS) standards.
  • GSM Global System for Mobile Communication
  • GPRS General Packet Radio Services
  • the GSM/GPRS wireless network is used worldwide and it is expected that these standards will be superseded eventually by Enhanced Data GSM Environment (EDGE) and Universal Mobile Telecommunications Service (UMTS). New standards are still being defined, but it is believed that they will have similarities to the network behaviour described herein, and it will also be understood by persons skilled in the art that the invention is intended to use any other suitable standards that are developed in the future.
  • the wireless link connecting communication subsystem 104 with network 200 represents one or more different Radio Frequency (RF) channels, operating according to defined protocols specified for GSM/GPRS communications. With newer network protocols, these channels are capable of supporting both circuit switched voice communications and packet switched data communications.
  • RF Radio Frequency
  • wireless network associated with mobile device 100 is a GSM/GPRS wireless network in one example implementation of mobile device 100
  • other wireless networks may also be associated with mobile device 100 in variant implementations.
  • Different types of wireless networks that may be employed include, for example, data-centric wireless networks, voice-centric wireless networks, and dual-mode networks that can support both voice and data communications over the same physical base stations.
  • Combined dual-mode networks include, but are not limited to, Code Division Multiple Access (CDMA) or CDMA2000 networks, GSM/GPRS networks (as mentioned above), and future third-generation (3G) networks like EDGE and UMTS.
  • CDMA Code Division Multiple Access
  • GSM/GPRS networks as mentioned above
  • 3G third-generation
  • Some older examples of data-centric networks include the MobitexTM Radio Network and the DataTACTM Radio Network.
  • Examples of older voice-centric data networks include Personal Communication Systems (PCS) networks like GSM and Time Division Multiple Access (TDMA) systems.
  • PCS Personal Communication Systems
  • TDMA Time Division Multiple Access
  • Microprocessor 102 also interacts with additional subsystems such as a Random Access Memory (RAM) 106 , flash memory 108 , display 110 , auxiliary input/output (I/O) subsystem 112 , serial port 114 , keyboard 116 , speaker 118 , microphone 120 , short-range communications subsystem 122 and other devices 124 .
  • RAM Random Access Memory
  • I/O auxiliary input/output subsystem 112
  • serial port 114 serial port 114
  • keyboard 116 keyboard 116
  • speaker 118 microphone 120
  • short-range communications subsystem 122 short-range communications subsystem 122 and other devices 124 .
  • Some of the subsystems of mobile device 100 perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions.
  • display 110 and keyboard 116 may be used for both communication-related functions, such as entering a text message for transmission over network 200 , and device-resident functions such as a calculator or task list.
  • Operating system software used by microprocessor 102 is typically stored in a persistent store such as flash memory 108 , which may alternatively be a read-only memory (ROM) or similar storage element (not shown).
  • ROM read-only memory
  • RAM 106 volatile store
  • Mobile device 100 may send and receive communication signals over network 200 after required network registration or activation procedures have been completed.
  • Network access is associated with a subscriber or user of a mobile device 100 .
  • mobile device 100 To identify a subscriber, mobile device 100 requires a Subscriber Identity Module or “SIM” card 126 to be inserted in a SIM interface 128 in order to communicate with a network.
  • SIM 126 is one type of a conventional “smart card” used to identify a subscriber of mobile device 100 and to personalize the mobile device 100 , among other things. Without SIM 126 , mobile device 100 is not fully operational for communication with network 200 . By inserting SIM 126 into SIM interface 128 , a subscriber can access all subscribed services.
  • SIM 126 includes a processor and memory for storing information. Once SIM 126 is inserted in SIM interface 128 , it is coupled to microprocessor 102 . In order to identify the subscriber, SIM 126 contains some user parameters such as an International Mobile Subscriber Identity (IMSI).
  • IMSI International Mobile Subscriber Identity
  • An advantage of using SIM 126 is that a subscriber is not necessarily bound by any single physical mobile device. SIM 126 may store additional subscriber information for a mobile device as well, including datebook (or calendar) information and recent call information.
  • Mobile device 100 is a battery-powered device and includes a battery interface 132 for receiving one or more rechargeable batteries 130 .
  • Battery interface 132 is coupled to a regulator (not shown), which assists battery 130 in providing power V+ to mobile device 100 .
  • a regulator not shown
  • future technologies such as micro fuel cells may provide the power to mobile device 100 .
  • Microprocessor 102 in addition to its operating system functions, enables execution of software applications on mobile device 100 .
  • a set of applications that control basic device operations, including data and voice communication applications, will normally be installed on mobile device 100 during its manufacture.
  • Another application that may be loaded onto mobile device 100 would be a personal information manager (PIM).
  • PIM has functionality to organize and manage data items of interest to a subscriber, such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items.
  • a PIM application has the ability to send and receive data items via wireless network 200 .
  • PIM data items may be seamlessly integrated, synchronized, and updated via wireless network 200 with the mobile device subscriber's corresponding data items stored and/or associated with a host computer system. This functionality creates a mirrored host computer on mobile device 100 with respect to such items. This can be particularly advantageous where the host computer system is the mobile device subscriber's office computer system.
  • Additional applications may also be loaded onto mobile device 100 through network 200 , auxiliary I/O subsystem 112 , serial port 114 , short-range communications subsystem 122 , or any other suitable subsystem 124 .
  • This flexibility in application installation increases the functionality of mobile device 100 and may provide enhanced on-device functions, communication-related functions, or both.
  • secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using mobile device 100 .
  • Serial port 114 enables a subscriber to set preferences through an external device or software application and extends the capabilities of mobile device 100 by providing for information or software downloads to mobile device 100 other than through a wireless communication network.
  • the alternate download path may, for example, be used to load an encryption key onto mobile device 100 through a direct and thus reliable and trusted connection to provide secure device communication.
  • Short-range communications subsystem 122 provides for communication between mobile device 100 and different systems or devices, without the use of network 200 .
  • subsystem 122 may include an infrared device and associated circuits and components for short-range communication. Examples of short range communication would include standards developed by the Infrared Data Association (IrDA), Bluetooth, and the 802.11 family of standards developed by IEEE.
  • IrDA Infrared Data Association
  • Bluetooth Bluetooth
  • 802.11 family of standards developed by IEEE IEEE
  • a received signal such as a text message, an e-mail message, or web page download will be processed by communication subsystem 104 and input to microprocessor 102 .
  • Microprocessor 102 will then process the received signal for output to display 110 or alternatively to auxiliary I/O subsystem 112 .
  • a subscriber may also compose data items, such as e-mail messages, for example, using keyboard 116 in conjunction with display 110 and possibly auxiliary I/O subsystem 112 .
  • Auxiliary subsystem 112 may include devices such as: a touch screen, mouse, track ball, infrared fingerprint detector, or a roller wheel with dynamic button pressing capability.
  • Keyboard 116 is an alphanumeric keyboard and/or telephone-type keypad.
  • a composed item may be transmitted over network 200 through communication subsystem 104 .
  • mobile device 100 For voice communications, the overall operation of mobile device 100 is substantially similar, except that the received signals would be output to speaker 118 , and signals for transmission would be generated by microphone 120 .
  • Alternative voice or audio I/O subsystems such as a voice message recording subsystem, may also be implemented on mobile device 100 .
  • voice or audio signal output is accomplished primarily through speaker 118
  • display 110 may also be used to provide additional information such as the identity of a calling party, duration of a voice call, or other voice call related information.
  • Communication subsystem 104 comprises a receiver 150 , a transmitter 152 , one or more embedded or internal antenna elements 154 , 156 , Local Oscillators (LOs) 158 , and a processing module such as a Digital Signal Processor (DSP) 160 .
  • LOs Local Oscillators
  • DSP Digital Signal Processor
  • communication subsystem 104 The particular design of communication subsystem 104 is dependent upon the network 200 in which mobile device 100 is intended to operate, thus it should be understood that the design illustrated in FIG. 2 serves only as one example.
  • Signals received by antenna 154 through network 200 are input to receiver 150 , which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and analog-to-digital (A/D) conversion.
  • A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in DSP 160 .
  • signals to be transmitted are processed, including modulation and encoding, by DSP 160 .
  • DSP-processed signals are input to transmitter 152 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over network 200 via antenna 156 .
  • DSP 160 not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in receiver 150 and transmitter 152 may be adaptively controlled through automatic gain control algorithms implemented in DSP 160 .
  • the wireless link between mobile device 100 and a network 200 may contain one or more different channels, typically different RF channels, and associated protocols used between mobile device 100 and network 200 .
  • a RF channel is a limited resource that must be conserved, typically due to limits in overall bandwidth and limited battery power of mobile device 100 .
  • transmitter 152 When mobile device 100 is fully operational, transmitter 152 is typically keyed or turned on only when it is sending to network 200 and is otherwise turned off to conserve resources. Similarly, receiver 150 is periodically turned off to conserve power until it is needed to receive signals or information (if at all) during designated time periods.
  • network 200 comprises one or more nodes 202 .
  • Mobile device 100 communicates with a node 202 within wireless network 200 .
  • node 202 is configured in accordance with General Packet Radio Service (GPRS) and Global Systems for Mobile (GSM) technologies.
  • GPRS General Packet Radio Service
  • GSM Global Systems for Mobile
  • Node 202 includes a base station controller (BSC) 204 with an associated tower station 206 , a Packet Control Unit (PCU) 208 added for GPRS support in GSM, a Mobile Switching Center (MSC) 210 , a Home Location Register (HLR) 212 , a Visitor Location Registry (VLR) 214 , a Serving GPRS Support Node (SGSN) 216 , a Gateway GPRS Support Node (GGSN) 218 , and a Dynamic Host Configuration Protocol (DHCP) 220 .
  • BSC base station controller
  • PCU Packet Control Unit
  • MSC Mobile Switching Center
  • HLR Home Location Register
  • VLR Visitor Location Registry
  • SGSN Serving GPRS Support Node
  • GGSN Gateway GPRS Support Node
  • DHCP Dynamic Host Configuration Protocol
  • MSC 210 is coupled to BSC 204 and to a landline network, such as a Public Switched Telephone Network (PSTN) 222 to satisfy circuit switched requirements.
  • PSTN Public Switched Telephone Network
  • the connection through PCU 208 , SGSN 216 and GGSN 218 to the public or private network (Internet) 224 (also referred to herein generally as a shared network infrastructure) represents the data path for GPRS capable mobile devices.
  • BSC 204 also contains a Packet Control Unit (PCU) 208 that connects to SGSN 216 to control segmentation, radio channel allocation and to satisfy packet switched requirements.
  • PCU Packet Control Unit
  • HLR 212 is shared between MSC 210 and SGSN 216 . Access to VLR 214 is controlled by MSC 210 .
  • Station 206 is a fixed transceiver station. Station 206 and BSC 204 together form the fixed transceiver equipment.
  • the fixed transceiver equipment provides wireless network coverage for a particular coverage area commonly referred to as a “cell”.
  • the fixed transceiver equipment transmits communication signals to and receives communication signals from mobile devices within its cell via station 206 .
  • the fixed transceiver equipment normally performs such functions as modulation and possibly encoding and/or encryption of signals to be transmitted to the mobile device in accordance with particular, usually predetermined, communication protocols and parameters, under control of its controller.
  • the fixed transceiver equipment similarly demodulates and possibly decodes and decrypts, if necessary, any communication signals received from mobile device 100 within its cell. Communication protocols and parameters may vary between different nodes. For example, one node may employ a different modulation scheme and operate at different frequencies than other nodes.
  • HLR 212 For all mobile devices 100 registered with a specific network, permanent configuration data such as a user profile is stored in HLR 212 .
  • HLR 212 also contains location information for each registered mobile device and can be queried to determine the current location of a mobile device.
  • MSC 210 is responsible for a group of location areas and stores the data of the mobile devices currently in its area of responsibility in VLR 214 .
  • VLR 214 also contains information on mobile devices that are visiting other networks. The information in VLR 214 includes part of the permanent mobile device data transmitted from HLR 212 to VLR 214 for faster access. By moving additional information from a remote HLR 212 node to VLR 214 , the amount of traffic between these nodes can be reduced so that voice and data services can be provided with faster response times and at the same time requiring less use of computing resources.
  • SGSN 216 and GGSN 218 are elements added for GPRS support; namely packet switched data support, within GSM.
  • SGSN 216 and MSC 210 have similar responsibilities within wireless network 200 by keeping track of the location of each mobile device 100 .
  • SGSN 216 also performs security functions and access control for data traffic on network 200 .
  • GGSN 218 provides internetworking connections with external packet switched networks and connects to one or more SGSN's 216 via an Internet Protocol (IP) backbone network operated within the network 200 .
  • IP Internet Protocol
  • a given mobile device 100 must perform a “GPRS Attach” to acquire an IP address and to access data services. This requirement is not present in circuit switched voice channels as Integrated Services Digital Network (ISDN) addresses are used for routing incoming and outgoing calls.
  • ISDN Integrated Services Digital Network
  • GPRS capable networks use private, dynamically assigned IP addresses, thus requiring a DHCP server 220 connected to the GGSN 218 .
  • RADIUS Remote Authentication Dial-In User Service
  • a logical connection is established from a mobile device 100 , through PCU 208 , and SGSN 216 to an Access Point Node (APN) within GGSN 218 .
  • APN represents a logical end of an IP tunnel that can either access direct Internet compatible services or private network connections.
  • the APN also represents a security mechanism for network 200 , insofar as each mobile device 100 must be assigned to one or more APNs and mobile devices 100 cannot exchange data without first performing a GPRS Attach to an APN that it has been authorized to use.
  • the APN may be considered to be similar to an Internet domain name such as “myconnection.wireless.com”.
  • IPsec IP Security
  • VPN Virtual Private Networks
  • PDP Packet Data Protocol
  • network 200 will run an idle timer for each PDP Context to determine if there is a lack of activity.
  • the PDP Context can be deallocated and the IP address returned to the IP address pool managed by DHCP server 220 .
  • Host system 250 will typically be a corporate office or other local area network (LAN), but may instead be a home office computer or some other private system, for example, in variant implementations.
  • host system 250 is depicted as a LAN of an organization to which a user of mobile device 100 belongs.
  • LAN 250 comprises a number of network components connected to each other by LAN connections 260 .
  • a user's desktop computer 262 a with an accompanying cradle 264 for the user's mobile device 100 is situated on LAN 250 .
  • Cradle 264 for mobile device 100 may be coupled to computer 262 a by a serial or a Universal Serial Bus (USB) connection, for example.
  • Other user computers 262 b are also situated on LAN 250 , and each may or may not be equipped with an accompanying cradle 264 for a mobile device.
  • Cradle 264 facilitates the loading of information (e.g.
  • PIM data private symmetric encryption keys to facilitate secure communications between mobile device 100 and LAN 250 ) from user computer 262 a to mobile device 100 , and may be particularly useful for bulk information updates often performed in initializing mobile device 100 for use.
  • the information downloaded to mobile device 100 may include certificates used in the exchange of messages. It will be understood by persons skilled in the art that user computers 262 a , 262 b will typically be also connected to other peripheral devices not explicitly shown in FIG. 4 .
  • Embodiments of the invention relate generally to the processing of messages, such as e-mail messages, and some embodiments relate generally to the communication of such messages to and from mobile device 100 . Accordingly, only a subset of network components of LAN 250 are shown in FIG. 4 for ease of exposition, and it will be understood by persons skilled in the art that LAN 250 will comprise additional components not explicitly shown in FIG. 4 , for this example configuration. More generally, LAN 250 may represent a smaller part of a larger network [not shown] of the organization, and may comprise different components and/or be arranged in different topologies than that shown in the example of FIG. 4 .
  • mobile device 100 communicates with LAN 250 through a node 202 of wireless network 200 and a shared network infrastructure 224 such as a service provider network or the public Internet. Access to LAN 250 may be provided through one or more routers [not shown], and computing devices of LAN 250 may operate from behind a firewall or proxy server 266 .
  • LAN 250 comprises a wireless VPN router [not shown] to facilitate data exchange between the LAN 250 and mobile device 100 .
  • the concept of a wireless VPN router is new in the wireless industry and implies that a VPN connection can be established directly through a specific wireless network to mobile device 100 .
  • IP Internet Protocol
  • IPV6 Internet Protocol Version 6
  • IPV6 Internet Protocol Version 6
  • IPV6 Internet Protocol Version 6
  • Messages intended for a user of mobile device 100 are initially received by a message server 268 of LAN 250 .
  • Such messages may originate from any of a number of sources.
  • a message may have been sent by a sender from a computer 262 b within LAN 250 , from a different mobile device [not shown] connected to wireless network 200 or to a different wireless network, or from a different computing device or other device capable of sending messages, via the shared network infrastructure 224 , and possibly through an application service provider (ASP) or Internet service provider (ISP), for example.
  • ASP application service provider
  • ISP Internet service provider
  • Message server 268 typically acts as the primary interface for the exchange of messages, particularly e-mail messages, within the organization and over the shared network infrastructure 224 . Each user in the organization that has been set up to send and receive messages is typically associated with a user account managed by message server 268 .
  • message server 268 is a Microsoft ExchangeTM Server.
  • LAN 250 may comprise multiple message servers 268 .
  • Message server 268 may also be adapted to provide additional functions beyond message management, including the management of data associated with calendars and task lists, for example.
  • message server 268 When messages are received by message server 268 , they are typically stored in a message store [not explicitly shown], from which messages can be subsequently retrieved and delivered to users. For instance, an e-mail client application operating on a user's computer 262 a may request the e-mail messages associated with that user's account stored on message server 268 . These messages would then typically be retrieved from message server 268 and stored locally on computer 262 a.
  • An e-mail client application operating on mobile device 100 may also request messages associated with the user's account from message server 268 .
  • the e-mail client may be configured (either by the user or by an administrator, possibly in accordance with an organization's information technology (IT) policy) to make this request at the direction of the user, at some pre-defined time interval, or upon the occurrence of some pre-defined event.
  • mobile device 100 is assigned its own e-mail address, and messages addressed specifically to mobile device 100 are automatically redirected to mobile device 100 as they are received by message server 268 .
  • wireless communications support components 270 may be provided.
  • wireless communications support components 270 comprise a message management server 272 , for example.
  • Message management server 272 is used to specifically provide support for the management of messages, such as e-mail messages, that are to be handled by mobile devices.
  • message management server 272 can be used to control when, if, and how messages should be sent to mobile device 100 .
  • Message management server 272 also facilitates the handling of messages composed on mobile device 100 , which are sent to message server 268 for subsequent delivery.
  • message management server 272 may: monitor the user's “mailbox” (e.g. the message store associated with the user's account on message server 268 ) for new e-mail messages; apply user-definable filters to new messages to determine if and how the messages will be relayed to the user's mobile device 100 ; compress and encrypt new messages (e.g. using an encryption technique such as Data Encryption Standard (DES) or Triple DES) and push them to mobile device 100 via the shared network infrastructure 224 and wireless network 200 ; and receive messages composed on mobile device 100 (e.g. encrypted using Triple DES), decrypt and decompress the composed messages, re-format the composed messages if desired so that they will appear to have originated from the user's computer 262 a , and re-route the composed messages to message server 268 for delivery.
  • DES Data Encryption Standard
  • Triple DES Triple DES
  • Certain properties or restrictions associated with messages that are to be sent from and/or received by mobile device 100 can be defined (e.g. by an administrator in accordance with IT policy) and enforced by message management server 272 . These may include whether mobile device 100 may receive encrypted and/or signed messages, minimum encryption key sizes, whether outgoing messages must be encrypted and/or signed, and whether copies of all secure messages sent from mobile device 100 are to be sent to a pre-defined copy address, for example.
  • Message management server 272 may also be adapted to provide other control functions, such as only pushing certain message information or pre-defined portions (e.g. “blocks”) of a message stored on message server 268 to mobile device 100 .
  • message management server 272 is adapted to push only the first part of a message to mobile device 100 , with the part being of a pre-defined size (e.g. 2 KB). The user can then request more of the message, to be delivered in similar-sized blocks by message management server 272 to mobile device 100 , possibly up to a maximum pre-defined message size.
  • message management server 272 facilitates better control over the type of data and the amount of data that is communicated to mobile device 100 , and can help to minimize potential waste of bandwidth or other resources.
  • message management server 272 need not be implemented on a separate physical server in LAN 250 or other network.
  • some or all of the functions associated with message management server 272 may be integrated with message server 268 , or some other server in LAN 250 .
  • LAN 250 may comprise multiple message management servers 272 , particularly in variant implementations where a large number of mobile devices need to be supported.
  • Embodiments of the invention relate generally to the processing of encoded messages, such as e-mail messages that are encrypted and/or signed. While Simple Mail Transfer Protocol (SMTP), RFC822 headers, and Multipurpose Internet Mail Extensions (MIME) body parts may be used to define the format of a typical e-mail message not requiring encoding, Secure/MIME (S/MIME), a version of the MIME protocol, may be used in the communication of encoded messages (i.e. in secure messaging applications). S/MIME enables end-to-end authentication and confidentiality, and protects data integrity and privacy from the time an originator of a message sends a message until it is decoded and read by the message recipient. Other known standards and protocols may be employed to facilitate secure message communication, such as Pretty Good PrivacyTM (PGP), OpenPGP, and others known in the art.
  • PGP Pretty Good PrivacyTM
  • OpenPGP OpenPGP
  • Secure messaging protocols such as S/MIME rely on public and private encryption keys to provide confidentiality and integrity, and on a Public Key Infrastructure (PKI) to communicate information that provides authentication and authorization.
  • PKI Public Key Infrastructure
  • Data encrypted using a private key of a private key/public key pair can only be decrypted using the corresponding public key of the pair, and vice-versa. Private key information is never made public, whereas public key information is shared.
  • a sender wishes to send a message to a recipient in encrypted form
  • the recipient's public key is used to encrypt a message, which can then be decrypted only using the recipient's private key.
  • a one-time session key is generated and used to encrypt the body of a message, typically with a symmetric encryption technique (e.g. Triple DES).
  • the session key is then encrypted using the recipient's public key (e.g. with a public key encryption algorithm such as RSA), which can then be decrypted only using the recipient's private key.
  • the decrypted session key can then be used to decrypt the message body.
  • the message header may be used to specify the particular encryption scheme that must be used to decrypt the message.
  • Other encryption techniques based on public key cryptography may be used in variant implementations. However, in each of these cases, only the recipient's private key may be used to facilitate decryption of the message, and in this way, the confidentiality of messages can be maintained.
  • a sender may sign a message using a digital signature.
  • a digital signature is a digest of the message (e.g. a hash of the message) encrypted using the sender's private key, which can then be appended to the outgoing message.
  • the recipient uses the same technique as the sender (e.g. using the same standard hash algorithm) to obtain a digest of the received message.
  • the recipient also uses the sender's public key to decrypt the digital signature, in order to obtain what should be a matching digest for the received message. If the digests of the received message do not match, this suggests that either the message content was changed during transport and/or the message did not originate from the sender whose public key was used for verification. By verifying a digital signature in this way, authentication of the sender and message integrity can be maintained.
  • An encoded message may be encrypted, signed, or both encrypted and signed.
  • the authenticity of public keys used in these operations is validated using certificates.
  • a certificate is a digital document issued by a certificate authority (CA). Certificates are used to authenticate the association between users and their public keys, and essentially, provides a level of trust in the authenticity of the users' public keys. Certificates contain information about the certificate holder, with certificate contents typically formatted in accordance with an accepted standard (e.g. X.509).
  • Certificate 310 issued to “John Smith” is an example of a certificate issued to an individual, which may be referred to as an end entity certificate.
  • End entity certificate 310 typically identifies the certificate holder 312 (i.e. John Smith in this example) and the issuer of the certificate 314 , and includes a digital signature of the issuer 316 and the certificate holder's public key 318 .
  • Certificate 310 will also typically include other information and attributes that identify the certificate holder (e.g. e-mail address, organization name, organizational unit name, location, etc.).
  • the individual composes a message to be sent to a recipient, it is customary to include that individual's certificate 310 with the message.
  • a public key to be trusted its issuing organization must be trusted.
  • the relationship between a trusted CA and a user's public key can be represented by a series of related certificates, also referred to as a certificate chain.
  • the certificate chain can be followed to determine the validity of a certificate.
  • the recipient of a message purported to be sent by John Smith may wish to verify the trust status of certificate 310 attached to the received message.
  • a recipient's computing device e.g. computer 262 a of FIG. 4
  • the certificate 320 of issuer ABC is obtained, and used to verify that certificate 310 was indeed signed by issuer ABC.
  • Certificate 320 may already be stored in a certificate store on the computing device, or it may need to be retrieved from a certificate source (e.g. LDAP server 284 of FIG. 4 or some other public or private LDAP server). If certificate 320 is already stored in the recipient's computing device and the certificate has been designated as trusted by the recipient, then certificate 310 is considered to be trusted since it chains to a stored, trusted certificate.
  • certificate 330 is also required to verify the trust of certificate 310 .
  • Certificate 330 is self-signed, and is referred to as a “root certificate”. Accordingly, certificate 320 may be referred to as an “intermediate certificate” in certificate chain 300 ; any given certificate chain to a root certificate, assuming a chain to the root certificate can be determined for a particular end entity certificate, may contain zero, one, or multiple intermediate certificates.
  • certificate 330 is a root certificate issued by a trusted source (from a large certificate authority such as Verisign or Entrust, for example), then certificate 310 may be considered to be trusted since it chains to a trusted certificate. The implication is that both the sender and the recipient of the message trust the source of the root certificate 330 . If a certificate cannot be chained to a trusted certificate, the certificate may be considered to be “not trusted”.
  • Certificate servers store information about certificates and lists identifying certificates that have been revoked. These certificate servers can be accessed to obtain certificates and to verify certificate authenticity and revocation status. For example, a Lightweight Directory Access Protocol (LDAP) server may be used to obtain certificates, and an Online Certificate Status Protocol (OCSP) server may be used to verify certificate revocation status.
  • LDAP Lightweight Directory Access Protocol
  • OCSP Online Certificate Status Protocol
  • Standard e-mail security protocols typically facilitate secure message transmission between non-mobile computing devices (e.g. computers 262 a , 262 b of FIG. 4 ; remote desktop devices).
  • mobile device 100 is adapted to store certificates and associated public keys of other individuals. Certificates stored on a user's computer 262 a will typically be downloaded from computer 262 a to mobile device 100 through cradle 264 , for example.
  • Certificates stored on computer 262 a and downloaded to mobile device 100 are not limited to certificates associated with individuals but may also include certificates issued to CAs, for example. Certain certificates stored in computer 262 a and/or mobile device 100 can also be explicitly designated as “trusted” by the user. Accordingly, when a certificate is received by a user on mobile device 100 , it can be verified on mobile device 100 by matching the certificate with one stored on mobile device 100 and designated as trusted, or otherwise determined to be chained to a trusted certificate.
  • Mobile device 100 may also be adapted to store the private key of the public key/private key pair associated with the user, so that the user of mobile device 100 can sign outgoing messages composed on mobile device 100 , and decrypt messages sent to the user encrypted with the user's public key.
  • the private key may be downloaded to mobile device 100 from the user's computer 262 a through cradle 264 , for example.
  • the private key is preferably exchanged between the computer 262 a and mobile device 100 so that the user may share one identity and one method for accessing messages.
  • User computers 262 a , 262 b can obtain certificates from a number of sources, for storage on computers 262 a , 262 b and/or mobile devices (e.g. mobile device 100 ). These certificate sources may be private (e.g. dedicated for use within an organization) or public, may reside locally or remotely, and may be accessible from within an organization's private network or through the Internet, for example.
  • multiple PKI servers 280 associated with the organization reside on LAN 250 .
  • PKI servers 280 include a CA server 282 for issuing certificates, an LDAP server 284 used to search for and download certificates (e.g. for individuals within the organization), and an OCSP server 286 used to verify the revocation status of certificates.
  • Certificates may be retrieved from LDAP server 284 by a user computer 262 a , for example, to be downloaded to mobile device 100 via cradle 264 .
  • LDAP server 284 may be accessed directly (i.e. “over the air” in this context) by mobile device 100 , and mobile device 100 may search for and retrieve individual certificates through a mobile data server 288 .
  • mobile data server 288 may be adapted to allow mobile device 100 to directly query OCSP server 286 to verify the revocation status of certificates.
  • mobile data server 288 need not physically reside on a separate computing device from the other components of LAN 250 , and that mobile data server 288 may be provided on the same computing device as another component of LAN 250 in variant implementations. Furthermore, the functions of mobile data server 288 may be integrated with the functions of another component in LAN 250 (e.g. message management server 272 ) in variant implementations.
  • only selected PKI servers 280 may be made accessible to mobile devices (e.g. allowing certificates to be downloaded only from a user's computer 262 a , 262 b , while allowing the revocation status of certificates to be checked from mobile device 100 ).
  • certain PKI servers 280 may be made accessible only to mobile devices registered to particular users, as specified by an IT administrator, possibly in accordance with an IT policy, for example.
  • Other sources of certificates may include a Windows certificate store, another secure certificate store on or outside LAN 250 , and smart cards, for example.
  • Encoded message 350 typically includes one or more of the following: a header portion 352 , an encoded body portion 354 , optionally one or more encoded attachments 356 , one or more encrypted session keys 358 , and signature and signature-related information 360 .
  • header portion 352 typically includes addressing information such as “To”, “From”, and “CC” addresses, and may also include message length indicators, and sender encryption and signature scheme identifiers, for example.
  • Actual message content normally includes a message body or data portion 354 and possibly one or more attachments 356 , which may be encrypted by the sender using a session key. If a session key was used, it is typically encrypted for each intended recipient using the respective public key for each recipient, and included in the message at 358 . If the message was signed, a signature and signature-related information 360 are also included. This may include the sender's certificate, for example.
  • an encoded message as shown in FIG. 6 is provided by way of example only, and persons skilled in the art will understand that embodiments of the invention will be applicable to encoded messages of other formats.
  • components of an encoded message may appear in a different order than shown in FIG. 6 , and an encoded message may include fewer, additional, or different components, which may depend on whether the encoded message is encrypted, signed or both.
  • Embodiments of the invention are generally directed to a system and method for more efficiently searching certificates on a device and retrieving certificates for storage on the device.
  • the device is a mobile device (e.g. mobile device 100 of FIG. 4 ), and a certificate search application residing and executing on the mobile device is programmed to initiate searches of certificates on one or more certificate servers (e.g. LDAP server 284 of FIG. 4 ).
  • the mobile device searches for and retrieves individual certificates from a certificate server through an intermediate computing device (e.g. mobile data server 288 of FIG. 4 ).
  • a certificate search application on mobile device 100 searches for and retrieves individual certificates from LDAP server 284 through mobile data server 288 .
  • a search request is received by the certificate search application, typically from a user who provides a first name, last name, and e-mail address of an individual for whom the user wishes to locate a certificate.
  • Certain search requests may also be made broader, by constructing search queries where inputting only a few letters of a name will return all certificates issued with a name containing those letters as a prefix, or by otherwise using wild cards or blank entries in input fields to expand a search, for example.
  • the search request is then communicated from mobile device 100 to mobile data server 288 , which then queries LDAP server 284 for the requested certificate(s).
  • located certificates are retrieved by the mobile data server 288 , and specific search result data relating to each retrieved certificate, such as the common name and e-mail address of the individual (or entity) to which the respective certificate is issued, is communicated to the mobile device 100 so that a list can be generated from the search result data for display to the user.
  • the user can then select specific certificates for downloading to and storage on mobile device 100 from the list.
  • the selections are then communicated to mobile data server 288 , from which the selected certificates are downloaded to mobile device 100 .
  • embodiments of the invention relate generally to methods that can facilitate a determination of whether certificates may already be stored on a device (such as mobile device 100 , for example), without requiring the certificates to be downloaded in their entirety to the device.
  • FIG. 7A a flowchart illustrating steps in a method of searching and retrieving certificates in an embodiment of the invention is shown generally as 400 .
  • a first computing device receives a request from a second device to search at least one certificate server for certificates.
  • the first computing device acts as an intermediary between the second device and the at least one certificate server, such as a mobile data server (e.g. mobile data server 288 of FIG. 4 ) in the case where the second device is a mobile device (e.g. mobile device 100 of FIG. 4 ).
  • a certificate server to be searched may be an LDAP server (e.g. LDAP server 284 of FIG. 4 ).
  • the request may comprise data provided by a certificate search application executing and residing on the second device.
  • the data may originate from user input to the certificate search application (e.g. when the search is initiated by a user), or from data generated by an application that initiates the search in variant implementations.
  • the data will typically include at least one name and/or an e-mail address, although it will be understood by persons skilled in the art that a variety of search queries may be constructed without departing from the scope of the invention.
  • first computing device is a mobile data server and the second device is a mobile device.
  • embodiments of the invention described with reference to method 400 or method 400 b of FIG. 7B may be applied to implementations where the first computing device is not a mobile data server but is some other computing device and/or the second device is not a mobile device but is some other computing device.
  • a system architecture comprising first and second devices and at least one certificate server, where data transmissions between the first and second devices is generally more costly (e.g. in terms of time and/or bandwidth) than data transmissions between the first device and the at least one certificate server, may benefit from an application of an embodiment of the invention.
  • the mobile data server queries the at least one certificate server for certificates based on the search request received at step 410 from the certificate search application of the mobile device. Certificates located in the search are retrieved from the at least one certificate server by the mobile data server.
  • the mobile data server returns search result data relating to each located certificate to the certificate search application of the mobile device.
  • the search result data returned typically includes the common name and e-mail address of the individual (or entity) to which the respective certificate is issued.
  • the mobile data server further processes each retrieved certificate, by parsing each retrieved certificate to identify the serial number and issuer of the respective certificate, which is returned as a part of the search result data.
  • the certificates retrieved at step 420 are only stored temporarily until search result data is returned to the mobile device at step 430 , at which time the retrieved certificates are deleted. In other implementations, the certificates retrieved at step 420 may be cached or otherwise more permanently stored (e.g. until a response to the returned search result data is received from the mobile device, or for some pre-determined duration).
  • the certificate search application compares the serial number and issuer data associated with each located certificate to the serial number and issuer data associated with certificates stored on the mobile device in one or more designated certificate stores thereof, to determine whether the respective certificate is already stored on the mobile device.
  • a list of located certificates is generated and displayed to a user of the mobile device.
  • the list is generated from at least a subset of the search result data returned to the mobile device at step 430 .
  • the list may identify each located certificate by the common name and/or e-mail address of the individual (or entity) to which the certificate is issued.
  • an indicator accompanying the respective entry on the list for each located certificate may also be provided, where the indicator indicates whether the respective certificate is already stored on the mobile device, based on determinations made at step 440 . Accordingly, the user need not select certificates for download that are already stored on the mobile device, so that duplicate certificates need not be necessarily downloaded to the mobile device.
  • the indicator may comprise a checked or unchecked box, for example.
  • each entry on the list may be highlighted or non-highlighted depending on the status of the indicator.
  • certificates are selected for download, by the user of the mobile device, for example.
  • step 470 data identifying the selections made at step 460 are received by the mobile data server from the mobile device, and the selected certificates are subsequently returned to the mobile device, typically for storage on the mobile device.
  • the mobile data server it may be necessary for the mobile data server to query a certificate server again for a selected certificate before the certificate is returned to the mobile device [step not shown], in the event that the certificate was not retained by the mobile data server since the previous download.
  • Method 400 b is similar to method 400 , except that the search result data associated with certificates returned by the first computing device to the second device comprises a hash of at least a part of each located certificate.
  • the mobile data server returns search result data relating to each located certificate to the certificate search application of the mobile device.
  • the search result data returned typically includes the common name and e-mail address of the individual (or entity) to which the respective certificate is issued.
  • the mobile data server further processes each retrieved certificate by applying a hash algorithm, to hash at least a part of each retrieved certificate. The hash is then returned as a part of the search result data.
  • the entire certificate is hashed to generate the returned hash.
  • one or more specific parts or fields of a certificate may be hashed to generate the returned hash, although the likelihood that the hash will uniquely and correctly identify an identical certificate may be decreased depending on the parts or fields hashed.
  • the certificate search application generates a hash for each certificate stored on the mobile device in one or more designated certificate stores thereof, and compares each generated hash to the hash associated with each located certificate, in order to determine whether the respective certificate is already stored on the mobile device.
  • the same hash algorithm employed at step 430 b is applied at this step (to the same parts or fields of the stored certificates if the entire certificates are not hashed) in generating the hashes of the stored certificates. Accordingly, if a generated hash of a given certificate matches a hash received from the mobile data server at step 430 b , a match is deemed to have been determined.
  • other data that can be used to uniquely identify a certificate and that may be communicated more efficiently (e.g. in terms of time and/or bandwidth) than communicating the entire certificate may be returned to the second device as part of the search result data, and used to determine if the certificate is already stored on the second device.
  • Embodiments of the invention described above generally allow users to quickly determine which certificate(s) need to be downloaded to their computing device without making costly requests.
  • the certificate search request may not be initiated by a user but may instead be initiated by an application executing on the second device (possibly by the certificate search application or some other application).
  • a list may not be generated for display to a user (e.g. at step 450 of FIGS. 7A and 7B ), and certificates may be automatically designated for download without user intervention after identifying which certificates may have already been stored on the second device (e.g. at step 440 of FIGS. 7A and 7B ).
  • the invention may also be applied to other applications not involving certificates.
  • some of the foregoing techniques may be used to determine if certain contact data records or electronic documents are already stored on a computing device, for example.
  • the steps of a method of searching and retrieving certificates in embodiments of the invention may be provided as executable software instructions stored on computer-readable media, which may include transmission-type media.

Abstract

A system and method for searching and retrieving certificates, which may be used in the processing of encoded messages. In one broad aspect, a method is provided in which a certificate search request is received, a search of one or more certificate servers for certificates satisfying the request is performed, located certificates are retrieved and processed at a first computing device to determine data that uniquely identifies each located certificate, and search result data comprising the determined data is communicated to a second device (e.g. a mobile device) for use in determining whether each located certificate is already stored on the second device.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a continuation of prior U.S. patent application Ser. No. 12/645,003, filed on Dec. 22, 2009, now issued to patent as U.S. Pat. No. 8,209,530, which is a continuation of prior U.S. patent application Ser. No. 10/931,983, filed on Sep. 2, 2004, now issued to patent as U.S. Pat. No. 7,640,428. The entire contents of U.S. patent application Ser. No. 12/645,003 and U.S. patent application Ser. No. 10/931,983 are hereby incorporated by reference.
FIELD OF THE INVENTION
The invention relates generally to the processing of messages, such as e-mail messages, and more specifically to a system and method for searching and retrieving certificates used in the processing of encoded messages.
BACKGROUND OF THE INVENTION
Electronic mail (“e-mail”) messages may be encoded using one of a number of known protocols. Some of these protocols, such as Secure Multiple Internet Mail Extensions (“S/MIME”) for example, rely on public and private encryption keys to provide confidentiality and integrity, and on a Public Key Infrastructure (PKI) to communicate information that provides authentication and authorization. Data encrypted using a private key of a private key/public key pair can only be decrypted using the corresponding public key of the pair, and vice-versa. The authenticity of public keys used in the encoding of messages is validated using certificates. In particular, if a user of a computing device wishes to encrypt a message before the message is sent to a particular individual, the user will require a certificate for that individual. That certificate will typically comprise the public key of the individual, as well as other identification-related information.
If the requisite certificate for the intended recipient is not already stored on the user's computing device, the certificate must first be retrieved. Searching for and retrieving a certificate for a specific recipient is a process that generally involves querying a certificate server by having the user manually enter the name and/or e-mail address of the intended recipient in a search form displayed on the computing device. Generally, certificates located in the search are then temporarily downloaded to the computing device for consideration, and a list of located certificates may then be displayed to the user. Selected certificates in the list may then be manually identified by a user for storage in a non-volatile store of the computing device, for potential future use.
In some implementations, however, instead of temporarily downloading all the certificates located in the search to the computing device in the first instance, only certain data needed to generate a list of certificates located in the search may be initially downloaded to the computing device. The list is displayed to a user, typically identifying each located certificate using the common name and e-mail address of the individual to whom the respective certificate has been issued. Only after the user selects specific certificates from the list to be stored for future use are the certificates downloaded to the computing device for storage. In particular, if the computing device is a mobile device, deferring the downloading of certificates to the mobile device, and only downloading the user-selected certificates, can significantly minimize waste of resources.
Unfortunately, in these implementations where the downloading of certificates is deferred, it is generally not possible to determine with certainty whether any of the certificates identified in the list are already stored in a certificate store of the computing device from only the downloaded data used to generate the list. For example, in order for an application on the computing device to be able to determine with certainty that a given certificate identified in the list is already stored in the certificate store, the actual certificate would typically need to be downloaded to the computing device so that the requisite data needed to make the determination can be obtained. This can be a time-consuming and expensive task (e.g. with respect to bandwidth), and may be wasteful if the downloaded certificate is, in fact, already in the certificate store.
SUMMARY OF THE INVENTION
Embodiments of the invention are generally directed to a system and method for more efficiently searching certificates on a computing device and retrieving certificates for storage on the computing device.
In one broad aspect of the invention, there is provided a method of searching and retrieving certificates comprising the steps of: receiving a certificate search request; performing a search on one or more certificate servers, wherein at least one query is submitted to the one or more certificate servers to request retrieval of certificates satisfying the certificate search request; retrieving at least one certificate from the one or more certificate servers; processing each certificate retrieved at a first computing device to determine search result data, wherein the search result data comprises data that uniquely identifies the respective certificate; and for each certificate retrieved, communicating search result data associated therewith to a second device from the first computing device, for use in determining whether the respective certificate is stored on the second device.
In another broad aspect of the invention, the data that uniquely identifies each respective certificate comprises serial number and issuer data for the respective certificate, and the processing step comprises parsing each certificate retrieved to obtain the respective serial number and issuer data.
In another broad aspect of the invention, the data that uniquely identifies each respective certificate comprises a hash of at least a part of the respective certificate, and the processing step comprises applying a hash algorithm to each certificate retrieved to obtain the respective hash.
In another broad aspect of the invention, there is provided a system for searching and retrieving certificates comprising at least a first computing device and a second device, wherein the first computing device is adapted to: receive a certificate search request; perform a search on one or more certificate servers by submitting at least one query thereto to request retrieval of certificates satisfying the certificate search request; retrieve at least one certificate from the one or more certificate servers; process each certificate retrieved to determine search result data, wherein the search result data comprises data that uniquely identifies the respective certificate; and for each certificate retrieved, communicate search result data associated therewith to a second device for use in determining whether the respective certificate is stored on the second device.
BRIEF DESCRIPTION OF THE DRAWINGS
For a better understanding of embodiments of the invention, and to show more clearly how it may be carried into effect, reference will now be made, by way of example, to the accompanying drawings in which:
FIG. 1 is a block diagram of a mobile device in one example implementation;
FIG. 2 is a block diagram of a communication subsystem component of the mobile device of FIG. 1;
FIG. 3 is a block diagram of a node of a wireless network;
FIG. 4 is a block diagram illustrating components of a host system in one example configuration;
FIG. 5 is a block diagram showing an example of a certificate chain;
FIG. 6 is a block diagram illustrating components of an example of an encoded message;
FIG. 7A is a flowchart illustrating steps in a method of searching and retrieving certificates in an embodiment of the invention; and
FIG. 7B is a flowchart illustrating steps in a method of searching and retrieving certificates in another embodiment of the invention.
DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION
Some embodiments of the invention make use of a mobile station. A mobile station is a two-way communication device with advanced data communication capabilities having the capability to communicate with other computer systems, and is also referred to herein generally as a mobile device. A mobile device may also include the capability for voice communications. Depending on the functionality provided by a mobile device, it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities). A mobile device communicates with other devices through a network of transceiver stations.
To aid the reader in understanding the structure of a mobile device and how it communicates with other devices, reference is made to FIGS. 1 through 3.
Referring first to FIG. 1, a block diagram of a mobile device in one example implementation is shown generally as 100. Mobile device 100 comprises a number of components, the controlling component being microprocessor 102. Microprocessor 102 controls the overall operation of mobile device 100. Communication functions, including data and voice communications, are performed through communication subsystem 104. Communication subsystem 104 receives messages from and sends messages to a wireless network 200. In this example implementation of mobile device 100, communication subsystem 104 is configured in accordance with the Global System for Mobile Communication (GSM) and General Packet Radio Services (GPRS) standards. The GSM/GPRS wireless network is used worldwide and it is expected that these standards will be superseded eventually by Enhanced Data GSM Environment (EDGE) and Universal Mobile Telecommunications Service (UMTS). New standards are still being defined, but it is believed that they will have similarities to the network behaviour described herein, and it will also be understood by persons skilled in the art that the invention is intended to use any other suitable standards that are developed in the future. The wireless link connecting communication subsystem 104 with network 200 represents one or more different Radio Frequency (RF) channels, operating according to defined protocols specified for GSM/GPRS communications. With newer network protocols, these channels are capable of supporting both circuit switched voice communications and packet switched data communications.
Although the wireless network associated with mobile device 100 is a GSM/GPRS wireless network in one example implementation of mobile device 100, other wireless networks may also be associated with mobile device 100 in variant implementations. Different types of wireless networks that may be employed include, for example, data-centric wireless networks, voice-centric wireless networks, and dual-mode networks that can support both voice and data communications over the same physical base stations. Combined dual-mode networks include, but are not limited to, Code Division Multiple Access (CDMA) or CDMA2000 networks, GSM/GPRS networks (as mentioned above), and future third-generation (3G) networks like EDGE and UMTS. Some older examples of data-centric networks include the Mobitex™ Radio Network and the DataTAC™ Radio Network. Examples of older voice-centric data networks include Personal Communication Systems (PCS) networks like GSM and Time Division Multiple Access (TDMA) systems.
Microprocessor 102 also interacts with additional subsystems such as a Random Access Memory (RAM) 106, flash memory 108, display 110, auxiliary input/output (I/O) subsystem 112, serial port 114, keyboard 116, speaker 118, microphone 120, short-range communications subsystem 122 and other devices 124.
Some of the subsystems of mobile device 100 perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions. By way of example, display 110 and keyboard 116 may be used for both communication-related functions, such as entering a text message for transmission over network 200, and device-resident functions such as a calculator or task list. Operating system software used by microprocessor 102 is typically stored in a persistent store such as flash memory 108, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as RAM 106.
Mobile device 100 may send and receive communication signals over network 200 after required network registration or activation procedures have been completed. Network access is associated with a subscriber or user of a mobile device 100. To identify a subscriber, mobile device 100 requires a Subscriber Identity Module or “SIM” card 126 to be inserted in a SIM interface 128 in order to communicate with a network. SIM 126 is one type of a conventional “smart card” used to identify a subscriber of mobile device 100 and to personalize the mobile device 100, among other things. Without SIM 126, mobile device 100 is not fully operational for communication with network 200. By inserting SIM 126 into SIM interface 128, a subscriber can access all subscribed services. Services could include: web browsing and messaging such as e-mail, voice mail, Short Message Service (SMS), and Multimedia Messaging Services (MMS). More advanced services may include: point of sale, field service and sales force automation. SIM 126 includes a processor and memory for storing information. Once SIM 126 is inserted in SIM interface 128, it is coupled to microprocessor 102. In order to identify the subscriber, SIM 126 contains some user parameters such as an International Mobile Subscriber Identity (IMSI). An advantage of using SIM 126 is that a subscriber is not necessarily bound by any single physical mobile device. SIM 126 may store additional subscriber information for a mobile device as well, including datebook (or calendar) information and recent call information.
Mobile device 100 is a battery-powered device and includes a battery interface 132 for receiving one or more rechargeable batteries 130. Battery interface 132 is coupled to a regulator (not shown), which assists battery 130 in providing power V+ to mobile device 100. Although current technology makes use of a battery, future technologies such as micro fuel cells may provide the power to mobile device 100.
Microprocessor 102, in addition to its operating system functions, enables execution of software applications on mobile device 100. A set of applications that control basic device operations, including data and voice communication applications, will normally be installed on mobile device 100 during its manufacture. Another application that may be loaded onto mobile device 100 would be a personal information manager (PIM). A PIM has functionality to organize and manage data items of interest to a subscriber, such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. A PIM application has the ability to send and receive data items via wireless network 200. PIM data items may be seamlessly integrated, synchronized, and updated via wireless network 200 with the mobile device subscriber's corresponding data items stored and/or associated with a host computer system. This functionality creates a mirrored host computer on mobile device 100 with respect to such items. This can be particularly advantageous where the host computer system is the mobile device subscriber's office computer system.
Additional applications may also be loaded onto mobile device 100 through network 200, auxiliary I/O subsystem 112, serial port 114, short-range communications subsystem 122, or any other suitable subsystem 124. This flexibility in application installation increases the functionality of mobile device 100 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using mobile device 100.
Serial port 114 enables a subscriber to set preferences through an external device or software application and extends the capabilities of mobile device 100 by providing for information or software downloads to mobile device 100 other than through a wireless communication network. The alternate download path may, for example, be used to load an encryption key onto mobile device 100 through a direct and thus reliable and trusted connection to provide secure device communication.
Short-range communications subsystem 122 provides for communication between mobile device 100 and different systems or devices, without the use of network 200. For example, subsystem 122 may include an infrared device and associated circuits and components for short-range communication. Examples of short range communication would include standards developed by the Infrared Data Association (IrDA), Bluetooth, and the 802.11 family of standards developed by IEEE.
In use, a received signal such as a text message, an e-mail message, or web page download will be processed by communication subsystem 104 and input to microprocessor 102. Microprocessor 102 will then process the received signal for output to display 110 or alternatively to auxiliary I/O subsystem 112. A subscriber may also compose data items, such as e-mail messages, for example, using keyboard 116 in conjunction with display 110 and possibly auxiliary I/O subsystem 112. Auxiliary subsystem 112 may include devices such as: a touch screen, mouse, track ball, infrared fingerprint detector, or a roller wheel with dynamic button pressing capability. Keyboard 116 is an alphanumeric keyboard and/or telephone-type keypad. A composed item may be transmitted over network 200 through communication subsystem 104.
For voice communications, the overall operation of mobile device 100 is substantially similar, except that the received signals would be output to speaker 118, and signals for transmission would be generated by microphone 120. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on mobile device 100. Although voice or audio signal output is accomplished primarily through speaker 118, display 110 may also be used to provide additional information such as the identity of a calling party, duration of a voice call, or other voice call related information.
Referring now to FIG. 2, a block diagram of the communication subsystem component 104 of FIG. 1 is shown. Communication subsystem 104 comprises a receiver 150, a transmitter 152, one or more embedded or internal antenna elements 154, 156, Local Oscillators (LOs) 158, and a processing module such as a Digital Signal Processor (DSP) 160.
The particular design of communication subsystem 104 is dependent upon the network 200 in which mobile device 100 is intended to operate, thus it should be understood that the design illustrated in FIG. 2 serves only as one example. Signals received by antenna 154 through network 200 are input to receiver 150, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in DSP 160. In a similar manner, signals to be transmitted are processed, including modulation and encoding, by DSP 160. These DSP-processed signals are input to transmitter 152 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over network 200 via antenna 156. DSP 160 not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in receiver 150 and transmitter 152 may be adaptively controlled through automatic gain control algorithms implemented in DSP 160.
The wireless link between mobile device 100 and a network 200 may contain one or more different channels, typically different RF channels, and associated protocols used between mobile device 100 and network 200. A RF channel is a limited resource that must be conserved, typically due to limits in overall bandwidth and limited battery power of mobile device 100.
When mobile device 100 is fully operational, transmitter 152 is typically keyed or turned on only when it is sending to network 200 and is otherwise turned off to conserve resources. Similarly, receiver 150 is periodically turned off to conserve power until it is needed to receive signals or information (if at all) during designated time periods.
Referring now to FIG. 3, a block diagram of a node of a wireless network is shown as 202. In practice, network 200 comprises one or more nodes 202. Mobile device 100 communicates with a node 202 within wireless network 200. In the example implementation of FIG. 3, node 202 is configured in accordance with General Packet Radio Service (GPRS) and Global Systems for Mobile (GSM) technologies. Node 202 includes a base station controller (BSC) 204 with an associated tower station 206, a Packet Control Unit (PCU) 208 added for GPRS support in GSM, a Mobile Switching Center (MSC) 210, a Home Location Register (HLR) 212, a Visitor Location Registry (VLR) 214, a Serving GPRS Support Node (SGSN) 216, a Gateway GPRS Support Node (GGSN) 218, and a Dynamic Host Configuration Protocol (DHCP) 220. This list of components is not meant to be an exhaustive list of the components of every node 202 within a GSM/GPRS network, but rather a list of components that are commonly used in communications through network 200.
In a GSM network, MSC 210 is coupled to BSC 204 and to a landline network, such as a Public Switched Telephone Network (PSTN) 222 to satisfy circuit switched requirements. The connection through PCU 208, SGSN 216 and GGSN 218 to the public or private network (Internet) 224 (also referred to herein generally as a shared network infrastructure) represents the data path for GPRS capable mobile devices. In a GSM network extended with GPRS capabilities, BSC 204 also contains a Packet Control Unit (PCU) 208 that connects to SGSN 216 to control segmentation, radio channel allocation and to satisfy packet switched requirements. To track mobile device location and availability for both circuit switched and packet switched management, HLR 212 is shared between MSC 210 and SGSN 216. Access to VLR 214 is controlled by MSC 210.
Station 206 is a fixed transceiver station. Station 206 and BSC 204 together form the fixed transceiver equipment. The fixed transceiver equipment provides wireless network coverage for a particular coverage area commonly referred to as a “cell”. The fixed transceiver equipment transmits communication signals to and receives communication signals from mobile devices within its cell via station 206. The fixed transceiver equipment normally performs such functions as modulation and possibly encoding and/or encryption of signals to be transmitted to the mobile device in accordance with particular, usually predetermined, communication protocols and parameters, under control of its controller. The fixed transceiver equipment similarly demodulates and possibly decodes and decrypts, if necessary, any communication signals received from mobile device 100 within its cell. Communication protocols and parameters may vary between different nodes. For example, one node may employ a different modulation scheme and operate at different frequencies than other nodes.
For all mobile devices 100 registered with a specific network, permanent configuration data such as a user profile is stored in HLR 212. HLR 212 also contains location information for each registered mobile device and can be queried to determine the current location of a mobile device. MSC 210 is responsible for a group of location areas and stores the data of the mobile devices currently in its area of responsibility in VLR 214. Further VLR 214 also contains information on mobile devices that are visiting other networks. The information in VLR 214 includes part of the permanent mobile device data transmitted from HLR 212 to VLR 214 for faster access. By moving additional information from a remote HLR 212 node to VLR 214, the amount of traffic between these nodes can be reduced so that voice and data services can be provided with faster response times and at the same time requiring less use of computing resources.
SGSN 216 and GGSN 218 are elements added for GPRS support; namely packet switched data support, within GSM. SGSN 216 and MSC 210 have similar responsibilities within wireless network 200 by keeping track of the location of each mobile device 100. SGSN 216 also performs security functions and access control for data traffic on network 200. GGSN 218 provides internetworking connections with external packet switched networks and connects to one or more SGSN's 216 via an Internet Protocol (IP) backbone network operated within the network 200. During normal operations, a given mobile device 100 must perform a “GPRS Attach” to acquire an IP address and to access data services. This requirement is not present in circuit switched voice channels as Integrated Services Digital Network (ISDN) addresses are used for routing incoming and outgoing calls. Currently, all GPRS capable networks use private, dynamically assigned IP addresses, thus requiring a DHCP server 220 connected to the GGSN 218. There are many mechanisms for dynamic IP assignment, including using a combination of a Remote Authentication Dial-In User Service (RADIUS) server and DHCP server. Once the GPRS Attach is complete, a logical connection is established from a mobile device 100, through PCU 208, and SGSN 216 to an Access Point Node (APN) within GGSN 218. The APN represents a logical end of an IP tunnel that can either access direct Internet compatible services or private network connections. The APN also represents a security mechanism for network 200, insofar as each mobile device 100 must be assigned to one or more APNs and mobile devices 100 cannot exchange data without first performing a GPRS Attach to an APN that it has been authorized to use. The APN may be considered to be similar to an Internet domain name such as “myconnection.wireless.com”.
Once the GPRS Attach is complete, a tunnel is created and all traffic is exchanged within standard IP packets using any protocol that can be supported in IP packets. This includes tunneling methods such as IP over IP as in the case with some IPSecurity (IPsec) connections used with Virtual Private Networks (VPN). These tunnels are also referred to as Packet Data Protocol (PDP) Contexts and there are a limited number of these available in the network 200. To maximize use of the PDP Contexts, network 200 will run an idle timer for each PDP Context to determine if there is a lack of activity. When a mobile device 100 is not using its PDP Context, the PDP Context can be deallocated and the IP address returned to the IP address pool managed by DHCP server 220.
Referring now to FIG. 4, a block diagram illustrating components of a host system in one example configuration is shown. Host system 250 will typically be a corporate office or other local area network (LAN), but may instead be a home office computer or some other private system, for example, in variant implementations. In this example shown in FIG. 4, host system 250 is depicted as a LAN of an organization to which a user of mobile device 100 belongs.
LAN 250 comprises a number of network components connected to each other by LAN connections 260. For instance, a user's desktop computer 262 a with an accompanying cradle 264 for the user's mobile device 100 is situated on LAN 250. Cradle 264 for mobile device 100 may be coupled to computer 262 a by a serial or a Universal Serial Bus (USB) connection, for example. Other user computers 262 b are also situated on LAN 250, and each may or may not be equipped with an accompanying cradle 264 for a mobile device. Cradle 264 facilitates the loading of information (e.g. PIM data, private symmetric encryption keys to facilitate secure communications between mobile device 100 and LAN 250) from user computer 262 a to mobile device 100, and may be particularly useful for bulk information updates often performed in initializing mobile device 100 for use. The information downloaded to mobile device 100 may include certificates used in the exchange of messages. It will be understood by persons skilled in the art that user computers 262 a, 262 b will typically be also connected to other peripheral devices not explicitly shown in FIG. 4.
Embodiments of the invention relate generally to the processing of messages, such as e-mail messages, and some embodiments relate generally to the communication of such messages to and from mobile device 100. Accordingly, only a subset of network components of LAN 250 are shown in FIG. 4 for ease of exposition, and it will be understood by persons skilled in the art that LAN 250 will comprise additional components not explicitly shown in FIG. 4, for this example configuration. More generally, LAN 250 may represent a smaller part of a larger network [not shown] of the organization, and may comprise different components and/or be arranged in different topologies than that shown in the example of FIG. 4.
In this example, mobile device 100 communicates with LAN 250 through a node 202 of wireless network 200 and a shared network infrastructure 224 such as a service provider network or the public Internet. Access to LAN 250 may be provided through one or more routers [not shown], and computing devices of LAN 250 may operate from behind a firewall or proxy server 266.
In a variant implementation, LAN 250 comprises a wireless VPN router [not shown] to facilitate data exchange between the LAN 250 and mobile device 100. The concept of a wireless VPN router is new in the wireless industry and implies that a VPN connection can be established directly through a specific wireless network to mobile device 100. The possibility of using a wireless VPN router has only recently been available and could be used when the new Internet Protocol (IP) Version 6 (IPV6) arrives into IP-based wireless networks. This new protocol will provide enough IP addresses to dedicate an IP address to every mobile device, making it possible to push information to a mobile device at any time. An advantage of using a wireless VPN router is that it could be an off-the-shelf VPN component, not requiring a separate wireless gateway and separate wireless infrastructure to be used. A VPN connection would preferably be a Transmission Control Protocol (TCP)/IP or User Datagram Protocol (UDP)/IP connection to deliver the messages directly to mobile device 100 in this variant implementation.
Messages intended for a user of mobile device 100 are initially received by a message server 268 of LAN 250. Such messages may originate from any of a number of sources. For instance, a message may have been sent by a sender from a computer 262 b within LAN 250, from a different mobile device [not shown] connected to wireless network 200 or to a different wireless network, or from a different computing device or other device capable of sending messages, via the shared network infrastructure 224, and possibly through an application service provider (ASP) or Internet service provider (ISP), for example.
Message server 268 typically acts as the primary interface for the exchange of messages, particularly e-mail messages, within the organization and over the shared network infrastructure 224. Each user in the organization that has been set up to send and receive messages is typically associated with a user account managed by message server 268. One example of a message server 268 is a Microsoft Exchange™ Server. In some implementations, LAN 250 may comprise multiple message servers 268. Message server 268 may also be adapted to provide additional functions beyond message management, including the management of data associated with calendars and task lists, for example.
When messages are received by message server 268, they are typically stored in a message store [not explicitly shown], from which messages can be subsequently retrieved and delivered to users. For instance, an e-mail client application operating on a user's computer 262 a may request the e-mail messages associated with that user's account stored on message server 268. These messages would then typically be retrieved from message server 268 and stored locally on computer 262 a.
When operating mobile device 100, the user may wish to have e-mail messages retrieved for delivery to the handheld. An e-mail client application operating on mobile device 100 may also request messages associated with the user's account from message server 268. The e-mail client may be configured (either by the user or by an administrator, possibly in accordance with an organization's information technology (IT) policy) to make this request at the direction of the user, at some pre-defined time interval, or upon the occurrence of some pre-defined event. In some implementations, mobile device 100 is assigned its own e-mail address, and messages addressed specifically to mobile device 100 are automatically redirected to mobile device 100 as they are received by message server 268.
To facilitate the wireless communication of messages and message-related data between mobile device 100 and components of LAN 250, a number of wireless communications support components 270 may be provided. In this example implementation, wireless communications support components 270 comprise a message management server 272, for example. Message management server 272 is used to specifically provide support for the management of messages, such as e-mail messages, that are to be handled by mobile devices. Generally, while messages are still stored on message server 268, message management server 272 can be used to control when, if, and how messages should be sent to mobile device 100. Message management server 272 also facilitates the handling of messages composed on mobile device 100, which are sent to message server 268 for subsequent delivery.
For example, message management server 272 may: monitor the user's “mailbox” (e.g. the message store associated with the user's account on message server 268) for new e-mail messages; apply user-definable filters to new messages to determine if and how the messages will be relayed to the user's mobile device 100; compress and encrypt new messages (e.g. using an encryption technique such as Data Encryption Standard (DES) or Triple DES) and push them to mobile device 100 via the shared network infrastructure 224 and wireless network 200; and receive messages composed on mobile device 100 (e.g. encrypted using Triple DES), decrypt and decompress the composed messages, re-format the composed messages if desired so that they will appear to have originated from the user's computer 262 a, and re-route the composed messages to message server 268 for delivery.
Certain properties or restrictions associated with messages that are to be sent from and/or received by mobile device 100 can be defined (e.g. by an administrator in accordance with IT policy) and enforced by message management server 272. These may include whether mobile device 100 may receive encrypted and/or signed messages, minimum encryption key sizes, whether outgoing messages must be encrypted and/or signed, and whether copies of all secure messages sent from mobile device 100 are to be sent to a pre-defined copy address, for example.
Message management server 272 may also be adapted to provide other control functions, such as only pushing certain message information or pre-defined portions (e.g. “blocks”) of a message stored on message server 268 to mobile device 100. For example, when a message is initially retrieved by mobile device 100 from message server 268, message management server 272 is adapted to push only the first part of a message to mobile device 100, with the part being of a pre-defined size (e.g. 2 KB). The user can then request more of the message, to be delivered in similar-sized blocks by message management server 272 to mobile device 100, possibly up to a maximum pre-defined message size.
Accordingly, message management server 272 facilitates better control over the type of data and the amount of data that is communicated to mobile device 100, and can help to minimize potential waste of bandwidth or other resources.
It will be understood by persons skilled in the art that message management server 272 need not be implemented on a separate physical server in LAN 250 or other network. For example, some or all of the functions associated with message management server 272 may be integrated with message server 268, or some other server in LAN 250. Furthermore, LAN 250 may comprise multiple message management servers 272, particularly in variant implementations where a large number of mobile devices need to be supported.
Embodiments of the invention relate generally to the processing of encoded messages, such as e-mail messages that are encrypted and/or signed. While Simple Mail Transfer Protocol (SMTP), RFC822 headers, and Multipurpose Internet Mail Extensions (MIME) body parts may be used to define the format of a typical e-mail message not requiring encoding, Secure/MIME (S/MIME), a version of the MIME protocol, may be used in the communication of encoded messages (i.e. in secure messaging applications). S/MIME enables end-to-end authentication and confidentiality, and protects data integrity and privacy from the time an originator of a message sends a message until it is decoded and read by the message recipient. Other known standards and protocols may be employed to facilitate secure message communication, such as Pretty Good Privacy™ (PGP), OpenPGP, and others known in the art.
Secure messaging protocols such as S/MIME rely on public and private encryption keys to provide confidentiality and integrity, and on a Public Key Infrastructure (PKI) to communicate information that provides authentication and authorization. Data encrypted using a private key of a private key/public key pair can only be decrypted using the corresponding public key of the pair, and vice-versa. Private key information is never made public, whereas public key information is shared.
For example, if a sender wishes to send a message to a recipient in encrypted form, the recipient's public key is used to encrypt a message, which can then be decrypted only using the recipient's private key. Alternatively, in some encoding techniques, a one-time session key is generated and used to encrypt the body of a message, typically with a symmetric encryption technique (e.g. Triple DES). The session key is then encrypted using the recipient's public key (e.g. with a public key encryption algorithm such as RSA), which can then be decrypted only using the recipient's private key. The decrypted session key can then be used to decrypt the message body. The message header may be used to specify the particular encryption scheme that must be used to decrypt the message. Other encryption techniques based on public key cryptography may be used in variant implementations. However, in each of these cases, only the recipient's private key may be used to facilitate decryption of the message, and in this way, the confidentiality of messages can be maintained.
As a further example, a sender may sign a message using a digital signature. A digital signature is a digest of the message (e.g. a hash of the message) encrypted using the sender's private key, which can then be appended to the outgoing message. To verify the signature of the message when received, the recipient uses the same technique as the sender (e.g. using the same standard hash algorithm) to obtain a digest of the received message. The recipient also uses the sender's public key to decrypt the digital signature, in order to obtain what should be a matching digest for the received message. If the digests of the received message do not match, this suggests that either the message content was changed during transport and/or the message did not originate from the sender whose public key was used for verification. By verifying a digital signature in this way, authentication of the sender and message integrity can be maintained.
An encoded message may be encrypted, signed, or both encrypted and signed. The authenticity of public keys used in these operations is validated using certificates. A certificate is a digital document issued by a certificate authority (CA). Certificates are used to authenticate the association between users and their public keys, and essentially, provides a level of trust in the authenticity of the users' public keys. Certificates contain information about the certificate holder, with certificate contents typically formatted in accordance with an accepted standard (e.g. X.509).
Consider FIG. 5, in which an example certificate chain 300 is shown. Certificate 310 issued to “John Smith” is an example of a certificate issued to an individual, which may be referred to as an end entity certificate. End entity certificate 310 typically identifies the certificate holder 312 (i.e. John Smith in this example) and the issuer of the certificate 314, and includes a digital signature of the issuer 316 and the certificate holder's public key 318. Certificate 310 will also typically include other information and attributes that identify the certificate holder (e.g. e-mail address, organization name, organizational unit name, location, etc.). When the individual composes a message to be sent to a recipient, it is customary to include that individual's certificate 310 with the message.
For a public key to be trusted, its issuing organization must be trusted. The relationship between a trusted CA and a user's public key can be represented by a series of related certificates, also referred to as a certificate chain. The certificate chain can be followed to determine the validity of a certificate.
For instance, in the example certificate chain 300 shown in FIG. 5, the recipient of a message purported to be sent by John Smith may wish to verify the trust status of certificate 310 attached to the received message. To verify the trust status of certificate 310 on a recipient's computing device (e.g. computer 262 a of FIG. 4) for example, the certificate 320 of issuer ABC is obtained, and used to verify that certificate 310 was indeed signed by issuer ABC. Certificate 320 may already be stored in a certificate store on the computing device, or it may need to be retrieved from a certificate source (e.g. LDAP server 284 of FIG. 4 or some other public or private LDAP server). If certificate 320 is already stored in the recipient's computing device and the certificate has been designated as trusted by the recipient, then certificate 310 is considered to be trusted since it chains to a stored, trusted certificate.
However, in the example shown in FIG. 5, certificate 330 is also required to verify the trust of certificate 310. Certificate 330 is self-signed, and is referred to as a “root certificate”. Accordingly, certificate 320 may be referred to as an “intermediate certificate” in certificate chain 300; any given certificate chain to a root certificate, assuming a chain to the root certificate can be determined for a particular end entity certificate, may contain zero, one, or multiple intermediate certificates. If certificate 330 is a root certificate issued by a trusted source (from a large certificate authority such as Verisign or Entrust, for example), then certificate 310 may be considered to be trusted since it chains to a trusted certificate. The implication is that both the sender and the recipient of the message trust the source of the root certificate 330. If a certificate cannot be chained to a trusted certificate, the certificate may be considered to be “not trusted”.
Certificate servers store information about certificates and lists identifying certificates that have been revoked. These certificate servers can be accessed to obtain certificates and to verify certificate authenticity and revocation status. For example, a Lightweight Directory Access Protocol (LDAP) server may be used to obtain certificates, and an Online Certificate Status Protocol (OCSP) server may be used to verify certificate revocation status.
Standard e-mail security protocols typically facilitate secure message transmission between non-mobile computing devices ( e.g. computers 262 a, 262 b of FIG. 4; remote desktop devices). Referring again to FIG. 4, in order that signed messages received from senders may be read from mobile device 100 and encrypted messages be sent to those senders, mobile device 100 is adapted to store certificates and associated public keys of other individuals. Certificates stored on a user's computer 262 a will typically be downloaded from computer 262 a to mobile device 100 through cradle 264, for example.
Certificates stored on computer 262 a and downloaded to mobile device 100 are not limited to certificates associated with individuals but may also include certificates issued to CAs, for example. Certain certificates stored in computer 262 a and/or mobile device 100 can also be explicitly designated as “trusted” by the user. Accordingly, when a certificate is received by a user on mobile device 100, it can be verified on mobile device 100 by matching the certificate with one stored on mobile device 100 and designated as trusted, or otherwise determined to be chained to a trusted certificate.
Mobile device 100 may also be adapted to store the private key of the public key/private key pair associated with the user, so that the user of mobile device 100 can sign outgoing messages composed on mobile device 100, and decrypt messages sent to the user encrypted with the user's public key. The private key may be downloaded to mobile device 100 from the user's computer 262 a through cradle 264, for example. The private key is preferably exchanged between the computer 262 a and mobile device 100 so that the user may share one identity and one method for accessing messages.
User computers 262 a, 262 b can obtain certificates from a number of sources, for storage on computers 262 a, 262 b and/or mobile devices (e.g. mobile device 100). These certificate sources may be private (e.g. dedicated for use within an organization) or public, may reside locally or remotely, and may be accessible from within an organization's private network or through the Internet, for example. In the example shown in FIG. 4, multiple PKI servers 280 associated with the organization reside on LAN 250. PKI servers 280 include a CA server 282 for issuing certificates, an LDAP server 284 used to search for and download certificates (e.g. for individuals within the organization), and an OCSP server 286 used to verify the revocation status of certificates.
Certificates may be retrieved from LDAP server 284 by a user computer 262 a, for example, to be downloaded to mobile device 100 via cradle 264. However, in a variant implementation, LDAP server 284 may be accessed directly (i.e. “over the air” in this context) by mobile device 100, and mobile device 100 may search for and retrieve individual certificates through a mobile data server 288. Similarly, mobile data server 288 may be adapted to allow mobile device 100 to directly query OCSP server 286 to verify the revocation status of certificates.
It will be understood by persons skilled in the art that mobile data server 288 need not physically reside on a separate computing device from the other components of LAN 250, and that mobile data server 288 may be provided on the same computing device as another component of LAN 250 in variant implementations. Furthermore, the functions of mobile data server 288 may be integrated with the functions of another component in LAN 250 (e.g. message management server 272) in variant implementations.
In variant implementations, only selected PKI servers 280 may be made accessible to mobile devices (e.g. allowing certificates to be downloaded only from a user's computer 262 a, 262 b, while allowing the revocation status of certificates to be checked from mobile device 100).
In variant implementations, certain PKI servers 280 may be made accessible only to mobile devices registered to particular users, as specified by an IT administrator, possibly in accordance with an IT policy, for example.
Other sources of certificates [not shown] may include a Windows certificate store, another secure certificate store on or outside LAN 250, and smart cards, for example.
Referring now to FIG. 6, a block diagram illustrating components of an example of an encoded message, as may be received by a message server (e.g. message server 268 of FIG. 4), is shown generally as 350. Encoded message 350 typically includes one or more of the following: a header portion 352, an encoded body portion 354, optionally one or more encoded attachments 356, one or more encrypted session keys 358, and signature and signature-related information 360. For example, header portion 352 typically includes addressing information such as “To”, “From”, and “CC” addresses, and may also include message length indicators, and sender encryption and signature scheme identifiers, for example. Actual message content normally includes a message body or data portion 354 and possibly one or more attachments 356, which may be encrypted by the sender using a session key. If a session key was used, it is typically encrypted for each intended recipient using the respective public key for each recipient, and included in the message at 358. If the message was signed, a signature and signature-related information 360 are also included. This may include the sender's certificate, for example.
The format for an encoded message as shown in FIG. 6 is provided by way of example only, and persons skilled in the art will understand that embodiments of the invention will be applicable to encoded messages of other formats. Depending on the specific messaging scheme used, components of an encoded message may appear in a different order than shown in FIG. 6, and an encoded message may include fewer, additional, or different components, which may depend on whether the encoded message is encrypted, signed or both.
Embodiments of the invention are generally directed to a system and method for more efficiently searching certificates on a device and retrieving certificates for storage on the device. In one embodiment, the device is a mobile device (e.g. mobile device 100 of FIG. 4), and a certificate search application residing and executing on the mobile device is programmed to initiate searches of certificates on one or more certificate servers (e.g. LDAP server 284 of FIG. 4). In this embodiment, the mobile device searches for and retrieves individual certificates from a certificate server through an intermediate computing device (e.g. mobile data server 288 of FIG. 4).
With reference to FIG. 4, consider an example implementation where a certificate search application on mobile device 100 searches for and retrieves individual certificates from LDAP server 284 through mobile data server 288. A search request is received by the certificate search application, typically from a user who provides a first name, last name, and e-mail address of an individual for whom the user wishes to locate a certificate. Certain search requests may also be made broader, by constructing search queries where inputting only a few letters of a name will return all certificates issued with a name containing those letters as a prefix, or by otherwise using wild cards or blank entries in input fields to expand a search, for example. The search request is then communicated from mobile device 100 to mobile data server 288, which then queries LDAP server 284 for the requested certificate(s). In this example implementation, located certificates are retrieved by the mobile data server 288, and specific search result data relating to each retrieved certificate, such as the common name and e-mail address of the individual (or entity) to which the respective certificate is issued, is communicated to the mobile device 100 so that a list can be generated from the search result data for display to the user. The user can then select specific certificates for downloading to and storage on mobile device 100 from the list. The selections are then communicated to mobile data server 288, from which the selected certificates are downloaded to mobile device 100.
By communicating only specific search result data used to generate a list of located certificates instead of entire certificates to mobile device 100 in the first instance, and by only downloading specific certificates selected by the user, the search and retrieval of certificates can be performed more efficiently (e.g. in terms of time and bandwidth). However, prior art systems may not be adapted to determine or provide an indication to users as to which certificates on the list are already stored in a certificate store on mobile device 100, without downloading the certificates to mobile device 100 to facilitate a determination. In such systems, selected certificates may need to be downloaded in order to confirm that they are not already stored in the certificate store. This consumes time and bandwidth, and is potentially unnecessary.
Accordingly, embodiments of the invention relate generally to methods that can facilitate a determination of whether certificates may already be stored on a device (such as mobile device 100, for example), without requiring the certificates to be downloaded in their entirety to the device.
Referring to FIG. 7A, a flowchart illustrating steps in a method of searching and retrieving certificates in an embodiment of the invention is shown generally as 400.
At step 410, a first computing device receives a request from a second device to search at least one certificate server for certificates. In one example implementation, the first computing device acts as an intermediary between the second device and the at least one certificate server, such as a mobile data server (e.g. mobile data server 288 of FIG. 4) in the case where the second device is a mobile device (e.g. mobile device 100 of FIG. 4). In one example implementation, a certificate server to be searched may be an LDAP server (e.g. LDAP server 284 of FIG. 4).
The request may comprise data provided by a certificate search application executing and residing on the second device. The data may originate from user input to the certificate search application (e.g. when the search is initiated by a user), or from data generated by an application that initiates the search in variant implementations. The data will typically include at least one name and/or an e-mail address, although it will be understood by persons skilled in the art that a variety of search queries may be constructed without departing from the scope of the invention.
For convenience, further steps of method 400 will now be described with reference to an example implementation where the first computing device is a mobile data server and the second device is a mobile device. However, embodiments of the invention described with reference to method 400 or method 400 b of FIG. 7B may be applied to implementations where the first computing device is not a mobile data server but is some other computing device and/or the second device is not a mobile device but is some other computing device. For example, a system architecture comprising first and second devices and at least one certificate server, where data transmissions between the first and second devices is generally more costly (e.g. in terms of time and/or bandwidth) than data transmissions between the first device and the at least one certificate server, may benefit from an application of an embodiment of the invention.
At step 420, the mobile data server queries the at least one certificate server for certificates based on the search request received at step 410 from the certificate search application of the mobile device. Certificates located in the search are retrieved from the at least one certificate server by the mobile data server.
At step 430, the mobile data server returns search result data relating to each located certificate to the certificate search application of the mobile device. The search result data returned typically includes the common name and e-mail address of the individual (or entity) to which the respective certificate is issued. However, in accordance with this embodiment of the invention, the mobile data server further processes each retrieved certificate, by parsing each retrieved certificate to identify the serial number and issuer of the respective certificate, which is returned as a part of the search result data.
In some implementations, the certificates retrieved at step 420 are only stored temporarily until search result data is returned to the mobile device at step 430, at which time the retrieved certificates are deleted. In other implementations, the certificates retrieved at step 420 may be cached or otherwise more permanently stored (e.g. until a response to the returned search result data is received from the mobile device, or for some pre-determined duration).
At step 440, the certificate search application compares the serial number and issuer data associated with each located certificate to the serial number and issuer data associated with certificates stored on the mobile device in one or more designated certificate stores thereof, to determine whether the respective certificate is already stored on the mobile device.
At step 450, a list of located certificates is generated and displayed to a user of the mobile device. The list is generated from at least a subset of the search result data returned to the mobile device at step 430. For instance, the list may identify each located certificate by the common name and/or e-mail address of the individual (or entity) to which the certificate is issued. In one embodiment of the invention, an indicator accompanying the respective entry on the list for each located certificate may also be provided, where the indicator indicates whether the respective certificate is already stored on the mobile device, based on determinations made at step 440. Accordingly, the user need not select certificates for download that are already stored on the mobile device, so that duplicate certificates need not be necessarily downloaded to the mobile device. The indicator may comprise a checked or unchecked box, for example. As a further example, each entry on the list may be highlighted or non-highlighted depending on the status of the indicator.
At step 460, certificates are selected for download, by the user of the mobile device, for example.
At step 470, data identifying the selections made at step 460 are received by the mobile data server from the mobile device, and the selected certificates are subsequently returned to the mobile device, typically for storage on the mobile device. In some implementations, it may be necessary for the mobile data server to query a certificate server again for a selected certificate before the certificate is returned to the mobile device [step not shown], in the event that the certificate was not retained by the mobile data server since the previous download.
Referring now to FIG. 7B, a flowchart illustrating steps in a method of searching and retrieving certificates in another embodiment of the invention is shown generally as 400 b. Method 400 b is similar to method 400, except that the search result data associated with certificates returned by the first computing device to the second device comprises a hash of at least a part of each located certificate.
Specifically, at step 430 b, the mobile data server returns search result data relating to each located certificate to the certificate search application of the mobile device. The search result data returned typically includes the common name and e-mail address of the individual (or entity) to which the respective certificate is issued. In accordance with this embodiment of the invention, the mobile data server further processes each retrieved certificate by applying a hash algorithm, to hash at least a part of each retrieved certificate. The hash is then returned as a part of the search result data. In one implementation, the entire certificate is hashed to generate the returned hash. However in variant implementations, one or more specific parts or fields of a certificate may be hashed to generate the returned hash, although the likelihood that the hash will uniquely and correctly identify an identical certificate may be decreased depending on the parts or fields hashed.
At step 440, the certificate search application generates a hash for each certificate stored on the mobile device in one or more designated certificate stores thereof, and compares each generated hash to the hash associated with each located certificate, in order to determine whether the respective certificate is already stored on the mobile device. The same hash algorithm employed at step 430 b is applied at this step (to the same parts or fields of the stored certificates if the entire certificates are not hashed) in generating the hashes of the stored certificates. Accordingly, if a generated hash of a given certificate matches a hash received from the mobile data server at step 430 b, a match is deemed to have been determined.
Details pertaining to the remaining steps of method 400 b are provided with reference to FIG. 7A.
In variant embodiments of the invention, other data that can be used to uniquely identify a certificate and that may be communicated more efficiently (e.g. in terms of time and/or bandwidth) than communicating the entire certificate may be returned to the second device as part of the search result data, and used to determine if the certificate is already stored on the second device.
Embodiments of the invention described above generally allow users to quickly determine which certificate(s) need to be downloaded to their computing device without making costly requests. In variant embodiments of the invention, the certificate search request may not be initiated by a user but may instead be initiated by an application executing on the second device (possibly by the certificate search application or some other application). In those embodiments, a list may not be generated for display to a user (e.g. at step 450 of FIGS. 7A and 7B), and certificates may be automatically designated for download without user intervention after identifying which certificates may have already been stored on the second device (e.g. at step 440 of FIGS. 7A and 7B).
In variant embodiments, the invention may also be applied to other applications not involving certificates. For example, some of the foregoing techniques may be used to determine if certain contact data records or electronic documents are already stored on a computing device, for example.
The steps of a method of searching and retrieving certificates in embodiments of the invention may be provided as executable software instructions stored on computer-readable media, which may include transmission-type media.
The invention has been described with regard to a number of embodiments. However, it will be understood by persons skilled in the art that other variants and modifications may be made without departing from the scope of the invention as defined in the claims appended hereto.

Claims (27)

The invention claimed is:
1. A method of retrieving certificates, the method comprising:
transmitting a certificate search request from an application executing on a mobile device to one or more certificate servers;
for each of one or more located certificates, receiving, at the mobile device in response to the certificate search request, search result data associated with the located certificate from the one or more certificate servers, wherein the search result data for the located certificate comprises serial number and issuer data that uniquely identifies the located certificate and is not the entire data within the located certificate;
determining, by the application without user intervention, whether each located certificate is already stored on the mobile device by comparing the serial number and issuer data that uniquely identifies the located certificate in said search result data to serial number and issuer data associated with certificates stored on the mobile device so that the located certificate is not required to be downloaded in its entirety to the mobile device to determine whether the located certificate is stored on the mobile device;
in response to the determining, selecting certificates for retrieval after identifying which located certificates are already stored on the mobile device; and
retrieving, to the mobile device, the located certificates that are selected for retrieval by the application from the one or more certificate servers, for storage on the mobile device.
2. The method of claim 1, further comprising identifying, in a user interface of the mobile device, which located certificates are not already stored on the mobile device; wherein the selecting is performed, in response to the identifying which located certificates are not already stored on the mobile device, based on user input received at the mobile device.
3. The method of claim 1, wherein the selecting and the retrieving is performed without user intervention.
4. The method of claim 1, wherein the one or more certificate servers comprises an LDAP server.
5. A mobile device configured to retrieve certificates from one or more certificate servers, the mobile device comprising:
a physical processor configured to
transmit a certificate search request from an application executing on the mobile device to the one or more certificate servers;
for each of one or more located certificates, receive, at the mobile device in response to the certificate search request, search result data associated with the located certificate from the one or more certificate servers, wherein the search result data for the located certificate comprises serial number and issuer data that uniquely identifies the located certificate and is not the entire data within the located certificate;
determine, by the application without user intervention, whether each located certificate is already stored on the mobile device by comparing the serial number and issuer data that uniquely identifies the located certificate in said search result data to serial number and issuer data associated with certificates stored on the mobile device so that the located certificate is not required to be downloaded in its entirety to the mobile device to determine whether the located certificate is stored on the mobile device;
in response to determining whether each located certificate is already stored on the mobile device, select certificates for retrieval after identifying which located certificates are already stored on the mobile device; and
retrieve, to the mobile device, the located certificates that are selected for retrieval by the application from the one or more certificate servers, for storage on the mobile device.
6. The device of claim 5, wherein the processor is configured to identify, in a user interface of the mobile device, which located certificates are not already stored on the mobile device; and wherein the processor is configured to select the certificates for retrieval, in response to identifying which located certificates are not already stored on the mobile device, based on user input received at the mobile device.
7. The device of claim 5, wherein the processor is configured to select the certificate for retrieval and to retrieve the located certificates that are selected for retrieval without user intervention.
8. The device of claim 5, wherein the one or more certificate servers comprises an LDAP server.
9. A non-transitory computer-readable medium comprising instructions for execution by a processor of a mobile device, the instructions causing the processor to perform a method of retrieving certificates comprising:
transmitting a certificate search request from an application executing on the mobile device to one or more certificate servers;
for each of one or more located certificates, receiving, at the mobile device in response to the certificate search request, search result data associated with the located certificate from the one or more certificate servers, wherein the search result data for the located certificate comprises serial number and issuer data that uniquely identifies the located certificate and is not the entire data within the located certificate;
determining, by the application without user intervention, whether each located certificate is already stored on the mobile device by comparing the serial number and issuer data that uniquely identifies the located certificate in said search result data to serial number and issuer data associated with certificates stored on the mobile device so that the located certificate is not required to be downloaded in its entirety to the mobile device to determine whether the located certificate is stored on the mobile device;
in response to the determining, selecting certificates for retrieval after identifying which located certificates are already stored on the mobile device; and
retrieving, to the mobile device, the located certificates that are selected for retrieval by the application from the one or more certificate servers, for storage on the mobile device.
10. The medium of claim 9, wherein the instructions further cause the processor to identify, in a user interface of the mobile device, which located certificates are not already stored on the mobile device; wherein the selecting is performed, in response to identifying which located certificates are not already stored on the mobile device, based on user input received at the mobile device.
11. The medium of claim 9, wherein the selecting and the retrieving is performed without user intervention.
12. The medium of claim 9, wherein the one or more certificate servers comprises an LDAP server.
13. A method of retrieving certificates, the method comprising:
transmitting a certificate search request from an application executing on a mobile device to one or more certificate servers;
for each of one or more located certificates, receiving, at the mobile device in response to the certificate search request, search result data associated with the located certificate from the one or more certificate servers, wherein the search result data for the located certificate comprises a certificate hash that uniquely identifies the located certificate and is not the entire data within the located certificate;
determining, by the application without user intervention, whether each located certificate is already stored on the mobile device by comparing the certificate hash that uniquely identifies the located certificate in said search result data to certificate hashes associated with certificates stored on the mobile device so that the located certificate is not required to be downloaded in its entirety to the mobile device to determine whether the located certificate is stored on the mobile device;
in response to the determining, selecting certificates for retrieval after identifying which located certificates are already stored on the mobile device; and
retrieving, to the mobile device, the located certificates that are selected for retrieval by the application from the one or more certificate servers, for storage on the mobile device.
14. The method of claim 13, further comprising identifying, in a user interface of the mobile device, which located certificates are not already stored on the mobile device; wherein the selecting is performed, in response to the identifying which located certificates are not already stored on the mobile device, based on user input received at the mobile device.
15. The method of claim 13, wherein the selecting and the retrieving is performed without user intervention.
16. The method of claim 13, wherein the one or more certificate servers comprises an LDAP server.
17. The method of claim 13, further comprising generating one or more certificate hashes associated with certificates stored on the mobile device.
18. A mobile device configured to retrieve certificates from one or more certificate servers, the mobile device comprising:
a physical processor configured to
transmit a certificate search request from an application executing on the mobile device to the one or more certificate servers;
for each of one or more located certificates, receive, at the mobile device in response to the certificate search request, search result data associated with the located certificate from the one or more certificate servers, wherein the search result data for the located certificate comprises a certificate hash that uniquely identifies the located certificate and is not the entire data within the located certificate;
determine, by the application without user intervention, whether each located certificate is already stored on the mobile device by comparing the certificate hash that uniquely identifies the located certificate in said search result data to certificate hashes associated with certificates stored on the mobile device so that the located certificate is not required to be downloaded in its entirety to the mobile device to determine whether the located certificate is stored on the mobile device;
in response to determining whether each located certificate is already stored on the mobile device, select certificates for retrieval after identifying which located certificates are already stored on the mobile device; and
retrieve, to the mobile device, the located certificates that are selected for retrieval by the application from the one or more certificate servers, for storage on the mobile device.
19. The device of claim 18, wherein the processor is configured to identify, in a user interface of the mobile device, which located certificates are not already stored on the mobile device; and wherein the processor is configured to select the certificates for retrieval, in response to identifying which located certificates are not already stored on the mobile device, based on user input received at the mobile device.
20. The device of claim 18, wherein the processor is configured to select the certificates for retrieval and to retrieve the located certificates that are selected for retrieval without user intervention.
21. The device of claim 18, wherein the one or more certificate servers comprises an LDAP server.
22. The device of claim 18, wherein the processor is configured to generate one or more certificate hashes associated with certificates stored on the mobile device.
23. A non-transitory computer-readable medium comprising instructions for execution by a processor of a mobile device, the instructions causing the processor to perform a method of retrieving certificates comprising:
transmitting a certificate search request from an application executing on the mobile device to one or more certificate servers;
for each of one or more located certificates, receiving, at the mobile device in response to the certificate search request, search result data associated with the located certificate from the one or more certificate servers, wherein the search result data for the located certificate comprises a certificate hash that uniquely identifies the located certificate and is not the entire data within the located certificate;
determining, by the application without user intervention, whether each located certificate is already stored on the mobile device by comparing the certificate hash that uniquely identifies the located certificate in said search result data to certificate hashes associated with certificates stored on the mobile device so that the located certificate is not required to be downloaded in its entirety to the mobile device to determine whether the located certificate is stored on the mobile device;
in response to the determining, selecting certificates for retrieval after identifying which located certificates are already stored on the mobile device; and
retrieving, to the mobile device, the located certificates that are selected for retrieval by the application from the one or more certificate servers, for storage on the mobile device.
24. The medium of claim 23, wherein the instructions further cause the processor to identify, in a user interface of the mobile device, which located certificates are not already stored on the mobile device; wherein the selecting is performed, in response to identifying which located certificates are not already stored on the mobile device, based on user input received at the mobile device.
25. The medium of claim 23, wherein the selecting and the retrieving is performed without user intervention.
26. The medium of claim 23, wherein the one or more certificate servers comprises an LDAP server.
27. The medium of claim 23, wherein the instructions further cause the processor to generate one or more certificate hashes associated with certificates stored on the mobile device.
US13/483,216 2004-09-02 2012-05-30 System and method for searching and retrieving certificates Active US8566582B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/483,216 US8566582B2 (en) 2004-09-02 2012-05-30 System and method for searching and retrieving certificates

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/931,983 US7640428B2 (en) 2004-09-02 2004-09-02 System and method for searching and retrieving certificates
US12/645,003 US8209530B2 (en) 2004-09-02 2009-12-22 System and method for searching and retrieving certificates
US13/483,216 US8566582B2 (en) 2004-09-02 2012-05-30 System and method for searching and retrieving certificates

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/645,003 Continuation US8209530B2 (en) 2004-09-02 2009-12-22 System and method for searching and retrieving certificates

Publications (2)

Publication Number Publication Date
US20120239927A1 US20120239927A1 (en) 2012-09-20
US8566582B2 true US8566582B2 (en) 2013-10-22

Family

ID=36035450

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/931,983 Active 2027-07-17 US7640428B2 (en) 2004-09-02 2004-09-02 System and method for searching and retrieving certificates
US12/645,003 Active 2025-01-31 US8209530B2 (en) 2004-09-02 2009-12-22 System and method for searching and retrieving certificates
US13/483,216 Active US8566582B2 (en) 2004-09-02 2012-05-30 System and method for searching and retrieving certificates

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/931,983 Active 2027-07-17 US7640428B2 (en) 2004-09-02 2004-09-02 System and method for searching and retrieving certificates
US12/645,003 Active 2025-01-31 US8209530B2 (en) 2004-09-02 2009-12-22 System and method for searching and retrieving certificates

Country Status (1)

Country Link
US (3) US7640428B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8943156B2 (en) 2006-06-23 2015-01-27 Blackberry Limited System and method for handling electronic mail mismatches

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3926792B2 (en) 2001-06-12 2007-06-06 リサーチ イン モーション リミテッド System and method for compressing secure email for exchange with mobile data communication devices
KR20040015272A (en) 2001-06-12 2004-02-18 리서치 인 모션 리미티드 Certificate management and transfer system and method
CN1653459B (en) 2001-06-12 2010-12-15 捷讯研究有限公司 System and method for processing encoded messages for exchange with a mobile data communication device
US20040205248A1 (en) * 2001-07-10 2004-10-14 Herbert A Little System and method for secure message key caching in a mobile communication device
CN101232504B (en) 2001-08-06 2012-09-19 捷讯研究有限公司 System and method for processing encoded messages
US9094429B2 (en) 2004-08-10 2015-07-28 Blackberry Limited Server verification of secure electronic messages
US7631183B2 (en) 2004-09-01 2009-12-08 Research In Motion Limited System and method for retrieving related certificates
US7549043B2 (en) 2004-09-01 2009-06-16 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
US7640428B2 (en) 2004-09-02 2009-12-29 Research In Motion Limited System and method for searching and retrieving certificates
US9282455B2 (en) 2004-10-01 2016-03-08 Intel Corporation System and method for user certificate initiation, distribution, and provisioning in converged WLAN-WWAN interworking networks
FI20050491A0 (en) * 2005-05-09 2005-05-09 Nokia Corp System for delivery of certificates in a communication system
DE602005020482D1 (en) * 2005-10-14 2010-05-20 Research In Motion Ltd Masterverschlüsselung
US20070088681A1 (en) * 2005-10-17 2007-04-19 Veveo, Inc. Method and system for offsetting network latencies during incremental searching using local caching and predictive fetching of results from a remote server
US20080022374A1 (en) * 2006-06-29 2008-01-24 Research In Motion Limited System and method for securely communicating with a server
US20090300346A1 (en) * 2008-05-30 2009-12-03 Kashyap Merchant Device and Method for Identifying Certificates
US20100031028A1 (en) * 2008-07-31 2010-02-04 Research In Motion Limited Systems and methods for selecting a certificate for use with secure messages
US8275991B2 (en) * 2009-07-10 2012-09-25 Cahn Robert S On-line membership verification
TWI595380B (en) * 2015-11-20 2017-08-11 捷碼數位科技股份有限公司 Device for generating or verifying authenticate electronic document with electronic and paper certification and method thereof
US10666637B2 (en) * 2015-12-14 2020-05-26 Amazon Technologies, Inc. Certificate renewal and deployment
US10041451B2 (en) 2016-05-23 2018-08-07 Ford Global Technologies, Llc Methods and systems for controlling air flow paths in an engine
US10574634B2 (en) * 2017-02-10 2020-02-25 Ssh Communications Security Oyj Management of authenticator information in a computer system
US10530816B2 (en) 2017-05-18 2020-01-07 Nio Usa, Inc. Method for detecting the use of unauthorized security credentials in connected vehicles

Citations (163)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4028500A (en) 1973-05-15 1977-06-07 Martin Marietta Corporation Mobile unit supervisory control sequencer and method
US5410602A (en) 1993-09-27 1995-04-25 Motorola, Inc. Method for key management of point-to-point communications
US5457748A (en) 1992-11-30 1995-10-10 Motorola, Inc. Method and apparatus for improved security within encrypted communication devices
EP0500245B1 (en) 1991-02-08 1996-11-06 Kabushiki Kaisha Toshiba Cipher communication system for transaction data
US5623546A (en) 1995-06-23 1997-04-22 Motorola, Inc. Encryption method and system for portable data
US5634051A (en) 1993-10-28 1997-05-27 Teltech Resource Network Corporation Information management system
US5666530A (en) 1992-12-02 1997-09-09 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between
EP0500222B1 (en) 1991-02-14 1997-10-22 Hewlett-Packard Company Method for reconciling entries in a plurality of lists
US5710922A (en) 1993-06-02 1998-01-20 Apple Computer, Inc. Method for synchronizing and archiving information between computer systems
US5727202A (en) 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
US5778068A (en) 1995-02-13 1998-07-07 Eta Technologies Corporation Personal access management system
US5778346A (en) 1992-01-21 1998-07-07 Starfish Software, Inc. System and methods for appointment reconcilation
US5812671A (en) 1996-07-17 1998-09-22 Xante Corporation Cryptographic communication system
US5870030A (en) 1996-04-04 1999-02-09 Motorola, Inc. Advertiser pays information and messaging system and apparatus
US5956707A (en) 1997-02-13 1999-09-21 Chu; Wesley W. Database system with query relaxation using type abstraction hierarchy (TAH) as query condition relaxation structure
US5991399A (en) 1997-12-18 1999-11-23 Intel Corporation Method for securely distributing a conditional use private key to a trusted entity on a remote system
US6000000A (en) 1995-10-13 1999-12-07 3Com Corporation Extendible method and apparatus for synchronizing multiple files on two different computer systems
JP2000104774A (en) 1998-09-25 2000-04-11 Kurashiki Kako Co Ltd Long life elastic structure
EP0942568A3 (en) 1998-02-17 2000-04-12 Phone.Com Inc. Centralized certificate management system for two-way interactive communication devices in data networks
US6061448A (en) 1997-04-01 2000-05-09 Tumbleweed Communications Corp. Method and system for dynamic server document encryption
US6073237A (en) 1997-11-06 2000-06-06 Cybercash, Inc. Tamper resistant method and apparatus
US6081601A (en) 1998-01-08 2000-06-27 Nokia Telecommunications Oy Method of implementing connection security in a wireless network
US6084969A (en) 1997-12-31 2000-07-04 V-One Corporation Key encryption system and method, pager unit, and pager proxy for a two-way alphanumeric pager network
US6085323A (en) 1996-04-15 2000-07-04 Kabushiki Kaisha Toshiba Information processing system having function of securely protecting confidential information
US6119228A (en) 1997-08-22 2000-09-12 Compaq Computer Corporation Method for securely communicating remote control commands in a computer network
US6125369A (en) 1997-10-02 2000-09-26 Microsoft Corporation Continuous object sychronization between object stores on different computers
US6209098B1 (en) 1996-10-25 2001-03-27 Intel Corporation Circuit and method for ensuring interconnect security with a multi-chip integrated circuit package
JP2001103571A (en) 1999-10-01 2001-04-13 Mitsubishi Electric Corp Mobile communication service providing system
US6219694B1 (en) 1998-05-29 2001-04-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device having a shared electronic address
US6230186B1 (en) 1998-04-28 2001-05-08 Rhoda Yaker Private electronic message system
US6229894B1 (en) 1997-07-14 2001-05-08 Entrust Technologies, Ltd. Method and apparatus for access to user-specific encryption information
US6233572B1 (en) 1998-05-28 2001-05-15 I2 Technologies, Inc. Computer implemented system and method for high level controlled searching through a problem space
JP2001197055A (en) 2000-01-07 2001-07-19 Nippon Steel Corp Device, method, and service system for proxy authentication and computer-readable recording medium
US6266775B1 (en) 1997-08-25 2001-07-24 Nec Corporation Method and apparatus for displaying information and information recording medium having information displaying means
US6266420B1 (en) 1998-10-08 2001-07-24 Entrust Technologies Limited Method and apparatus for secure group communications
US6289105B1 (en) 1995-07-28 2001-09-11 Kabushiki Kaisha Toshiba Method and apparatus for encrypting and transferring electronic mails
JP2001265216A (en) 2000-03-16 2001-09-28 Nippon Telegr & Teleph Corp <Ntt> Method and device for publishing public key certificate
US6301658B1 (en) 1998-09-09 2001-10-09 Secure Computing Corporation Method and system for authenticating digital certificates issued by an authentication hierarchy
US20010046307A1 (en) 1998-04-30 2001-11-29 Hewlett-Packard Company Method and apparatus for digital watermarking of images
US20010050990A1 (en) 1997-02-19 2001-12-13 Frank Wells Sudia Method for initiating a stream-oriented encrypted communication
US20020007453A1 (en) 2000-05-23 2002-01-17 Nemovicher C. Kerry Secured electronic mail system and method
US6348972B1 (en) 1995-06-01 2002-02-19 Tokyo Shibaura Electric Co Network print system for allowing a printer or printers to select a host
US20020032861A1 (en) 2000-07-14 2002-03-14 Nec Corporation System and method for executing and assuring security of electronic mail for users, and storage medium storing program to cause computer to implement same method
US20020035685A1 (en) 2000-09-11 2002-03-21 Masahiro Ono Client-server system with security function intermediary
US20020035687A1 (en) 2000-06-07 2002-03-21 Kristofer Skantze Method and device for secure wireless transmission of information
GB2328125B (en) 1997-08-08 2002-04-10 Ericsson Telefon Ab L M Network control system
US6377946B1 (en) 1998-02-25 2002-04-23 Hitachi Ltd Document search method and apparatus and portable medium used therefor
US20020051544A1 (en) 1993-12-03 2002-05-02 Fujitsu Limited User support system for cryptographic communication in network systems
US20020053023A1 (en) 2000-08-17 2002-05-02 Patterson Andrew John Certification validation system
US6389455B1 (en) 1998-09-22 2002-05-14 Richard C. Fuisz Method and apparatus for bouncing electronic messages
US20020059383A1 (en) 2000-06-19 2002-05-16 Takeo Katsuda Apparatus, portable terminal unit, and system for controlling E-mail, and its method, computer-readable recording medium and program product for processing E-mail
US20020059375A1 (en) 1999-04-08 2002-05-16 Alvin Pivowar System and method for sharing data among a plurality of personal digital assistants
JP2002163395A (en) 2000-11-27 2002-06-07 Hitachi Software Eng Co Ltd Method for supporting confirmation of electronic certificate validity and information processor used for the same
US20020080752A1 (en) 2000-12-22 2002-06-27 Fredrik Johansson Route optimization technique for mobile IP
US6421707B1 (en) 1998-02-13 2002-07-16 Lucent Technologies Inc. Wireless multi-media messaging communications method and apparatus
US20020099766A1 (en) 2001-01-24 2002-07-25 Tuli Raja Singh Portable high speed internet access device with encryption
US20020147905A1 (en) 2001-04-05 2002-10-10 Sun Microsystems, Inc. System and method for shortening certificate chains
JP2002535884A (en) 1999-01-14 2002-10-22 タンブルウィード コミュニケーションズ コーポレイション Distribution of web-based secure email messages
US20020165967A1 (en) 2001-05-02 2002-11-07 Morgan Paul A. Global personalization engine
US20020169954A1 (en) 1998-11-03 2002-11-14 Bandini Jean-Christophe Denis Method and system for e-mail message transmission
US20020173295A1 (en) 2001-05-15 2002-11-21 Petri Nykanen Context sensitive web services
US20020176067A1 (en) 2001-05-23 2002-11-28 Canesta, Inc. Method and system to enhance dynamic range conversion useable with CMOS three-dimensional imaging
WO2002101580A1 (en) * 2001-06-12 2002-12-19 Research In Motion Limited Certificate management and transfer system and method
US20030002671A1 (en) 2001-06-11 2003-01-02 Eastman Kodak Company Delivery of electronic content over a network using a hybrid optical disk for authentication
US20030028647A1 (en) 2001-07-31 2003-02-06 Comverse, Ltd. E-mail protocol optimized for a mobile environment and gateway using same
JP2003046499A (en) 2001-08-03 2003-02-14 Nec Corp Communication system, user terminal, ic card, authentication system, and control system and program for access and communication
US6531985B1 (en) 2000-08-14 2003-03-11 3Com Corporation Integrated laptop antenna using two or more antennas
US20030074555A1 (en) 2001-10-17 2003-04-17 Fahn Paul Neil URL-based certificate in a PKI
US6564320B1 (en) 1998-06-30 2003-05-13 Verisign, Inc. Local hosting of digital certificate services
US6567914B1 (en) 1998-07-22 2003-05-20 Entrust Technologies Limited Apparatus and method for reducing transmission bandwidth and storage requirements in a cryptographic security system
US20030126085A1 (en) 2001-12-27 2003-07-03 Slamdunk Networks, Inc. Dynamic authentication of electronic messages using a reference to a certificate
US20030163567A1 (en) 2002-02-28 2003-08-28 Mcmorris Patrick Domain name validation using mapping table
US20030172122A1 (en) 2002-03-06 2003-09-11 Little Herbert A. System and method for providing secure message signature status and trust status indication
US6633873B1 (en) 1999-02-16 2003-10-14 Fujitsu Limited Distributed data retrieval system including mechanism for predicting an amount of response data
US20030196084A1 (en) 2002-04-12 2003-10-16 Emeka Okereke System and method for secure wireless communications using PKI
US20030198350A1 (en) 2002-04-18 2003-10-23 International Business Machines Corporation Method, system and program product for managing a size of a key management block during content distribution
US20030212888A1 (en) 1998-08-26 2003-11-13 Wildish Michael Andrew System and method of looking up and validating a digital certificate in one pass
JP2003348078A (en) 2002-05-27 2003-12-05 Hitachi Ltd Location authentication system and method thereof
US6661927B1 (en) 2000-07-27 2003-12-09 Motorola, Inc. System and method for efficiently encoding an image by prioritizing groups of spatially correlated coefficients based on an activity measure
US20040024826A1 (en) 2000-09-07 2004-02-05 Erez Halahmi E-mail proxy
JP2004048139A (en) 2002-07-09 2004-02-12 Nikon Corp Image transmission system, image relay apparatus and electronic image apparatus
US20040030681A1 (en) 2000-11-21 2004-02-12 Shannon Paul Thurmond System and process for network site fragmented search
EP0841770B1 (en) 1996-11-06 2004-02-18 Nokia Corporation Method for sending a secure message in a telecommunications system
US6697942B1 (en) 1999-02-04 2004-02-24 Earthlink, Inc. Method for remotely managing a remote device using an electronic mail message
US20040052356A1 (en) 2002-09-18 2004-03-18 Sbc Properties, L.P., Of Reno, Nv Multi-modal address book
US6725262B1 (en) 2000-04-27 2004-04-20 Microsoft Corporation Methods and systems for synchronizing multiple computing devices
US20040083364A1 (en) 2000-12-07 2004-04-29 Jean-Pierre Andreaux Method of secure transmission of digital data from a source to a receiver
US6732144B1 (en) 1999-11-19 2004-05-04 Kabushiki Kaisha Toshiba Communication method for data synchronization processing and electronic device therefor
US6732273B1 (en) 1998-10-21 2004-05-04 Lucent Technologies Inc. Priority and security coding system for electronic mail messages
US20040090457A1 (en) 2002-11-12 2004-05-13 Microsoft Corporation System and apparatus for sending complete responses to truncated electronic mail messages on a mobile device
US20040093493A1 (en) * 1995-01-17 2004-05-13 Bisbee Stephen F. System and method for electronic transmission, storage and retrieval of authenticated documents
US20040096055A1 (en) 2002-11-20 2004-05-20 Roy Williams System and method for transmitting reduced information from a certificate to perform encryption operations
US6745024B1 (en) 2000-01-10 2004-06-01 Qualcomm Incorporated System and method for preparing and sending an electronic mail communication using a wireless communications device
JP2004179724A (en) 2002-11-25 2004-06-24 Mitsubishi Electric Corp Server apparatus, certificate verifying method, program, and computer-readable recording medium recorded with the program
US20040133775A1 (en) 2003-01-07 2004-07-08 Callas Jonathan D. System and method for secure electronic communication in a partially keyless environment
US20040133520A1 (en) 2003-01-07 2004-07-08 Callas Jonathan D. System and method for secure and transparent electronic communication
US6779115B1 (en) 2000-02-18 2004-08-17 Digital5, Inc. Portable device using a smart card to receive and decrypt digital data
US20040172453A1 (en) 2001-06-28 2004-09-02 Keith De Mendonca E-mail manager program for a wireless information device
US20040177248A1 (en) 2003-03-05 2004-09-09 Fuji Xerox Co., Ltd. Network connection system
US20040196978A1 (en) 2001-06-12 2004-10-07 Godfrey James A. System and method for processing encoded messages for exchange with a mobile data communication device
US20040202327A1 (en) 2001-08-06 2004-10-14 Little Herbert A. System and method for processing encoded messages
US20040205248A1 (en) 2001-07-10 2004-10-14 Herbert A Little System and method for secure message key caching in a mobile communication device
US6819766B1 (en) 1999-03-30 2004-11-16 International Business Machines Corporation Method and system for managing keys for encrypted data
US6829357B1 (en) 1999-12-14 2004-12-07 Trw Inc. Communication system having a transmitter and a receiver that engage in reduced size encrypted data communication
US20050005097A1 (en) 2003-06-12 2005-01-06 Minolta Co., Ltd. Communication system and method in public key infrastructure
US20050039100A1 (en) 2003-08-14 2005-02-17 International Business Machines Corporation Method and system for automatic error recovery in an electronic mail system
US20050055372A1 (en) 2003-09-04 2005-03-10 Microsoft Corporation Matching media file metadata to standardized metadata
US20050071508A1 (en) 2003-08-12 2005-03-31 Brown Michael K. System and method for processing encoded messages
US20050080642A1 (en) 2003-10-14 2005-04-14 Daniell W. Todd Consolidated email filtering user interface
US20050114671A1 (en) 2002-03-20 2005-05-26 Research In Motion Ltd. System and method for transmitting and utilizing attachments
US6904521B1 (en) 2001-02-16 2005-06-07 Networks Associates Technology, Inc. Non-repudiation of e-mail messages
US20050149442A1 (en) 2002-03-20 2005-07-07 Research In Motion Limited Certificate information storage system and method
US20050148323A1 (en) 2002-03-20 2005-07-07 Research In Motion Limited System and method for supporting multiple certificate status providers on a mobile communication device
US6918038B1 (en) 1996-08-13 2005-07-12 Angel Secure Networks, Inc. System and method for installing an auditable secure network
US20050160292A1 (en) 2004-01-21 2005-07-21 Microsoft Corporation Encryption to BCC recipients with S/MIME
US6925568B1 (en) 1998-01-16 2005-08-02 Sonera Oyj Method and system for the processing of messages in a telecommunication system
US6931532B1 (en) 1999-10-21 2005-08-16 International Business Machines Corporation Selective data encryption using style sheet processing
US20050188219A1 (en) 2003-12-26 2005-08-25 Orange France Method and a system for communication between a terminal and at least one communication equipment
US20050203855A1 (en) 2000-11-08 2005-09-15 Orchestria Limited Information management system
US20050210289A1 (en) 2004-03-22 2005-09-22 Brown Michael K System and method for viewing message attachments
US20050222991A1 (en) 2004-02-04 2005-10-06 Kazuyuki Ikenoya Information providing apparatus, information providing method, information providing program, and recording medium
US20050246763A1 (en) 2004-03-25 2005-11-03 National University Of Ireland Secure digital content reproduction using biometrically derived hybrid encryption techniques
US6983367B2 (en) 2000-03-14 2006-01-03 Sony Corporation Information providing apparatus and method, information processing apparatus and method, and program storage medium
US20060015722A1 (en) 2004-07-16 2006-01-19 Geotrust Security systems and services to provide identity and uniform resource identifier verification
US6993137B2 (en) 2000-06-16 2006-01-31 Entriq, Inc. Method and system to securely distribute content via a network
US6996720B1 (en) 1999-12-17 2006-02-07 Microsoft Corporation System and method for accessing protected content in a rights-management architecture
US20060031300A1 (en) 2002-08-30 2006-02-09 Kock Martijn W M Method and system for the phased retrieval of data
CA2476914A1 (en) 2004-08-09 2006-02-09 Research In Motion Limited System and method for certificate searching and retrieval
US20060036865A1 (en) 2004-08-10 2006-02-16 Research In Motion Limited Server verification of secure electronic messages
US20060036848A1 (en) 2004-08-09 2006-02-16 Research In Motion Limited System and method for enabling bulk retrieval of certificates
US20060036849A1 (en) 2004-08-09 2006-02-16 Research In Motion Limited System and method for certificate searching and retrieval
US7003667B1 (en) 1999-10-04 2006-02-21 Canon Kabushiki Kaisha Targeted secure printing
US20060059332A1 (en) 2004-09-02 2006-03-16 Research In Motion Limited System and method for searching and retrieving certificates
US7020708B2 (en) 1999-05-14 2006-03-28 Cingular Wireless Ii, Llc Aircraft data services
US7028186B1 (en) 2000-02-11 2006-04-11 Nokia, Inc. Key management methods for wireless LANs
US7032240B1 (en) 1999-12-07 2006-04-18 Pace Anti-Piracy, Inc. Portable authorization device for authorizing use of protected information and associated method
US7032030B1 (en) 1999-03-11 2006-04-18 John David Codignotto Message publishing system and method
US20060143700A1 (en) 2004-12-24 2006-06-29 Check Point Software Technologies, Inc. Security System Providing Methodology for Cooperative Enforcement of Security Policies During SSL Sessions
TW200629858A (en) 2004-09-01 2006-08-16 Research In Motion Ltd Providing certificate matching in a system and method for searching and retrieving certificates
US7113927B1 (en) 1998-10-09 2006-09-26 Victor Company Of Japan, Limited Data distribution system, data distribution method, portable terminal with data receiving capability, portable terminal with data transmitting/receiving capability, recording medium onto which data content is recorded, encoding apparatus, and decoding apparatus
US7127604B2 (en) 2002-07-09 2006-10-24 Texas Instruments Incorporated Changing a codec or MAC size without affecting the encryption key in PacketCable communication
US7136897B1 (en) 2000-08-22 2006-11-14 International Business Machines Corporation Minimizing electronic mailbox congestion
KR100650432B1 (en) 2004-09-02 2006-11-29 리서치 인 모션 리미티드 System and method for searching and retrieving certificates
US7171552B1 (en) 1999-11-29 2007-01-30 Cisco Technology, Inc. Encrypting information in a communications network
US20070050624A1 (en) 2003-02-20 2007-03-01 Lord Robert B Secure instant messaging system
US20070083749A1 (en) 2005-10-12 2007-04-12 The Boeing Company Systems and methods for automated exchange of electronic mail encryption certificates
US7213047B2 (en) 2002-10-31 2007-05-01 Sun Microsystems, Inc. Peer trust evaluation using mobile agents in peer-to-peer networks
US20070118874A1 (en) 2005-11-18 2007-05-24 Research In Motion Limited System and method for handling electronic messages
US20070123307A1 (en) 2005-11-30 2007-05-31 Research In Motion Limited Display of secure messages on a mobile communication device
TWI282231B (en) 2004-09-02 2007-06-01 Research In Motion Ltd System and method for searching and retrieving certificates
US7228418B1 (en) 1999-04-08 2007-06-05 France Telecom Authentication and signature method for messages using reduced size of binary units of information content and corresponding systems
EP1806683A1 (en) 2005-11-30 2007-07-11 Research In Motion Limited Display of secure messages on a mobile communication device
US20070165844A1 (en) 2005-10-14 2007-07-19 Research In Motion Limited System and method for protecting master encryption keys
US7254608B2 (en) 2002-10-31 2007-08-07 Sun Microsystems, Inc. Managing distribution of content using mobile agents in peer-topeer networks
US7254712B2 (en) 2001-06-12 2007-08-07 Research In Motion Limited System and method for compressing secure e-mail for exchange with a mobile data communication device
US7299502B2 (en) 2001-02-14 2007-11-20 Hewlett-Packard Development Company, L.P. System and method for providing customized secure access to shared documents
EP1871060A1 (en) 2006-06-23 2007-12-26 Research In Motion Limited System and method for searching a sender certificate when an e-mail address of the certificate and the sender address do not coincide
US20070299921A1 (en) 2006-06-23 2007-12-27 Research In Motion Limited System and method for handling electronic mail mismatches
US7373512B1 (en) 2000-03-27 2008-05-13 Entrust Limited Method and apparatus for providing information security to prevent digital signature forgery
US7529374B2 (en) 2002-02-02 2009-05-05 F-Secure Oyj Method and apparatus for encrypting data
US7549043B2 (en) 2004-09-01 2009-06-16 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
US7653698B2 (en) 2003-05-29 2010-01-26 Sonicwall, Inc. Identifying e-mail messages from allowed senders
EP1580953B1 (en) 2004-03-22 2011-02-09 Research In Motion Limited System and method for viewing message attachments

Patent Citations (200)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4028500A (en) 1973-05-15 1977-06-07 Martin Marietta Corporation Mobile unit supervisory control sequencer and method
EP0500245B1 (en) 1991-02-08 1996-11-06 Kabushiki Kaisha Toshiba Cipher communication system for transaction data
EP0500222B1 (en) 1991-02-14 1997-10-22 Hewlett-Packard Company Method for reconciling entries in a plurality of lists
US5778346A (en) 1992-01-21 1998-07-07 Starfish Software, Inc. System and methods for appointment reconcilation
US5457748A (en) 1992-11-30 1995-10-10 Motorola, Inc. Method and apparatus for improved security within encrypted communication devices
US20010011308A1 (en) 1992-12-02 2001-08-02 Ted H. Clark Handheld computer synchronized with a host computer
US5666530A (en) 1992-12-02 1997-09-09 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between
US5710922A (en) 1993-06-02 1998-01-20 Apple Computer, Inc. Method for synchronizing and archiving information between computer systems
US5410602A (en) 1993-09-27 1995-04-25 Motorola, Inc. Method for key management of point-to-point communications
US5634051A (en) 1993-10-28 1997-05-27 Teltech Resource Network Corporation Information management system
US20020051544A1 (en) 1993-12-03 2002-05-02 Fujitsu Limited User support system for cryptographic communication in network systems
US20040093493A1 (en) * 1995-01-17 2004-05-13 Bisbee Stephen F. System and method for electronic transmission, storage and retrieval of authenticated documents
US5778068A (en) 1995-02-13 1998-07-07 Eta Technologies Corporation Personal access management system
US6348972B1 (en) 1995-06-01 2002-02-19 Tokyo Shibaura Electric Co Network print system for allowing a printer or printers to select a host
US5623546A (en) 1995-06-23 1997-04-22 Motorola, Inc. Encryption method and system for portable data
US6289105B1 (en) 1995-07-28 2001-09-11 Kabushiki Kaisha Toshiba Method and apparatus for encrypting and transferring electronic mails
US6000000A (en) 1995-10-13 1999-12-07 3Com Corporation Extendible method and apparatus for synchronizing multiple files on two different computer systems
US5727202A (en) 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
US6313732B1 (en) 1996-04-04 2001-11-06 Motorola, Inc. Advertiser pays information and messaging system, apparatus and method
US5870030A (en) 1996-04-04 1999-02-09 Motorola, Inc. Advertiser pays information and messaging system and apparatus
US6085323A (en) 1996-04-15 2000-07-04 Kabushiki Kaisha Toshiba Information processing system having function of securely protecting confidential information
US5812671A (en) 1996-07-17 1998-09-22 Xante Corporation Cryptographic communication system
US6918038B1 (en) 1996-08-13 2005-07-12 Angel Secure Networks, Inc. System and method for installing an auditable secure network
US6209098B1 (en) 1996-10-25 2001-03-27 Intel Corporation Circuit and method for ensuring interconnect security with a multi-chip integrated circuit package
EP0841770B1 (en) 1996-11-06 2004-02-18 Nokia Corporation Method for sending a secure message in a telecommunications system
US5956707A (en) 1997-02-13 1999-09-21 Chu; Wesley W. Database system with query relaxation using type abstraction hierarchy (TAH) as query condition relaxation structure
US20010050990A1 (en) 1997-02-19 2001-12-13 Frank Wells Sudia Method for initiating a stream-oriented encrypted communication
US6061448A (en) 1997-04-01 2000-05-09 Tumbleweed Communications Corp. Method and system for dynamic server document encryption
US6229894B1 (en) 1997-07-14 2001-05-08 Entrust Technologies, Ltd. Method and apparatus for access to user-specific encryption information
GB2328125B (en) 1997-08-08 2002-04-10 Ericsson Telefon Ab L M Network control system
US6119228A (en) 1997-08-22 2000-09-12 Compaq Computer Corporation Method for securely communicating remote control commands in a computer network
US6266775B1 (en) 1997-08-25 2001-07-24 Nec Corporation Method and apparatus for displaying information and information recording medium having information displaying means
US6125369A (en) 1997-10-02 2000-09-26 Microsoft Corporation Continuous object sychronization between object stores on different computers
US6073237A (en) 1997-11-06 2000-06-06 Cybercash, Inc. Tamper resistant method and apparatus
US5991399A (en) 1997-12-18 1999-11-23 Intel Corporation Method for securely distributing a conditional use private key to a trusted entity on a remote system
US6084969A (en) 1997-12-31 2000-07-04 V-One Corporation Key encryption system and method, pager unit, and pager proxy for a two-way alphanumeric pager network
US6081601A (en) 1998-01-08 2000-06-27 Nokia Telecommunications Oy Method of implementing connection security in a wireless network
US6925568B1 (en) 1998-01-16 2005-08-02 Sonera Oyj Method and system for the processing of messages in a telecommunication system
US6421707B1 (en) 1998-02-13 2002-07-16 Lucent Technologies Inc. Wireless multi-media messaging communications method and apparatus
EP0942568A3 (en) 1998-02-17 2000-04-12 Phone.Com Inc. Centralized certificate management system for two-way interactive communication devices in data networks
US6377946B1 (en) 1998-02-25 2002-04-23 Hitachi Ltd Document search method and apparatus and portable medium used therefor
US6230186B1 (en) 1998-04-28 2001-05-08 Rhoda Yaker Private electronic message system
US20010046307A1 (en) 1998-04-30 2001-11-29 Hewlett-Packard Company Method and apparatus for digital watermarking of images
US6233572B1 (en) 1998-05-28 2001-05-15 I2 Technologies, Inc. Computer implemented system and method for high level controlled searching through a problem space
EP1096727B1 (en) 1998-05-29 2006-03-22 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
EP1096725B1 (en) 1998-05-29 2009-03-11 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6219694B1 (en) 1998-05-29 2001-04-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device having a shared electronic address
US6564320B1 (en) 1998-06-30 2003-05-13 Verisign, Inc. Local hosting of digital certificate services
US6567914B1 (en) 1998-07-22 2003-05-20 Entrust Technologies Limited Apparatus and method for reducing transmission bandwidth and storage requirements in a cryptographic security system
US20030212888A1 (en) 1998-08-26 2003-11-13 Wildish Michael Andrew System and method of looking up and validating a digital certificate in one pass
US6301658B1 (en) 1998-09-09 2001-10-09 Secure Computing Corporation Method and system for authenticating digital certificates issued by an authentication hierarchy
US6389455B1 (en) 1998-09-22 2002-05-14 Richard C. Fuisz Method and apparatus for bouncing electronic messages
JP2000104774A (en) 1998-09-25 2000-04-11 Kurashiki Kako Co Ltd Long life elastic structure
US6266420B1 (en) 1998-10-08 2001-07-24 Entrust Technologies Limited Method and apparatus for secure group communications
US7113927B1 (en) 1998-10-09 2006-09-26 Victor Company Of Japan, Limited Data distribution system, data distribution method, portable terminal with data receiving capability, portable terminal with data transmitting/receiving capability, recording medium onto which data content is recorded, encoding apparatus, and decoding apparatus
US6732273B1 (en) 1998-10-21 2004-05-04 Lucent Technologies Inc. Priority and security coding system for electronic mail messages
US20020169954A1 (en) 1998-11-03 2002-11-14 Bandini Jean-Christophe Denis Method and system for e-mail message transmission
JP2002535884A (en) 1999-01-14 2002-10-22 タンブルウィード コミュニケーションズ コーポレイション Distribution of web-based secure email messages
US6697942B1 (en) 1999-02-04 2004-02-24 Earthlink, Inc. Method for remotely managing a remote device using an electronic mail message
US6633873B1 (en) 1999-02-16 2003-10-14 Fujitsu Limited Distributed data retrieval system including mechanism for predicting an amount of response data
US7032030B1 (en) 1999-03-11 2006-04-18 John David Codignotto Message publishing system and method
US6819766B1 (en) 1999-03-30 2004-11-16 International Business Machines Corporation Method and system for managing keys for encrypted data
US7228418B1 (en) 1999-04-08 2007-06-05 France Telecom Authentication and signature method for messages using reduced size of binary units of information content and corresponding systems
US20020059375A1 (en) 1999-04-08 2002-05-16 Alvin Pivowar System and method for sharing data among a plurality of personal digital assistants
US7020708B2 (en) 1999-05-14 2006-03-28 Cingular Wireless Ii, Llc Aircraft data services
JP2001103571A (en) 1999-10-01 2001-04-13 Mitsubishi Electric Corp Mobile communication service providing system
US7003667B1 (en) 1999-10-04 2006-02-21 Canon Kabushiki Kaisha Targeted secure printing
US6931532B1 (en) 1999-10-21 2005-08-16 International Business Machines Corporation Selective data encryption using style sheet processing
US6732144B1 (en) 1999-11-19 2004-05-04 Kabushiki Kaisha Toshiba Communication method for data synchronization processing and electronic device therefor
US7171552B1 (en) 1999-11-29 2007-01-30 Cisco Technology, Inc. Encrypting information in a communications network
US7032240B1 (en) 1999-12-07 2006-04-18 Pace Anti-Piracy, Inc. Portable authorization device for authorizing use of protected information and associated method
US6829357B1 (en) 1999-12-14 2004-12-07 Trw Inc. Communication system having a transmitter and a receiver that engage in reduced size encrypted data communication
US6996720B1 (en) 1999-12-17 2006-02-07 Microsoft Corporation System and method for accessing protected content in a rights-management architecture
JP2001197055A (en) 2000-01-07 2001-07-19 Nippon Steel Corp Device, method, and service system for proxy authentication and computer-readable recording medium
US6745024B1 (en) 2000-01-10 2004-06-01 Qualcomm Incorporated System and method for preparing and sending an electronic mail communication using a wireless communications device
US7028186B1 (en) 2000-02-11 2006-04-11 Nokia, Inc. Key management methods for wireless LANs
US6779115B1 (en) 2000-02-18 2004-08-17 Digital5, Inc. Portable device using a smart card to receive and decrypt digital data
US6983367B2 (en) 2000-03-14 2006-01-03 Sony Corporation Information providing apparatus and method, information processing apparatus and method, and program storage medium
JP2001265216A (en) 2000-03-16 2001-09-28 Nippon Telegr & Teleph Corp <Ntt> Method and device for publishing public key certificate
US7373512B1 (en) 2000-03-27 2008-05-13 Entrust Limited Method and apparatus for providing information security to prevent digital signature forgery
US6725262B1 (en) 2000-04-27 2004-04-20 Microsoft Corporation Methods and systems for synchronizing multiple computing devices
US20020007453A1 (en) 2000-05-23 2002-01-17 Nemovicher C. Kerry Secured electronic mail system and method
US20020035687A1 (en) 2000-06-07 2002-03-21 Kristofer Skantze Method and device for secure wireless transmission of information
US6993137B2 (en) 2000-06-16 2006-01-31 Entriq, Inc. Method and system to securely distribute content via a network
US20020059383A1 (en) 2000-06-19 2002-05-16 Takeo Katsuda Apparatus, portable terminal unit, and system for controlling E-mail, and its method, computer-readable recording medium and program product for processing E-mail
US20020032861A1 (en) 2000-07-14 2002-03-14 Nec Corporation System and method for executing and assuring security of electronic mail for users, and storage medium storing program to cause computer to implement same method
US6661927B1 (en) 2000-07-27 2003-12-09 Motorola, Inc. System and method for efficiently encoding an image by prioritizing groups of spatially correlated coefficients based on an activity measure
US6531985B1 (en) 2000-08-14 2003-03-11 3Com Corporation Integrated laptop antenna using two or more antennas
US20020053023A1 (en) 2000-08-17 2002-05-02 Patterson Andrew John Certification validation system
US7136897B1 (en) 2000-08-22 2006-11-14 International Business Machines Corporation Minimizing electronic mailbox congestion
US20040024826A1 (en) 2000-09-07 2004-02-05 Erez Halahmi E-mail proxy
US20020035685A1 (en) 2000-09-11 2002-03-21 Masahiro Ono Client-server system with security function intermediary
US20050203855A1 (en) 2000-11-08 2005-09-15 Orchestria Limited Information management system
US20040030681A1 (en) 2000-11-21 2004-02-12 Shannon Paul Thurmond System and process for network site fragmented search
JP2002163395A (en) 2000-11-27 2002-06-07 Hitachi Software Eng Co Ltd Method for supporting confirmation of electronic certificate validity and information processor used for the same
US20040083364A1 (en) 2000-12-07 2004-04-29 Jean-Pierre Andreaux Method of secure transmission of digital data from a source to a receiver
US20020080752A1 (en) 2000-12-22 2002-06-27 Fredrik Johansson Route optimization technique for mobile IP
US20020099766A1 (en) 2001-01-24 2002-07-25 Tuli Raja Singh Portable high speed internet access device with encryption
US7299502B2 (en) 2001-02-14 2007-11-20 Hewlett-Packard Development Company, L.P. System and method for providing customized secure access to shared documents
US6904521B1 (en) 2001-02-16 2005-06-07 Networks Associates Technology, Inc. Non-repudiation of e-mail messages
US20020147905A1 (en) 2001-04-05 2002-10-10 Sun Microsystems, Inc. System and method for shortening certificate chains
US20020165967A1 (en) 2001-05-02 2002-11-07 Morgan Paul A. Global personalization engine
US20020173295A1 (en) 2001-05-15 2002-11-21 Petri Nykanen Context sensitive web services
US20020176067A1 (en) 2001-05-23 2002-11-28 Canesta, Inc. Method and system to enhance dynamic range conversion useable with CMOS three-dimensional imaging
US20030002671A1 (en) 2001-06-11 2003-01-02 Eastman Kodak Company Delivery of electronic content over a network using a hybrid optical disk for authentication
US20040171369A1 (en) 2001-06-12 2004-09-02 Little Herbert A. Certificate management and transfer system and method
US7546453B2 (en) 2001-06-12 2009-06-09 Research In Motion Limited Certificate management and transfer system and method
US20040196978A1 (en) 2001-06-12 2004-10-07 Godfrey James A. System and method for processing encoded messages for exchange with a mobile data communication device
US7254712B2 (en) 2001-06-12 2007-08-07 Research In Motion Limited System and method for compressing secure e-mail for exchange with a mobile data communication device
WO2002101580A1 (en) * 2001-06-12 2002-12-19 Research In Motion Limited Certificate management and transfer system and method
US20080016359A1 (en) 2001-06-12 2008-01-17 Godfrey James A System and method for compressing secure e-mail for exchange with a mobile data communication device
US20050163320A1 (en) 2001-06-12 2005-07-28 Brown Michael S. System and method for processing encoded messages for exchange with a mobile data communication device
US20040172453A1 (en) 2001-06-28 2004-09-02 Keith De Mendonca E-mail manager program for a wireless information device
US20040205248A1 (en) 2001-07-10 2004-10-14 Herbert A Little System and method for secure message key caching in a mobile communication device
US20030028647A1 (en) 2001-07-31 2003-02-06 Comverse, Ltd. E-mail protocol optimized for a mobile environment and gateway using same
JP2003046499A (en) 2001-08-03 2003-02-14 Nec Corp Communication system, user terminal, ic card, authentication system, and control system and program for access and communication
US20040202327A1 (en) 2001-08-06 2004-10-14 Little Herbert A. System and method for processing encoded messages
US20030074555A1 (en) 2001-10-17 2003-04-17 Fahn Paul Neil URL-based certificate in a PKI
US20030126085A1 (en) 2001-12-27 2003-07-03 Slamdunk Networks, Inc. Dynamic authentication of electronic messages using a reference to a certificate
US7529374B2 (en) 2002-02-02 2009-05-05 F-Secure Oyj Method and apparatus for encrypting data
US20030163567A1 (en) 2002-02-28 2003-08-28 Mcmorris Patrick Domain name validation using mapping table
US20030172122A1 (en) 2002-03-06 2003-09-11 Little Herbert A. System and method for providing secure message signature status and trust status indication
US20050148323A1 (en) 2002-03-20 2005-07-07 Research In Motion Limited System and method for supporting multiple certificate status providers on a mobile communication device
US20050114671A1 (en) 2002-03-20 2005-05-26 Research In Motion Ltd. System and method for transmitting and utilizing attachments
US20050149442A1 (en) 2002-03-20 2005-07-07 Research In Motion Limited Certificate information storage system and method
US20030196084A1 (en) 2002-04-12 2003-10-16 Emeka Okereke System and method for secure wireless communications using PKI
US20030198350A1 (en) 2002-04-18 2003-10-23 International Business Machines Corporation Method, system and program product for managing a size of a key management block during content distribution
JP2003348078A (en) 2002-05-27 2003-12-05 Hitachi Ltd Location authentication system and method thereof
US7127604B2 (en) 2002-07-09 2006-10-24 Texas Instruments Incorporated Changing a codec or MAC size without affecting the encryption key in PacketCable communication
JP2004048139A (en) 2002-07-09 2004-02-12 Nikon Corp Image transmission system, image relay apparatus and electronic image apparatus
US20060031300A1 (en) 2002-08-30 2006-02-09 Kock Martijn W M Method and system for the phased retrieval of data
US20040052356A1 (en) 2002-09-18 2004-03-18 Sbc Properties, L.P., Of Reno, Nv Multi-modal address book
US7213047B2 (en) 2002-10-31 2007-05-01 Sun Microsystems, Inc. Peer trust evaluation using mobile agents in peer-to-peer networks
US7254608B2 (en) 2002-10-31 2007-08-07 Sun Microsystems, Inc. Managing distribution of content using mobile agents in peer-topeer networks
US20040090457A1 (en) 2002-11-12 2004-05-13 Microsoft Corporation System and apparatus for sending complete responses to truncated electronic mail messages on a mobile device
US20040096055A1 (en) 2002-11-20 2004-05-20 Roy Williams System and method for transmitting reduced information from a certificate to perform encryption operations
JP2004179724A (en) 2002-11-25 2004-06-24 Mitsubishi Electric Corp Server apparatus, certificate verifying method, program, and computer-readable recording medium recorded with the program
US20040133520A1 (en) 2003-01-07 2004-07-08 Callas Jonathan D. System and method for secure and transparent electronic communication
US20040133775A1 (en) 2003-01-07 2004-07-08 Callas Jonathan D. System and method for secure electronic communication in a partially keyless environment
US20070050624A1 (en) 2003-02-20 2007-03-01 Lord Robert B Secure instant messaging system
US20040177248A1 (en) 2003-03-05 2004-09-09 Fuji Xerox Co., Ltd. Network connection system
US7653698B2 (en) 2003-05-29 2010-01-26 Sonicwall, Inc. Identifying e-mail messages from allowed senders
US20050005097A1 (en) 2003-06-12 2005-01-06 Minolta Co., Ltd. Communication system and method in public key infrastructure
US20050071508A1 (en) 2003-08-12 2005-03-31 Brown Michael K. System and method for processing encoded messages
US20050039100A1 (en) 2003-08-14 2005-02-17 International Business Machines Corporation Method and system for automatic error recovery in an electronic mail system
US20050055372A1 (en) 2003-09-04 2005-03-10 Microsoft Corporation Matching media file metadata to standardized metadata
US20050080642A1 (en) 2003-10-14 2005-04-14 Daniell W. Todd Consolidated email filtering user interface
US20050188219A1 (en) 2003-12-26 2005-08-25 Orange France Method and a system for communication between a terminal and at least one communication equipment
US20050160292A1 (en) 2004-01-21 2005-07-21 Microsoft Corporation Encryption to BCC recipients with S/MIME
US20050222991A1 (en) 2004-02-04 2005-10-06 Kazuyuki Ikenoya Information providing apparatus, information providing method, information providing program, and recording medium
US20050210289A1 (en) 2004-03-22 2005-09-22 Brown Michael K System and method for viewing message attachments
EP1580953B1 (en) 2004-03-22 2011-02-09 Research In Motion Limited System and method for viewing message attachments
US20050246763A1 (en) 2004-03-25 2005-11-03 National University Of Ireland Secure digital content reproduction using biometrically derived hybrid encryption techniques
US20060015722A1 (en) 2004-07-16 2006-01-19 Geotrust Security systems and services to provide identity and uniform resource identifier verification
US20130013917A1 (en) 2004-08-09 2013-01-10 Research In Motion Limited System and method for enabling bulk retrieval of certificates
CA2476914A1 (en) 2004-08-09 2006-02-09 Research In Motion Limited System and method for certificate searching and retrieval
US20080306922A1 (en) 2004-08-09 2008-12-11 Research In Motion Limited System and method for enabling bulk retrieval of certificates
US7430663B2 (en) 2004-08-09 2008-09-30 Research In Motion Limited System and method for enabling bulk retrieval of certificates
US20060036848A1 (en) 2004-08-09 2006-02-16 Research In Motion Limited System and method for enabling bulk retrieval of certificates
US8301878B2 (en) 2004-08-09 2012-10-30 Research In Motion Limited System and method for enabling bulk retrieval of certificates
US20060036849A1 (en) 2004-08-09 2006-02-16 Research In Motion Limited System and method for certificate searching and retrieval
US20060036865A1 (en) 2004-08-10 2006-02-16 Research In Motion Limited Server verification of secure electronic messages
US20090199007A1 (en) 2004-09-01 2009-08-06 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
CA2517209C (en) 2004-09-01 2011-07-26 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
US20130007447A1 (en) 2004-09-01 2013-01-03 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
AU2005204221B2 (en) 2004-09-01 2008-01-24 Blackberry Limited Providing certificate matching in a system and method for searching and retrieving certificates
US8296829B2 (en) 2004-09-01 2012-10-23 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
KR101072942B1 (en) 2004-09-01 2011-10-17 리서치 인 모션 리미티드 Providing certificate matching in a system and method for searching and retrieving certificates
EP1633100B1 (en) 2004-09-01 2008-07-02 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
TW200629858A (en) 2004-09-01 2006-08-16 Research In Motion Ltd Providing certificate matching in a system and method for searching and retrieving certificates
JP4555195B2 (en) 2004-09-01 2010-09-29 リサーチ イン モーション リミテッド Providing certificate matching in systems and methods for retrieving and retrieving certificates
CN100566236C (en) 2004-09-01 2009-12-02 捷讯研究有限公司 The method that credentials match is provided in system and is used to search for and obtain certificate
EP1936920B1 (en) 2004-09-01 2009-03-25 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
US7549043B2 (en) 2004-09-01 2009-06-16 Research In Motion Limited Providing certificate matching in a system and method for searching and retrieving certificates
US7640428B2 (en) 2004-09-02 2009-12-29 Research In Motion Limited System and method for searching and retrieving certificates
EP1633101B1 (en) 2004-09-02 2008-04-09 Research In Motion Limited System and method for searching and retrieving certificates
AU2005204223B2 (en) 2004-09-02 2007-11-29 Blackberry Limited System and method for searching and retrieving certificates
CN100531029C (en) 2004-09-02 2009-08-19 捷讯研究有限公司 System and method for searching and retrieving certificates
TWI282231B (en) 2004-09-02 2007-06-01 Research In Motion Ltd System and method for searching and retrieving certificates
US20060059332A1 (en) 2004-09-02 2006-03-16 Research In Motion Limited System and method for searching and retrieving certificates
KR100650432B1 (en) 2004-09-02 2006-11-29 리서치 인 모션 리미티드 System and method for searching and retrieving certificates
US8209530B2 (en) 2004-09-02 2012-06-26 Research In Motion Limited System and method for searching and retrieving certificates
US20100100730A1 (en) 2004-09-02 2010-04-22 Research In Motion Limited System and method for searching and retrieving certificates
JP4530953B2 (en) 2004-09-02 2010-08-25 リサーチ イン モーション リミテッド System and method for retrieving and retrieving certificates
CA2517211C (en) 2004-09-02 2011-05-03 Research In Motion Limited System and method for searching and retrieving certificates
US7627896B2 (en) 2004-12-24 2009-12-01 Check Point Software Technologies, Inc. Security system providing methodology for cooperative enforcement of security policies during SSL sessions
US20060143700A1 (en) 2004-12-24 2006-06-29 Check Point Software Technologies, Inc. Security System Providing Methodology for Cooperative Enforcement of Security Policies During SSL Sessions
US7664947B2 (en) 2005-10-12 2010-02-16 The Boeing Company Systems and methods for automated exchange of electronic mail encryption certificates
US20070083749A1 (en) 2005-10-12 2007-04-12 The Boeing Company Systems and methods for automated exchange of electronic mail encryption certificates
US20070165844A1 (en) 2005-10-14 2007-07-19 Research In Motion Limited System and method for protecting master encryption keys
US20070118874A1 (en) 2005-11-18 2007-05-24 Research In Motion Limited System and method for handling electronic messages
EP1806683A1 (en) 2005-11-30 2007-07-11 Research In Motion Limited Display of secure messages on a mobile communication device
US20070123307A1 (en) 2005-11-30 2007-05-31 Research In Motion Limited Display of secure messages on a mobile communication device
US7814161B2 (en) 2006-06-23 2010-10-12 Research In Motion Limited System and method for handling electronic mail mismatches
CA2592680C (en) 2006-06-23 2012-03-27 Research In Motion Limited System and method for handling electronic mail mismatches
US20070299921A1 (en) 2006-06-23 2007-12-27 Research In Motion Limited System and method for handling electronic mail mismatches
US8312165B2 (en) 2006-06-23 2012-11-13 Research In Motion Limited System and method for handling electronic mail mismatches
EP1871060A1 (en) 2006-06-23 2007-12-26 Research In Motion Limited System and method for searching a sender certificate when an e-mail address of the certificate and the sender address do not coincide
US20110029627A1 (en) 2006-06-23 2011-02-03 Research In Motion Limited System and method for handling electronic mail mismatches
US20130067009A1 (en) 2006-06-23 2013-03-14 Research In Motion Limited System and method for handling electronic mail mismatches

Non-Patent Citations (119)

* Cited by examiner, † Cited by third party
Title
"Blackberry Security with the S/MIME Support Package version 1.5", Research in Motion Limited, Dec. 17, 2003, pp. 1-24.
"BlackBerry with the S/MIME Support Package Version 4.0 User Guide Supplement", URL:http://www.blackberry.com/knowlesdgecenterpublic/livelink.exe/fetch/2000/8067/645045/8533/348781/1181993/SMIME-Support-Package-version-4.0-User-Guide-Supplement?nodeid=1181919&vernum=0>, Dec. 4, 2006, paragraphs 0001-0005, XP002410691.
Advisory Action. Co-pending U.S. Appl. No. 12/405,551. Dated: May 5, 2011.
Amendment. Co-pending U.S. Appl. No. 10/931,109. Dated: Jul. 18, 2008.
Australian Notice of Acceptance. Application No. 2005204223. Dated: Nov. 16, 2007.
Australian Search Report. Application No. 2005204223. Dated: Oct. 12, 2006.
Berson T. et al.: "Cryptography as a network service" 8th Annual Symposium on Network and Distributed System Security. (NDSS'01) Internet Soc Reston, VA, USA, Feb. 7, 2001, Feb. 9, 2001 pp. 1-12, XP002551706 the whole document.
Blom et al. "Conversational IP Multimedia Security", 4th International Workshop on Mobile and Wireless Communications Network, Sep. 9-11, 2002, pp. 147-151.
Brown et al., "PGP in Constrained Wireless Devices," Proceedings of the 9th Usenix Security Symposium, Denver, CO, USA, pp. 247-261 (Aug. 14-17, 2000).
Brown, Ian. et al., "A Proxy Approach to E-mail Security," Software Practice & Experience, John Wiley & Sons Ltd., Chichester, GB, vol. 29, No. 12, pp. 1049-1060 (Oct. 1999).
Butrico, M., et al.: "Enterprise Data Access from Mobile Computers: An End-to-end Story", Research Issues in Data Engineering, Feb. 28, 2000, pp. 9-16, XP010377083-8 pgs.
Certificate of Grant. Hong Kong Patent Application No. 06108965.8. Dated: Jun. 13, 2008.
Certificate of Grant. Singapore Patent Application No. 200505624-7. Dated: Mar. 31, 2008.
Chadwick et al., "Modifying LDAP to Support X.509-based PKIs", In Seventeenth annual IFIP WG 11.3 Working Conference on Database and Applications Security, Colorado, Aug. 2003, pp. 1-9. *
Chinese Certificate of Invention Patent with English translation. Chinese Patent No. ZL200510098012.3. Dated: Aug. 19, 2009.
Cole, "An Architecture for a Mobile OSI Mail Access System," IEEE Journal on Selected Areas in Communications, IEEE Inc., New York, USA, vol. 7, No. 2, pp. 249-256 (Feb. 1989).
Co-pending U.S. Appl. No. 10/931,109, "Providing Certificate Matching in a System and Method for Searching and Retrieving Certificates", Filed Sep. 1, 2004.
Co-pending U.S. Appl. No. 11/473,313, "System and Method for Handling Electronic Mail Mismatches", Filed Jun. 23, 2006.
Co-pending U.S. Appl. No. 12/405,551, "Providing Certificate Matching in a System and Method for Searching and Retrieving Certificates", Filed Mar. 17, 2009.
Co-pending U.S. Appl. No. 12/896,224, "System and Method for Handling Electronic Mail Mismatches", Filed Oct. 1, 2010.
Co-pending U.S. Appl. No. 13/615,098, "Providing Certificate Matching in a System and Method for Searching and Retrieving Certificates", Filed Sep. 13, 2012.
Co-pending U.S. Appl. No. 13/672,073, "System and Method for Handling Electronic Mail Mismatches", Filed Nov. 8, 2012.
Crocker, S. et al.: "MIME Object Security Services; rfc1848.text", IETF Standard, Internet Engineering Task Force, IETF, CH, Oct. 1995, XP015007633.
Decision to Grant a European Patent pursuant to Article 97(1) EPC. European Patent Application No. 04104240.9. Dated: Mar. 13, 2008.
Deroest, J.: "Ubiquitous Mobile Computing"; Sunexpert Magazine: Jul. 1998, pp. 54-56, XP002213003-3 pgs.
Dusse et al.: "S/MIME Version 2 Certificate Handling", Database IETF RFC Online IETF: RFC 2312, Mar. 1998, pp. 1-20 (Chapter 2.1, Chapter 4.1), XP0022220385.
Dusse, "S/MIME Version 2 Message Specification," The Internet Society, pp. 1-37 (Mar. 1998).
Encrypt Pre-shared Keys in Cisco IOS Router Configuration Example, Document 1D 46420 Cisco Systems, Internet Address: http://www.cisco.com/en/US/tech/tk583/tk372/technologies-configuration-example09186a0080112336.shtml.
Eskicioglu et al. "A Key Transport Protocol Based on Secret Sharing Applications to Information Security", IEEE Transactions on Consumer Electronics, vol. 48, No. 4, Nov. 2002, pp. 816-824.
European Communication under Rule 51(4) EPC. Application No. 04104240.9. Dated: Oct. 10, 2007.
European Search Report. Application No. 04104240.9. Dated: Dec. 6, 2006.
European Search Report. European Application No. 04104240.9. Dated: Feb. 10, 2005.
Examiner Interview Summary. Co-pending U.S. Appl. No. 11/473,313. Dated: Jun. 14, 2010.
Final Office Action. Co-pending U.S. Appl. No. 11/473,313. Dated: Dec. 3, 2009.
Final Office Action. Co-pending U.S. Appl. No. 12/405,551. Dated: Feb. 23, 2011.
Final Office Action. Co-pending U.S. Appl. No. 12/896,224. Dated Mar. 2, 2012.
First Office Action. Canadian Patent Application No. 2,517,211 Dated: Jul. 13, 2009.
First Office Action. Chinese Patent Application No. 200510098012.3. Dated: Nov. 28, 2008.
First Office Action. Co-pending U.S. Appl. No. 12/405,551. Dated: Oct. 25, 2010.
First Office Action. Indian Patent Application No. 2281/DEL/2005. Dated: Mar. 1, 2007.
Fumy et al. Principles of Key Management, IEEE Journal on Selected Areas in Communications, VDI, 11, No. 5, Jun. 1993, pp. 785-793.
Gong, "Multicast Security and its Extension to a Mobile Environment," Wireless Networks 1, J.C. Baltzer AG, Science Publishers, pp. 281-295 (1995).
Gutmann, Peter. "A Reliable, Scalable General-purpose Certificate Store", ACSAC 2000.
Hametvaara, Vesa, "Certificate Management in Mobile Devices", May 2002.
Harris, "Content Privacy and Content Security Working Together," Internet Article, Content Technologies White Paper, pp. 1-10 (Sep. 1999).
Hoffman: "Enhanced Security Services for S/MIME", Database IETF RFC Online IETF; RFC 2634, Jun. 1999, pp. 1-58 (Chapter 3, pp. 24-32), XP002220386.
Housley, R. "Cryptographic Message Syntax (CMS)" (RFC 3852), Jul. 2004.
Housley, R. et al., "Internet X.509 Public Key Infrastructure Certificate and CRL Profile (RFC 2459)", Jan. 1999.
Indian Exam Report. Indian Application No. 2281/DEL/2005. Dated: Feb. 27, 2008.
Indian Patent Certificate. Indian Patent Application No. 2281/DEL/2005. Dated: Mar. 7, 2008.
Interview Summary. Co-pending U.S. Appl. No. 13/672,073. Dated: Mar. 13, 2013.
Interview Summary. U.S. Appl. No. 12/405,551. Dated: Jul. 19, 2012.
Interview Summary. U.S. Appl. No. 13/615,098. Dated: Jul. 4, 2013.
ITU-T, "Information Technology-Open Systems Interconnection-The Directory: Public-key and Attribute Certificate Frameworks", Mar. 2000.
Japanese First Office Action (English translation). Application No. 2005-253511. Dated: Feb. 16, 2009.
Japanese Second Office Action. Japanese Application No. 2005-253511. Dated: Jan. 5, 2010.
Jing, Jin et al.: "Client-server Computing in Mobile Environments"; ACM Computing Surveys; Jun. 1999, vol. 31, No. 2, pp. 117-157, XP002212945-41 pgs.
Katsuro Inaya et al., Imakoso tsukau Windows CE (time to use Windows CE), Monthly ASCII, Oct. 1, 1999, vol. 23, No. 10, pp. 266-285.
Kiely, Don, SQL Server 2005 Secures Your Data Like Never Before, Sep. 29, 2005. Internet Address: http://www.devx.com/codemag/Article/293512trk=DXRSS-DB.
Korean Letters Patent (with English translation). Korean Application No. 10-2005-0081337. Dated: Nov. 21, 2006.
Kotzanikolaou et al., "Hybrid Key Establishment for Multiphase Self-Organized Sensor Networks", 6th IEEE International Symposium on a World of Wireless Mobile and Multimedia Networks, Jun. 13-16, 2005, pp. 581-587.
Lai, "A mobile subscriber proxy preserving writer-to-reader message security," Military Communications Conference, Milcom '96, Conference Proceedings, IEEE McLean, VA, USA Oct. 21-24, 1996, New York, NY, USA, IEEE, pp. 461-467 (Oct. 21, 1996).
Levien, R.: "Protecting Internet E-Mail From Prying Eyes", Data Communications, McGraw Hill. New York, US, vol. 25, No. 6 (May 1, 1996), pp. 117-118, 120, 122, XP000587586.
Mambo, "Proxy Signatures: Delegation of the Power to Sign Messages," IEICE Transactions on Fundamentals of Electronics, Communications and Computer Sciences, IEICE Tokyo, Japan, vol. E79-A, No. 9, pp. 1338-1353 (Sep. 1, 1996).
Miyagawa, "Internet security course starting from zero" second period, ASCII network PRO, vol. 5, No. 6, Japan ASCII Corporation, Jun. 2000, vol. 5, pp. 96-99.
Myers, M. et al., "Certificate Management Messages over CMS (RFC 2797)", Apr. 2000.
Myers, M. et al., X.509 Internet Public Key Infrastructure Online Certificate Status Protocol-OCSP, RFC2560 (Jun. 1999).
Nakajima, Tatsuo et al.: "Adaptive Continuous Media Applications in Mobile Computing Environments"; Multimedia Computing and Systems '97 Proceedings, IEEE International Conference on Ottawa, Ont., Canada, Jun. 3, 1997, pp. 152-160, XP010239184-9 pgs.
Notice of Allowance. Canadian Patent Application No. 2,517,211 Dated: Sep. 30, 2010.
Notice of Allowance. Chinese Patent Application No. 200510098012.3. Dated: May 8, 2009.
Notice of Allowance. Co-pending U.S. Appl. No. 11/473,313. Dated: Jun. 14, 2010.
Notice of Allowance. Co-pending U.S. Appl. No. 13/672,073. Dated: Mar. 12, 2013.
Notice of Allowance. Japanese Application No. 2005-253511. Dated: May 20, 2010.
Notice of Allowance. U.S. Appl. No. 12/405,551. Dated: Jul. 19, 2012.
Notice of Allowance. U.S. Appl. No. 12/896,224. Dated: Jul. 11, 2012.
Notice of Allowance. U.S. Appl. No. 13/615,098. Dated: Jun. 28, 2013.
Office Action. Co-pending U.S. Appl. No. 12/896,224. Dated Oct. 31, 2011.
Policht, Marcin, SQL Server 2005 Security-Part 3 Encryption, Database Journal Internet Address: http://www.databasejournal.com/features/mssql/article.php/3483931.
Preliminary Amendment. U.S. Appl. No. 13/615,098. Dated: Jun. 10, 2013.
Prosecution Documents for U.S. Appl. No. 10/931,983, issued to Patent No. 7,640,428 on Dec. 29, 2009.
Prosecution Documents for U.S. Appl. No. 12/645,003, issued to Patent No. 8,209,530 on Jun. 26, 2012.
Ramsdell, B. "S/MIME Version 3 Certificate Handling" (RFC 2632), Jun. 1999.
Ramsdell, B. "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling" (RFC3850), Jun. 2004.
Request for Continued Examination (RCE). Co-pending U.S. Appl. No. 10/931,109. Dated: Dec. 15, 2008.
Request for Continued Examination (RCE). Co-pending U.S. Appl. No. 12/405,551. Dated: May 17, 2011.
Request for Continued Examination. Co-pending U.S. Appl. No. 12/405,551. Dated: Apr. 19, 2011.
Research in Motion Limited, Blackberry Security White Paper Release 4.0 2005 Internet Address: http://blackberry.comlknowledgecenterpublicllivelink.exe?func=II&objld=S2S044&objAction=browse&sort=name.
Response and Request for Continued Examination. Co-pending U.S. Appl. No. 11/473,313. Dated: May 3, 2010.
Response. Co-pending U.S. Appl. No. 11/473,313. Dated: Jul. 24, 2009.
Response. Co-pending U.S. Appl. No. 12/405,551. Dated Dec. 15, 2010.
Response. Co-pending U.S. Appl. No. 12/405,551. Dated: Apr. 19, 2011.
Response. Co-pending U.S. Appl. No. 12/896,224. Dated Jan. 31, 2012.
Response. European Application No. 04104240.9. Dated: Aug. 25, 2005.
Response. European Application No. 04104240.9. Dated: Mar. 29, 2007.
Response. European Application No. 04104240.9. Dated: Mar. 30, 2005.
Response. U.S. Appl. No. 12/405,551. Dated: Jul. 5, 2012.
Russell, S.: "Fast Checking of Individual Certificate Revocation on Small Systems"; Computer Security Applications Conference, Phoenix, AZ, Dec. 6, 1999, pp. 249-255, XP010368617-7pgs.
Sawano, Hiroyuki, Create a Secure Electronic Mail Environment with S/MIME!, @IT Security & Trust, May 30, 2001, URL: http://www.atmarkit.co.jp/fsecurity/specia1/04smime/smime01.html.
Schumacher: "AutoPGP FAQ, Version 1", Internet Newsgroup, ′Online! (Apr. 19, 1994), XP002230742.
Schumacher: "AutoPGP FAQ, Version 1", Internet Newsgroup, 'Online! (Apr. 19, 1994), XP002230742.
Second Office Action. Canadian Patent Application No. 2,517,211 Dated: Mar. 19, 2010.
Shikii, C++ Builder component programming [26], DDJ vol. 8, No. 3, Japan, Shoei Corporation, Mar. 1999, vol. 8, pp. 137-142.
Singapore Exam Report. Singapore Application No. 200505624-7. Dated: Sep. 19, 2006.
Singapore Office Action. Application No. 200505624-7. Dated: Feb. 17, 2006.
Stallings, W.: "S/MIME: E-Mail Gets Secure", Byte, McGraw-Hill Inc., St. Peterborough, US vol. 23, No. 7, Jul. 1998, pp. 41-42, XP000774260.
Subramanyam, "Security in Mobile Systems," Reliable Distributed Systems, 1998 Proceedings, 17th IEEE Symposium on W. Lafayette, IN, USA, Oct. 20-23, 1998, Los Alamitos, CA, USA, IEEE Comput. Soc., USA, pp. 407-412 (Oct. 20, 1998).
Syverson, "Limitations on Design Principles for Public Key Protocols," Security and Privacy, 1996, Proceedings, 1996 IEEE Symposium on Oakland, CA, USA, May 6-8, 1996, Los Alamitos, CA, USA, IEEE Comput. Soc., USA, pp. 62-72 (May 6, 1996).
Taiwanese Letters Patent with English translation. Taiwanese Patent No. 1282231. Dated Jun. 1, 2007.
Terminal Disclaimers. Co-pending U.S. Appl. No. 13/672,073. Dated: Feb. 21, 2013.
Torvinen, "Wireless PKI: Fundamentals," Internet Article, Radicchio White Paper, pp. 1-15 (2000).
United States Final Office Action. Co-pending U.S. Appl. No. 11/473,313. Dated: Dec. 3, 2009.
United States Notice of Allowance and Fee(s) Due. Co-pending U.S. Appl. No. 10/931,109. Dated: Jan. 5, 2009.
United States Notice of Allowance and Fee(s) Due. Co-pending U.S. Appl. No. 10/931,109. Dated: Sep. 17, 2008.
United States Office Action. Co-pending U.S. Appl. No. 10/931,109. Dated: Apr. 22, 2008.
United States Office Action. Co-pending U.S. Appl. No. 11/473,313. Dated: Apr. 1, 2009.
United States Supplemental Notice of Allowability. Co-pending U.S. Appl. No. 10/931,109. Dated: Mar. 17, 2009.
United States Supplemental Notice of Allowability. Co-pending U.S. Appl. No. 10/931,109. Dated: Sep. 29, 2008.
Wasley, D.L.: "Improving Digital Credential Management in Browsers"; Internet article, Jul. 21, 2000, pp. 1-8, XP002213004-9 pgs.
Zollner J.: "Gateway to Overcome Incompatibilities of Security Mechanisms" Reliable Distributed Systems, 1999. Proceedings of the 19th IEEE Symposium on Lausanne, Switzerland Oct. 19-22, 1999, Los Alamitos, CAL, USA, IEEE Compu. Soc, US Oct. 19, 1999, pp. 372-377, XP 010357040 ISBN: 978-0-7695-0290-8 the whole document.

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8943156B2 (en) 2006-06-23 2015-01-27 Blackberry Limited System and method for handling electronic mail mismatches

Also Published As

Publication number Publication date
US7640428B2 (en) 2009-12-29
US20120239927A1 (en) 2012-09-20
US20100100730A1 (en) 2010-04-22
US20060059332A1 (en) 2006-03-16
US8209530B2 (en) 2012-06-26

Similar Documents

Publication Publication Date Title
US8566582B2 (en) System and method for searching and retrieving certificates
US8561158B2 (en) Providing certificate matching in a system and method for searching and retrieving certificates
CA2517209C (en) Providing certificate matching in a system and method for searching and retrieving certificates
US9621352B2 (en) System and method for verifying digital signatures on certificates
US8850188B2 (en) Updating certificate status in a system and method for processing certificates located in a certificate search
US8589677B2 (en) System and method for retrieving related certificates
US8301878B2 (en) System and method for enabling bulk retrieval of certificates
US8667266B2 (en) System and method for sending encrypted messages to a distribution list
EP1653655B1 (en) System and method for verifying digital signatures on certificates
US20060036849A1 (en) System and method for certificate searching and retrieval
CA2517211C (en) System and method for searching and retrieving certificates
EP1632871A1 (en) System and method for retrieving related certificates

Legal Events

Date Code Title Description
AS Assignment

Owner name: RESEARCH IN MOTION LIMITED, ONTARIO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ADAMS, NEIL P.;BROWN, MICHAEL S.;LITTLE, HERBERT A.;SIGNING DATES FROM 20040924 TO 20040928;REEL/FRAME:028285/0827

AS Assignment

Owner name: BLACKBERRY LIMITED, ONTARIO

Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:030919/0108

Effective date: 20130709

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

AS Assignment

Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103

Effective date: 20230511

AS Assignment

Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND

Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064269/0001

Effective date: 20230511