1. An organic-inorganic hybrid composition, which comprises:
a) a high Tg epoxy resin system comprising an epoxy resin with the following structure:
\u2003wherein n is 0\u201310; and
b) ferroelectric ceramic particles having two or more particle size distributions, wherein a first particle size distribution is 1\u2013100 nm, and a second particle size distribution is 300 nm\u20135 \u03bcm.
2. The composition as claimed in claim 1, wherein said ferroelectric ceramic particles have two dominant particle size distributions, wherein said first particle size distribution is 50\u2013100 nm, and said second particle size distribution is 0.5\u20135 \u03bcm, and the ferroelectric ceramic particles with the first particle size distribution constitute 1\u02dc40 wt % of the total ferroelectric ceramic particles.
3. The composition as claimed in claim 1, wherein said ferroelectric ceramic particles constitute 50\u201395 wt % of the total solid content of said composition.
4. The composition as claimed in claim 1, wherein said ferroelectric ceramic particles are BaTiO3, SrTiO3, Ba(Sr)TiO3, or any one of them implanted with metal ions.
5. The composition as claimed in claim 1, wherein said epoxy resin system further comprises one or more epoxy resins selected from the group consisting of bisphenol A epoxy resin, cycloaliphatic epoxy resin, naphthalene epoxy resin, diphenylene epoxy resin, and phenolic novolac epoxy resin.
6. The composition as claimed in claim 1, wherein said epoxy resin system further comprises a macromolecular dispersant.
7. The composition as claimed in claim 6, wherein said macromolecular dispersant is selected from the group consisting of polyester, polyamide, and copolymers thereof, wherein said macromolecular dispersant constitutes 2\u02dc10 wt % of the total solid content of said composition.
8. The composition as claimed in claim 6, wherein said epoxy resin system further comprises a macromolecular flexibilizer.
9. The composition as claimed in claim 8, wherein said epoxy resin system further comprises a diluent or an adhesion promoter.
10. The composition as claimed in claim 9, wherein said diluent or said adhesion promoter is:
11. The composition as claimed in claim 8, wherein said epoxy resin system further comprises a curing agent selected from the group consisting of polyamine, phenol resin, and acid anhydride.
12. A cured organic-inorganic hybrid material, which is cured from said composition claimed in claim 11.
13. The cured organic-inorganic hybrid material as claimed in claim 12, wherein said curing is carried out by heating said composition.
14. The cured organic-inorganic hybrid material as claimed in claim 13, wherein said heating is carried out at 160\u02dc200\xb0 C. for 2\u02dc6 hours.
15. The composition as claimed in claim 8, wherein said macromolecular flexibilizer is selected from the group consisting of polyester, polyamide, polyamide-imide, polyvinyl butyral, synthetic rubber, polycaprolactone, and aliphatic epoxy resin, and wherein said macromolecular flexibilizer constitutes 0.5\u02dc20 wt % of the total solid content of said composition.
16. The composition as claimed in claim 8, wherein said epoxy resin system further comprises a silane coupling agent to enhance the dispersion and compatibility of said ferroelectric ceramic particles in said composition.
17. The composition as claimed in claim 16, wherein said silane coupling agent is epoxysilane or aminosilane.
18. The composition as claimed in claim 8, wherein said epoxy resin system further comprises an organic solvent.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for distributing a trusted authority list, comprising:
identifying an entity as being a trusted certification authority;
maintaining a trusted authority list on a server, the trusted authority list containing an entity identifier that uniquely identifies the entity;
maintaining a digital certificate associated with the entity identifier on one or more computer-readable media; and
providing access to one or more client computers to allow the client computers to download the digital certificate, thereby accepting the entity as a trusted authority for the client computers.
2. The method as recited in claim 0, wherein:
the trusted authority list further comprises more than entity identifier, each entity identifier being uniquely associated with an entity that has been identified as being a trusted certification authority;
the maintaining a digital certificate further comprises maintaining a plurality of digital certificates, each digital certificate being associated with one or more entity identifiers; and
the client computers are configured to download more than one of the digital certificates, thereby accepting each entity having an entity identifier in the trusted authority list as a trusted authority for the client computers.
3. The method as recited in claim 0, further comprising adding an entity as a trusted certification authority by adding an entity identifier associated with the entity to the trusted authority list and maintaining a digital certificate associated with the entity.
4. The method as recited in claim 0, further comprising removing an entity as a trusted certification authority by removing an entity identifier associated with the entity from the trusted authority list.
5. A method for updating a trusted certification authority list, comprising:
encountering a digital certificate during a secure transaction;
identifying an entity associated with the digital certificate;
referring to a trusted root list to determine if the entity is trusted to participate in a secure transaction;
if the entity is identified in the trusted root list, proceeding with the secure transaction;
if the entity is not identified in the trusted root list, accessing a remote trusted root list to determine if the entity is identified in the remote trusted root list; and
proceeding with the secure transaction if the entity is identified in the remote trusted root list.
6. The method as recited in claim 5, further comprising downloading a digital certificate associated with the entity if the entity is identified in the remote trusted root list.
7. The method as recited in claim 5, further comprising providing a user option to proceed with the secure transaction if the entity cannot be identified in the remote trusted root list.
8. The method as recited in claim 5, wherein if the trusted root list does not exist, the remote trusted root list is downloaded to become the trusted root list.
9. The method as recited in claim 5, wherein the referring to a trusted root list to determine if the entity is trusted further comprises determining that the entity is trustworthy if an entity identifier uniquely associated with the entity is i identified in the trusted root list.
10. A method for updating a trusted authority list on a client computer, comprising:
maintaining a trusted root list on a server computer that is accessible by a plurality of client computers, the trusted root list containing one or more entity identifiers, each entity identifier being uniquely associated with an entity that has been identified as a trusted certification authority;
maintaining a digital certificate for each entity having an entity identifier;
transmitting at least one digital certificate to the client computer upon request from the client computer; and
wherein the client computer accesses the server computer and requests transmission of the digital certificate when the client computer encounters an entity associated with the digital certificate in an electronic transaction and the client computer does not have information that the encountered entity is trustworthy.
11. A method for determining if an entity encountered in an electronic transaction can be trusted to handle a secure transaction, comprising:
examining a digital certificate associated with the encountered entity to determine an identity of a certifying authority that issued the digital certificate;
determining whether the certifying authority is identified in a trusted root list;
if the certifying authority is not identified in the trusted root list, accessing a remote trusted root list;
determining whether the certifying authority is identified in the remote trusted root list; and
if the certifying authority is identified in the remote trusted root list, proceeding with the secure transaction.
12. The method as recited in claim 11, further comprising downloading a digital certificate associated with the certifying authority if the certifying authority is identified in the remote trusted root list.
13. The method as recited in claim 11, further comprising establishing the integrity of the remote trusted root list and proceeding only if the remote trusted root list has not been compromised.
14. The method as recited in claim 11, further comprising:
downloading a digital certificate associated with the certifying authority if the certifying authority is identified in the remote trusted root list; and
adding an identifier that is uniquely associated with the certifying authority to a local trusted root list.
15. The method as recited in claim 11, further comprising presenting a user option to continue with the secure transaction if the certifying authority is not identified in the remote trusted root list.
16. A system, comprising:
a trusted root list that includes a digital identifier for each of one or more trusted certifying authorities;
an authorizer configured to determine if an entity encountered during an online transaction is a trusted certifying authority by locating a digital identifier in the trusted root list that is associated with the encountered entity; and
wherein the authorizer is further configured to access a remote trusted root list and determine if the digital identifier associated with the encountered entity is identified in the remote trusted root list if the digital identifier is not included in the trusted root list.
17. The system as recited in claim 16, further comprising a browser configured to browse a network.
18. The system as recited in claim 16, wherein the digital identifier included in the trusted root list is associated with a root certification authority that certified the entity or certified a certification authority that ultimately certified the entity as being a trusted certification authority.
19. The system as recited in claim 16, wherein the authorizer is further configured to download a digital certificate associated with the entity and add the digital identifier to the located trusted root list if the digital identifier associated with the entity is located in the trusted root list but not in the local trusted root list.
20. The system as recited in claim 16, wherein the authorizer is further configured to present a user prompt allowing a secure transaction to proceed if the digital identifier associated with the entity is not found in the trusted root list or the remote trusted root list.
21. An operating system, comprising:
a local trusted root list that includes one or more digital identifiers, each digital identifier being associated with a root certification authority that may certify a trusted authority for executing secure transactions over an electronic network;
an authorization module configured to determine if an entity encountered on a network while attempting an electronic transaction can be trusted for a secure transaction by logically connecting a digital identifier associated with the entity with a digital identifier contained in the local trusted root list; and
wherein the authorization module is further configured to access a remote trusted root list if the digital identifier associated with the entity cannot be logically connected to a digital identifier contained in the local trusted root list.
22. The operating system as recited in claim 21, wherein the authorization module, in the event that the digital identifier is contained in the remote trusted root list, is further configured to:
download a digital certificate associated with the entity; and
add a digital identifier uniquely associated with the entity to the local trusted root list.
23. The operating system as recited in claim 21, wherein the authorization module is, in the event that the digital identifier is contained in the remote trusted root list, further configured to add the digital identifier from the remote trusted root list to the local trusted root list.
24. The operating system as recited in claim 21, wherein the authorizer is further configured to allow the secure transaction to proceed if the digital identifier associated with the entity is included in the trusted root list or the remote trusted root list.
25. The operating system as recited in claim 21, wherein the authorizer is further configured to allow the secure transaction to proceed if the digital identifier associated with the entity can be logically connected to a digital identifier in the trusted root list or the remote trusted root list.
26. The operating system as recited in claim 21, wherein the authorizer is further configured to provide a user option to allow the secure transaction to proceed even if the digital identifier associated with the entity cannot be logically connected to a digital identifier in the trusted root list or the remote trusted root list.
27. One or more computer-readable media containing computer-executable instructions that, when executed on a computer, perform the following steps:
attempting to authorize an entity to participate in a secure transaction by identifying a certification authority in a trusted root list that corresponds to a digital identifier associated with the entity;
if the digital identifier does not correspond with a certification authority included in the trusted root list, accessing a remote trusted root list;
attempting to locate a certification authority that corresponds with the digital identifier associated with the entity in the remote trusted root list;
if the certification authority is found, proceeding with the secure transaction.
28. The one or more computer-readable media as recited in claim 27, further comprising the step of presenting an option to proceed with the secure transaction if the certification authority is not found in the remote trusted root list.
29. The one or more computer-readable media as recited in claim 27, wherein the secure transaction is terminated if the certification authority is not found.
30. The one or more computer-readable media as recited in claim 27, wherein the certification authority is represented in the trusted root list by a digital identifier.