With the holiday season officially underway and the ground white with fresh snow, the time is perfect for celebrating the Village of Springville's annual A Very Merry Main Street.
Kicking off a full month of festivities, the most wonderful time of the year begins Saturday, Nov. 24 from 10 a.m. to 4 p.m. in the downtown Springville area.
Celebrated on Small Business Saturday, the village's own small businesses encourage community members and visitors to stroll down Main Street and get your holiday shopping done.
Stick around until the tree lighting in M&T Bank at 4 p.m.
Nearly 40 businesses are participating in A Very Merry Main Street this year with specials available for Small Business Saturday. Shoppers will also have a chance to win a $150 cash prize or a Very Merry Gift Basket.
Local merchants not located on Main Street will set up inside Sheret Jewelers, Love INC, Springville Hardware, Springville Center for the Arts, Concord Land Realty, Metro Kisch, LuLu Belle's Gifts and more offering a wide variety of local goods to choose from this holiday season.
Additionally, a group of carolers from Springville First United Methodist Church will bring some holiday cheer to Main Street with singing throughout the afternoon.
Carolers will meet at Love, INC and make their way through the streets to the community Christmas tree lighting. They will end their singing back at Love, INC and warm up with some hot cocoa. All ages and musical abilities are welcome.
At the Springville Center for the Arts, the Harold L. Olmsted Gallery will be home to a collection of "small works" this holiday season in an exhibit called Winter's Presence.
"Our fine craft and art pieces make very meaningful gifts. It takes 'shop local' to the next level by supporting local artists, and supporting Springville Center for the Arts," explains Board President Debra Ehrig.
The opening of the show will coincide with A Very Merry Main Street and continue through Dec. 22.
The show begins at 10 a.m. at the theater. Admission is one unwrapped toy per person to benefit the Kiwanis Toys for Tots program.
The event also features an Ugly Christmas Sweater Contest for kids and adults, ornament decorating for $1 each and a visit from Santa.
This great event for families is a nice opportunity to watch the holiday classics we usually only see on TV the way they should be seen: up on the big screen.
And that's just the beginning of the festive fun in Springville. Check our calendar of events to see other upcoming holiday happenings as well.


Methods and apparati for securely loading one or more computer software applications onto a tamper resistant module (TRM) (107) and for securely deleting one or more applications from the TRM. An embodiment of the invention comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept loading of an application. Thereafter, the method provides for loading the application onto the TRM (107) only after the first step determines that the TRM (107) is qualified to accept the loading of the application. Another embodiment comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept deleting of an application. Thereafter, the method provides for deleting the application from the TRM (107) only when the first step determines that the TRM (107) is qualified to accept the deleting of the application.
This patent application is a continuation of and claims priority to U.S. patent application Ser. No. 11/655,497, filed on Jan. 19, 2007; patent application Ser. No. 11/655,497 is a continuation of and claims priority to U.S. patent application Ser. No. 09/932,013, filed on Aug. 17, 2001; patent application Ser. No. 09/932,013 is a continuation of and claims priority to U.S. patent application Ser. No. 09/076,551, filed on May 12, 1998, now U.S. Pat. No. 6,317,832, entitled "Secure Multiple Application Card System and Process"; patent application Ser. No. 09/076,551 claims the priority benefit of U.S. provisional patent application No. 60/046,514 filed on May 15, 1997, entitled "Design for a Multi Application Smart Card", and further claims the priority benefit of U.S. provisional patent application No. 60/046,543 filed on May 15, 1997, and patent application Ser. No. 09/076,551 is a continuation of and claims priority to U.S. patent application Ser. No. 09/023,057, filed on Feb. 12, 1998, now U.S. Pat. No. 6,575,372, entitled "Secure Multi-Application IC Card System Having Selective Loading and Deleting Capability"; patent application Ser. No. 09/023,057 claims the priority benefit of U.S. provisional patent application No. 60/046,514, filed on May 15, 1997, entitled "Design for a Multi Application Smart Card", and further claims the priority benefit of Great Britain patent application no. 9703591.9, filed on Feb. 21, 1997, entitled "Multiple Application Computer System." All seven of these prior patent applications are hereby incorporated by reference into the present patent application in their entireties.
This invention pertains to the field of distribution of computer software applications, and, in particular, to use of a certification authority when loading software applications onto and deleting software applications from a tamper resistant module.
The invention relates to a computer system in which a population of computers has access to multiple software applications. The computers may be personal computers (PC's) or, for example, integrated circuit cards ("IC cards") also known as "smart cards". The applications may be programs available from a variety of sources including computer tape or disc and, in particular, remote computers with which a serial link, typically by telephone, is established.
In the PC environment, it is customary to distribute applications on floppy discs or CD ROMS and to retain them on a local hard disc for operation. In many ways, this is inconvenient, demanding high capacity local storage media and presenting difficulties with updates. In the field of smart cards, the problem of local application storage is much more acute, because storage capacity in the integrated circuit is relatively very limited. A solution in both cases is to make available applications held remotely and download them via a remote link. Internet and intranet systems are ideal vehicles for this, and it is possible to run PC's from Internet application modules (or "applets" as they are called) for immediate running and then to discard them. The applets require no local long-term storage capacity. An example of such a system is JAVA.
Several difficulties are associated with downloaded applications. One is hardware compatibility. Different computers have different microprocessors and different operating systems. It has been customary to re-write applications to cater for different computers, but this is cost-effective only for large, widely used, and static applications. It is not practicable for applets. A second problem is control of the applets. Without control, it would be possible for applets to make direct hardware calls to take control of local storage or communication devices. This could be mischievous at best and severely damaging or criminal at worst.
JAVA meets these two difficulties by ensuring that the applets are written in a common high-level interpreted language and that a local interpreter processes the applet instructions. Thus, all applets are written in the same language, and the interpreter constitutes both a hardware and a control buffer. Similarly, and for the same reasons, proposals have been made for on-board interpreters in smart cards to run downloaded high-level language applications.
The arrangement, according to the invention, allows the provision of computer specific applications or application specific computers. In some embodiments, both the tamper-resistant module and the application have both class identifiers and bit-maps so that mutual control may be exercised. However, in a preferred embodiment of the invention, the tamper-resistant module has the bit-map and the application has class identifiers. The integrity of the system depends upon both the bit-map and the class identifiers being secure. The tamper-resistant module secures the bit-map whereas the class identifiers are preferably secured by an encryption system in which a class identifier section of the application is digitally certified by a system manager.
In a preferred embodiment of the invention, class identifiers are provided both for the tamper-resistant module (TRM) and the application. The computers may be PC's, in which case the tamper-resistant modules may be smart cards read by readers attached to the computers or, for example, dongles, PC cards, or PCMCIA cards coupled to the computers.
In a preferred embodiment of the invention, the computers are embodied in integrated circuits which are themselves the tamper-resistant modules. Typically, the integrated circuits are mounted in IC cards, which are becoming increasingly used for many different purposes in the world today. An IC card typically is the size of a conventional credit card which contains a computer chip including a microprocessor, read-only-memory (ROM), electrically erasable programmable read-only-memory (EEPROM), an Input/Output (I/O) mechanism, and other circuitry to support the microprocessor in its operations. An IC card may contain a single application or may contain multiple independent applications in its memory. MULTOS TM is a multiple application operating system which runs on IC cards, among other platforms, and allows multiple applications to be executed on the card itself. This allows a card user to run many programs stored in the card (for example, credit/debit, electronic money/purse and/or loyalty applications) irrespective of the type of terminal (i.e., ATM, telephone, and/or POS) in which the card is inserted for use.
A conventional single application IC card, such as a telephone card or an electronic cash card, is loaded with a single application at its personalization stage when it is manufactured and before it is given to a card user. That application, however, cannot be modified or changed after the card is issued, even if the modification is desired by the card user or card issuer. Moreover, if a card user wanted a variety of application functions to be performed by IC cards issued to him or her, such as both an electronic purse and a credit/debit function, the card user would be required to carry multiple physical cards on his or her person, which would be quite cumbersome and inconvenient. If an application developer or card user desired two different applications to interact or exchange data with each other, such as a purse application interacting with a frequent flyer loyalty application, the card user would be forced to swap multiple cards in and out of the card-receiving terminal, making the transaction difficult, lengthy, and inconvenient.
Therefore, it is beneficial to store multiple applications on the same IC card. For example, a card user may have both a purse application and a credit/debit application on the same card, so that the user could select which type of payment (by electronic cash or credit card) to use to make a purchase. Multiple applications could be provided to an IC card if sufficient memory exists and an operating system capable of supporting multiple applications is present on the card. Although multiple applications could be preselected and placed in the memory of the card during its production stage, it would also be beneficial to have the ability to load and delete applications for the card post-production as needed.
The increased flexibility and power of storing multiple applications on a single card create new challenges to be overcome concerning the integrity and security of the information (including application code and associated data) exchanged between the individual card and the application provider as well as within the entire system when loading and deleting applications. It would be beneficial to have the capability in the IC card system to exchange data among cards, card issuers, system operators, and application providers securely and to load and delete applications securely at any time from a local terminal or remotely over a telephone line, Internet or intranet connection, or other data conduit. Because these data transmission lines are not typically secure lines, a number of security and entity authentication techniques must be implemented to make sure that applications being sent over the transmission lines are not tampered with and are only loaded onto the intended cards.
As mentioned, it is important—particularly where there is a continuing wide availability of new applications to the cardholder—that the system has the capability of adding applications onto the IC card subsequent to issuance. This is necessary to protect the longevity of the IC cards; otherwise, once an application becomes outdated, the card would be useless. In this regard, to protect against the improper or undesired loading of applications onto IC cards, it would be beneficial for the IC card system to have the capability of controlling the loading process, and restricting, when necessary or desirable, the use of certain applications to a limited group or number of cards such that the applications are "selectively available" to the IC cards in the system. This "selective capability" would allow the loading and deleting of applications at, for example, a desired point in time in the card's life cycle. It would also allow the loading of an application only to those cards chosen to receive the selected application.
Accordingly, it is an object of this invention to provide these important features, and specifically a secure system that allows for selective availability of applications which may be loaded onto IC cards or other tamper resistant modules.
Methods and apparati for securely loading one or more computer software applications onto a tamper resistant module (TRM) (107) and for securely deleting one or more applications from the TRM (107). An embodiment of the invention comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept loading of an application. Thereafter, the method provides for loading the application onto the TRM (107) only if the first step determines that the TRM (107) is qualified to accept the loading of the application. Another embodiment comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept deleting of an application. Thereafter, the method provides for deleting the application from the TRM (107) only when the first step determines that the TRM (107) is qualified to accept the deleting of the application.
FIG. 10 is a system diagram of entities involved with the use of the IC card once it has been personalized.
The present invention provides an IC card system and process which allow the flexibility to load and delete selected applications over the lifetime of a multi-application IC card or other tamper resistant module in response to the needs or desires of the card user, card issuers, and/or application developers. A card user who has such a card can selectively load and delete applications as desired if allowed by the card issuer in conjunction with the system operator or Certification Authority ("CA") which controls the loading and deleting process by certifying the transfer of information relating to the process. Unlike the JAVA scenario, the application remains loaded until it is deliberately deleted. There are restrictions on who may delete applications, and deletion requests must be made to an authorized body such as the IC card issuer or perhaps the application issuer.
By allowing applications to be selectively loaded and deleted from the card, a card issuer can extend additional functionality to an individual IC card without having to issue new cards. Moreover, application developers can replace old applications with new enhanced versions, and applications residing on the same card using a common multiple application operating system may interact and exchange data in a safe and secure manner. For example, a frequent flyer loyalty program may automatically credit one frequent flyer mile to a card user's internal account for every dollar spent with a Mondex purse or with a credit/debit application. By allowing the ability to selectively load and delete applications, the card user, subject to the requirements of the card issuer, also has the option of changing loyalty programs as desired.
A card issuer or application developer may intend that a particular application be loaded on only one card for a particular card user in a card system. A regional bank may desire to have a proprietary application reside only on the cards which the bank issues. The present invention allows for this selective loading, and specifically allows for the prevention of loading proprietary applications onto unauthorized cards issued by others.
To achieve these desired objectives, the present invention gives each card a specific identity by storing "card personalization data" on the card. Moreover, each application to be loaded or deleted on one or more cards in the system is assigned "application permissions data" which specify the cards upon which the applications may be loaded.
The type of personalized data can vary depending upon the needs and requirements of the card system. In the preferred embodiment, described in greater detail below, the personalization data include unique card identification designation data, the card issuer, the product class or type (which is defined by the card issuer), and the date of personalization. However, not all of these data elements are required to be used, and additional elements could also be included.
The application permissions data associated with an application, also described in greater detail below, can be a single value in an identity field, or could include multiple values in the identity field. For example, the application permissions data in the card issuer field could represent both product class A and product class B from a certain Bank X, indicating that the application could be loaded onto cards designated as product classes A and B issued by Bank X (as indicated in the card product ID field of the card's personalization data).
In addition, a "global value" could be stored in the issuer field (or other field) of the application permissions data, indicating that all IC cards in the system regardless of who issued the card match this permissions field. In this case, for example, a data value of zero stored in the application permissions card-issuer field will match all of the cards' personalization card-issuer fields.
FIG. 1 shows the three steps involved in providing an operational multi-application IC card in a secure system. The first step is the card manufacturing step 101. The second step is the personalization step 103, where card personalization data (also called entity authentication data) is loaded onto the card. The third step is the application loading step 105, which checks to see whether a card is qualified to receive an application, i.e., when the personalization data is checked against the application permissions data associated with the application to be loaded. Each of these three steps is described in detail below.
FIG. 2 shows the steps necessary in manufacturing 101 an IC card in a secure system. Step 201 manufactures the physical IC card by creating the integrated circuit on silicon and placing it on the card. The integrated circuit chip includes RAM, ROM, and EEPROM memories. When the card is first manufactured, a global public key of the system operator (in this case called the Certification Authority (CA)) is stored on each card in ROM in step 203. This allows the card to authenticate that the source of any message to it is from the CA, since the public key on the card is matched to the CA's secret key.
More specifically, this public key stored on the card allows the individual card to verify data signed with the CA's private key. The public key of the CA, which is stored on the card, is used only for determining whether the data sent to the card was signed with the proper CA private key. This allows the card to verify the source of any message coming from the CA.
Step 205 inserts a card enablement key in a secure portion of EEPROM in the card to facilitate card-specific confidentiality during enablement, and step 207 inserts a card identifier in EEPROM of the card. The identifier, which can be accessed by any terminal, allows the system to determine the identity of the card in later processes. The identifier is freely available and is not used to authenticate messages.
Step 209 stores the operating system code in ROM on the card, including any primitives which are called or supported by the operating system. The primitives are written in native language code (e.g., assembly language) and are stored in ROM. The primitives are subroutines which may be called by the operating system or by applications residing on the card, such as mathematical functions (multiply or divide), data retrieval, data manipulation, or cryptographic algorithms. The primitives can be executed very quickly, because they are written in the native language of the processor.
After the IC cards are manufactured, they are sent to a personalization bureau ("PB") to enable and personalize 103 the card by storing card personalization data in the memory of the card. The terms "enablement" and "personalization" are used interchangeably herein to indicate the preparatory steps taken to allow the card to be loaded securely with an application. The individual cards are preferably manufactured in batches and are sent to a personalization bureau in a group for processing.
FIG. 3 shows the steps of the card enablement process when the card arrives at a PB. The PB may be the card issuer (e.g., a bank or other financial institution), or may be a third party that performs the service for the card issuer. The PB configures the card to a specific user or user class.
FIG. 3 specifically shows the steps taken to enable and personalize 103 each IC card which work within the system. The cards can be placed in a terminal which communicates with IC cards and which reads the card identifier data (previously placed on the card during the manufacturing process--see step 207). This card identification data is read from the card in step 301. The terminal effectively sends a "get identification data" command to the card and the card returns the identification data to the terminal.
Step 303 first checks to see whether an enablement bit stored in EEPROM of the card has been already set. If it already has been set, the card has already been configured and personalized, and the enablement process abnormally ends ("ABEND"), as shown in step 304. A card cannot be enabled and personalized twice. If the bit has not been set, the process continues with step 305.
In step 305, the individualized card key set for the card being enabled (which key set is generated at the CA) is stored on the card. The keys can be used later in off-card verification (i.e., to verify that the card is an authentic card). This verification is necessary to further authenticate the card as the one for which the application was intended.
Other data can also be stored on the card at this time as needed by the system design, such as an address table or further subroutines.
Step 311 sets the enablement bit in EEPROM of the card, which indicates that the enablement process has been completed for the particular card. When this bit is set, another enablement process cannot occur on the card. This ensures that only one personalization and enablement process will occur to the card, thus preventing illegal tampering of the card or altering the card by mistake. In the preferred embodiment, the enablement bit is initially not set when the card is manufactured, and is set at the end of the enablement process.
FIG. 4 shows an example of a block diagram of an IC card chip which has been manufactured and personalized. The IC card chip is located on an IC card for use. The IC card preferably includes a central processing unit (CPU) 401, a RAM 403, an EEPROM 405, a ROM 407, a timer 409, control logic 411, I/O ports 413, and security circuitry 415, which are coupled together by a conventional data bus.
Control logic 411 in memory cards provides sufficient sequencing and switching to handle read-write access to the card's memory through the input/output ports 413. CPU 401 with its control logic can perform calculations, access memory locations, modify memory contents, and manage input/output ports. Some cards have a coprocessor for handling complex computations like cryptographic algorithms. Input-output ports 413 are used under the control of a CPU 401 and control logic 411 alone, for communications between the card and a card acceptance device. Timer 409 (which generates or provides a clock pulse) drives the control logic 411 and CPU 401 through the sequence of steps that accomplish memory access, memory reading or writing, processing, and data communication. A timer 409 may be used to provide application features such as call duration. Security circuitry 415 includes fusible links that connect the input/output lines to internal circuitry as required for testing during manufacture, but which are destroyed ("blown") upon completion of testing to prevent later access. The personalization data to qualify the card is stored in a secured location of EEPROM 405. The comparing of the personalization data to applications permissions data is performed by the CPU 401.
FIG. 5A shows the steps of generating and loading the four elements of the card personalization data into the memory of the IC cards, and FIG. 5B shows a schematic of bit maps for each identity field residing in the memory of an IC card containing personalization data, in accordance with the present invention. Each data structure for each identity field has its own descriptor code. Step 501 loads the data structure for the identity field "card ID" called "msm_mcd_permissions_mcd_no." This nomenclature stands for MULTOS system manager—MULTOS card device_permissions_MULTOS card device number. Although this number is typically 8 bytes long as shown in FIG. 5B, the data could be any length that indicates a unique number for the card. In the preferred embodiment, 2 bytes are dedicated as a signal indicator, 2 bytes comprise a MULTOS Injection Security Module ID (MISM ID) indicating which security module injected the card with its injected keys when it was manufactured, and 4 bytes comprise an Integrated Circuit Card (ICC) serial number which identifies the individual card produced at the particular MISM.
Step 503 loads the data structure for the identity field "issuer ID" called "msm_mcd_permissions_mcd_issuer_id." This nomenclature stands for a MULTOS card device issuer identification number. Each card issuer (such as a particular bank, financial institution or other company involved with an application) will be assigned a unique number in the card system. Each IC card in the MULTOS system contains information regarding the card issuer which personalized the card or is responsible for the card. A card issuer orders a certain number of cards from a manufacturer, and performs or has performed the personalization process as described herein. For example, a regional bank may order 5,000 cards to be distributed to its customers. The "mcd_issuer_id" data structure on these cards will indicate which issuer issued the cards. In the preferred embodiment, the data structure is 4 bytes long (as shown in FIG. 5A at 503A) to allow for many different issuers in the system, although the length of the data structure can vary with the needs of the card system.
Step 505 loads the data structure for the identity field "product ID" called "msm_mcd_permissions_mcd issuer_product_id." This nomenclature stands for MULTOS card device issuer product identification number. Each card issuer may have different classes of products or cards which it may want to differentiate. For example, a bank could issue a regular credit card with one product ID, a gold credit card with another product ID, and a platinum card with still another product ID. The card issuer may wish to load certain applications onto only one class of credit cards. A gold credit card user who pays an annual fee may be entitled to a greater variety of applications than a regular credit card user who pays no annual fee. The product ID field identifies the card as a particular class, and will later allow the card issuer to check the product ID and load only those applications onto cards which match the desired class.
Another way to differentiate products is by application type, such as by categorizing the application as financial, legal, medical, and/or recreational, or by assigning particular applications to a group of cards. For example, one card issuer may have different loyalty programs available with different companies to different sets of card users. For example, a bank may have an American Airlines™ loyalty program and a British Airways™ loyalty program for different regions of the country, dependent on where the airlines fly. The product type allows the issuer to fix the product classification of the card during the personalization process. When loading applications onto the card, the product type identification number on each card will be checked to make sure it matches the type of card onto which the issuer desires to load. The product type data structure is preferably an indexing mechanism (unlike the other personalization data structure) of 8 bits (as shown at 505A in FIG. 5A), but could be any length, depending upon the needs of the card system. In the illustrated embodiment, the resulting instruction locates the second bit (since the byte's indicated value is 2) in the array to be searched (see discussion of step 809 below).
Step 507 loads the data structure for the identity field data called "msm_mcd_permissions_mcd_controls_data_date." This nomenclature stands for the MULTOS card device controls data date or, in other words, the date on which the card was personalized, so that, for example, the application loader can load cards dated only after a certain date, load cards before a certain date (e.g., for application updates), or load cards with a particular data date. The information can include the year, month, and day of personalization, or may include less information, if desired. The data_date data structure is preferably one byte in length (see 507A in FIG. 5B), although it could be any length depending upon the needs of the particular card system used.
Once all of the personalization data structures are loaded and stored in the card, the card has been identified by issuer, product class, date, and identification number (and other data fields, if desired), and the card cannot change its identity; these fields cannot be changed in the memory of the card. If a card user wants to change the product_id stored in the card to gain access to different applications available to another product type, a new card will have to be issued to the user containing the correct personalization data. This system is consistent with a gold card member receiving a new card when the classification is changed to platinum.
After the card has been enabled and personalized by storing its individual card key set, MSM personalization characteristics, and enablement bit as described in FIG. 3, the card is ready to have applications loaded into its memory.
The application loading process 105 contains a number of security and card configuration checks to ensure the secure and proper loading of an application onto the intended IC card. The application loading process is preferably performed at the personalization bureau, so that the card contains one or more applications when the card is issued. The card may contain certain common applications which will be present on every card the issuer sends out, such as an electronic purse application or a credit/debit application. Alternatively, the personalization bureau could send the enabled cards to a third party for the process of loading applications. The multiple application operating system stored in the ROM of each card, and the card MSM personalization data, are designed to allow future loading and deleting of applications after the card has been issued, depending upon the desires of the particular card user and the responsible card issuer. Thus, an older version of an application stored on the IC card could be replaced with a new version of the application. An additional loyalty application could also be added to the card after it has been initially sent to the card user, because the application is newly available, or the user desires to use the new application. These loading and deleting functions for applications can be performed directly by a terminal or may be performed over telephone lines, data lines, a network such as the Internet, or any other way of transmitting data between two entities. In the present IC card system, the process of transmitting the application program and data ensures that only IC cards containing the proper personalization data and which fit an application permissions profile will be qualified and receive the corresponding application program and data.
FIG. 6 shows the preferred steps performed in loading an application onto an IC card in the MULTOS IC card system. For this example, the PB is loading an application from a terminal which enabled the same card. Step 601 performs an "open command" initiated by the terminal which previews the card to make sure the card is qualified to accept the loading of a specific application. The open command provides the card with the application's permissions data and the application's size, and instructs the card to determine (1) whether the enablement bit is set, indicating the card has been personalized; (2) whether the application code and associated data will fit in the existing memory space on the card; and (3) whether the personalization data assigned to the application to be loaded allows for the loading of the application onto the particular card at issue. The open command could also make additional checks as required by the card system. These checking steps during the open command execution will be described in detail in conjunction with FIG. 7.
After the open command has been executed, the application loader via the terminal is advised whether the card contains the proper identification personalization data and whether enough room exists in the memory of the card for the application code and related data. If there is insufficient memory, a negative response is returned by the card and the process is abended (abnormally ended). If the identification personalization data does not match the applications permissions data, a warning response is given in step 603, but the process continues to the load and create steps. Alternatively, if there is no match, the process may automatically be abended. If a positive response is returned by the card to the terminal in step 605, the application loader preferably proceeds to next steps. The "open" command allows the application to preview the card before starting any transfer of the code and data.
Step 607 then loads the application code and data onto the IC card into EEPROM. The actual loading occurs in conjunction with create step 609, which completes the loading process and enables the application to execute on the IC card after it is loaded. The combination of the "open", "load", and "create" commands are sent by the terminal, or another application provider source, to the IC card to perform the application loading process. The operating system in the IC cards is programmed to perform a specific set of instructions with respect to each of these commands, so that the IC card will communicate with and properly carry out the instructions from the terminal.
Step 609 performs the create command, which, at least: (1) checks whether an application load certificate is signed (encrypted) by the CA and therefore authenticates the application as a proper application for the system; and, (2) checks the card personalization data stored on the card against the permissions profile for the application to be loaded to qualify the card for loading. It may do other checks as required. If one of the checks fails, a failure response 610 is given and the process aborts. After it has passed these checks, the application is loaded into the memory of the card.
FIG. 7 shows the various steps of the open step 601 of FIG. 6 in more detail. Step 701 determines whether the enablement (i.e., control) bit is set. This bit is set when the card has completed its personalization process and has been assigned its personalization data. An application can be loaded on an IC card in the card system only if the card contains the personalization data. If the enablement bit is not set, the card has not been personalized, and therefore the card returns a negative response 703 to the terminal. If the enablement bit is set, the card has been enabled, and the test conditions continue with step 711.
Step 711 checks whether there is sufficient space in the memory on the card to store the application code and its associated data. Applications typically have associated data related to their functions. This data is used and manipulated when the application is run. Storage space in the memory of an IC card is a continuing concern, due to the relatively large physical space required for EEPROM and how it fits in the integrated circuit, which is desired to be small enough to fit on a credit card sized card. An example of the size of a preset EEPROM on an IC card is 16K bytes, although the actual size varies. Applications can range from 1K byte or less for a very simple application up to the size of available memory for a more sophisticated application. The data associated with an application can range from no data being stored in the card memory to a size constrained by the amount of available memory. These varied sizes of application code and data continually increase as applications become more advanced and diverse.
MULTOS as an operating system is not limited by the number of applications and associated data it can store on the card. Thus, if five applications can fit in the available memory of the card, the card user will have greatly increased functionality compared with the case where one or two applications are stored on the card. Once a card's memory is filled to its capacity, however, a new application cannot be loaded onto the card unless another application, including its code and data of sufficient size, can be deleted. Therefore, checking the amount of available space on the card is an important step. If there is not sufficient space, an insufficient space response 713 is returned to the terminal. The application loader can then decide whether another existing application on the card should be deleted to make room for the new application. Deletion depends upon the card issuer having an application delete certificate from the CA. If there is sufficient space on the card, the process continues with step 715.
An example of the testing of memory spaces in step 711 is now described. The numbers used in this example in no way limit the scope of the invention, but are used only to illustrate memory space requirements. An IC card may have 16K available EEPROM when it is first manufactured. The operating system data necessary for the operating system may take up 2K of memory space. Thus, 14K remain. An electronic purse application's code is stored in EEPROM, and may take up 8K of memory space. The purse application's required data may take up an additional 4K of memory space in EEPROM. The memory space which is free for other applications is thus 2K (16K−2K−8K−4K=2K ). If a card issuer wants to load a credit/debit application whose code is 6K bytes in size onto the card in this example, the application does not fit in the memory of the IC card. Therefore, the application cannot load the new application without first removing the purse application from the card. If a new credit/debit application is loaded into EEPROM of the IC card, it would have to overwrite other application's code or data. The application loader is prevented from doing this.
FIG. 8 shows the steps performed in determining whether the card's personalization data falls within the permissible set of cards onto which the application at issue may be loaded. These steps are preferably performed during the execution of the "create" command. However, these steps may be performed at any time during the loading or deleting of an application. As described previously, the card is personalized by storing data specific to the card (MSM personalization data), including: a card ID designation specific to an individual card, the card issuer number indicating the issuer of the card, the product type of the card, such as a gold or platinum card, and the date the card was personalized. This data uniquely identifies the card apart from all other IC cards in the system.
Accordingly, applications can be selectively stored on individual cards in the IC card system on virtually any basis, including the following. An application can be loaded selectively to cards containing one or more specific card numbers. An application can be selectively loaded on one or more cards containing a specified card issuer ID. Moreover, an application can be loaded only upon one type of product specified by the particular card issuer, and/or the application can be loaded only on cards which have a specified date or series of dates of personalization. Each of the personalization data allows an application to be selectively loaded onto certain cards or groups of cards, and also ensures that cards without the proper permissions do not receive the application. Personalization data types in addition to the four described can also be used as needed.
The selection of IC cards upon which a particular application may be loaded is made possible by the use of "applications permissions data" which is assigned to the application, representing at least one set of cards upon which the application may be loaded. The set may be based on virtually any factor, including one or more of the following: card numbers, card issuers, product types, or personalization dates. Although the individual card's personalization data typically identify one specific number, one card issuer, one product type, and one date, the application's permissions data may indicate a card number or a blanket permission, a card issuer or a blanket permission, and a number of product types and dates.
For example, a frequent loyalty program may be configured to allow its loading and use on cards in different product classes belonging to one card issuer. In addition, the application permissions data may indicate that the loyalty program can be used on gold and platinum product types if the card was issued after May, 1998. Thus, the MSM permissions check determines whether the card's individual personalization data is included in the allowed or permissible set of cards upon which the application may be loaded. If it is, the application is loaded.
To expedite the comparison process, an alternative embodiment may include setting one or more permissions data at zero representing a blanket permission for that particular data. For instance, by placing a zero for the "card number" entry in the application permissions data or some other value indicating that all cards may be loaded regardless of their number, the system knows not to deny any cards based on their card number. Moreover, if a zero is placed in the application's permissions data "issuer ID," all cards similarly pass the "issuer" test comparison. This feature allows greater flexibility in selecting groups of cards. The zero indicator could also be used for other permissions data, as required.
Referring to FIG. 8, each of the permissions data is checked in the order shown, but other orders could be followed, because if any one of the permissions fails, the application is prevented from being loaded on the IC card being checked. The permissions are preferably checked in the order shown. Step 801 checks whether the application permissions product type set encompasses the card's product type number stored in the memory of the card. Each card product type is assigned a number by the system operator. The product types are specified for each card issuer, because different card issuers have different product types. The cards are selectively checked to ensure that applications are loaded only on cards of authorized product type. The application permissions product type set can be 32 bytes long, which includes multiple acceptable product types, or can be a different length, depending upon the needs of the system. Using data structure 505A as an example, the operating system checks bit number 2 in the 256 bit array (32 bytes×8 bits per byte) resulting from the 32 byte long application permissions data structure. If the permissions check fails, the card returns a failure message to the terminal in step 803. If the product type check passes (for example, the value of bit no. 2 being 1), the process continues with step 805.
Step 805 checks whether the application permissions allowable card issuer number set encompasses the card's issuer number stored in the memory of the card, or whether the application permissions issuer data is zero (indicating all cards pass this individual permissions check). Each card issuer is assigned a number by the system operator, and the cards are selectively checked to ensure that applications are loaded only on cards distributed by authorized card issuers. The application permissions card issuer number set can be 4 bytes long if one issuer is designated, or can be longer, depending upon the needs of the system. If the issuer check fails, the card returns a failure message to the terminal in step 807. If the check passes, the process continues with step 809.
Step 809 checks whether the application permissions date set encompasses the card's data date stored in the memory of the card. The date that the IC card was personalized is stored and preferably includes at least the month and year. The cards are selectively checked to ensure that applications are loaded only on cards with the authorized personalization date. The application permissions date set can be 32 bytes long, which includes multiple dates, or can be a different length, depending upon the needs of the system. If the date permissions check fails, the card returns a failure message to the terminal in step 811. If the date check passes, the process continues with step 813.
Step 813 checks whether the application permissions allowable card number set encompasses the card's ID number stored in the card memory, or whether the application permissions allowable card number data is zero (indicating all cards pass this individual permissions check). The testing of the permissions is performed on the card during the execution of the open, load, and create commands. The application permissions card number data set can be 8 bytes long if one number is designated, or can be longer, depending upon the needs of the system. If the card number check fails, the card returns a failure message to the terminal in step 815. If the check passes, the process continues with step 817.
FIG. 9 shows the components of the system architecture for the card initialization process of an IC card in a secure multiple application IC card system. The system includes a card manufacturer 102, a personalization bureau 104, an application loader 106, the IC card 107 being initialized, the card user 109, and the certification authority 111 for the entire multiple application secure system. The card user 109 is the person or entity who uses the stored applications on the IC card. For example, a card user may prefer an IC card that contains both an electronic purse containing electronic cash (such as MONDEX™) and a credit/debit application (such as the MasterCard™ EMV application) on the same IC card. The following is a description of one way in which the card user 109 obtains an IC card 107 containing the desired applications in a secure manner.
The card user 109 contacts a card issuer 113, such as a bank which distributes IC cards, and requests an IC card with the two applications both residing in memory of a single IC card. The integrated circuit chip for the IC card 107 is manufactured by manufacturer 102 and sent to the card issuer 113 (or an entity acting on its behalf) in the form of an IC chip on a card. As discussed above (see steps 201-209), during the manufacturing process, data is transmitted 115 via a data conduit from the manufacturer 102 to card 107 and stored in IC card 107's memory. (Any of the data conduits described in this Figure could be a telephone line, Internet connection, or any other transmission medium.) The certification authority 111, which maintains encryption/decryption keys for the entire system, transmits 117 security data (i.e., a global public key) to the manufacturer over a data conduit which is placed on the card by the manufacturer along with other data, such as the card enablement key and card identifier. The card's multiple application operating system is also stored in ROM and placed on the card by the manufacturer. After the cards have been initially processed, they are sent to the card issuer for personalization and application loading.
The card issuer 113 performs, or has performed by another entity, two separate functions. First, the PB 104 personalizes the IC card 107 in the ways described above, and second, the application loader 106 loads the application, provided the card is qualified, as described.
Regarding personalization, an individualized card key set is generated by the CA 111 and stored on the card (see FIG. 3). The card is further given a specific identity using MSM personalization (see FIG. 3, step 307 and FIG. 5) including a card ID number, an issuer ID number identifying the card issuer which processed the card, a card product type number which is specified by the card issuer, and the date upon which the personalization took place. After the card has been personalized, applications need to be loaded onto the card so that the card can perform desired functions.
The application loader 106, which could use the same terminal or data conduit as personalization bureau 104, first needs to have determined whether the card is qualified to accept the application. This comparison process takes place on the card itself (as instructed by its operating system) using the permissions information. The card, if it is qualified, thus selectively loads the application onto itself based upon the card's identity and the card issuer's instructions. The application loader communicates 119 with the IC card via a terminal or by some other data conduit. After the applications have been loaded on the card, the card is delivered to the card user 109 for use.
The secure multiple application IC card system described herein allows for selective loading and deleting of applications at any point in the life cycle of the IC card after the card has been personalized. Thus, a card user could also receive a personalized card with no applications and then select a desired application over a common transmission line such as a telephone line or Internet connection.
FIG. 10 is a system diagram of entities involved with the use of an IC card once it has been personalized. The system includes an IC card 107, a terminal 153, an application load/deleted entity 155, the CA 157, a card issuer 171, and other IC cards 159 in the system. The arrows indicate communication between the respective entities. The CA 157 facilitates loading and deleting of applications. After providing the MSM permissions data and card specific keyset to the card during card enablements, the CA 157 allows applications to be later loaded and deleted, preferably by issuing an application certificate. Application specific keys are required to authenticate communication between a card and terminal. The IC card 107 also can communicate with other IC cards 159. Card issuer 171 is involved with all decisions of loading and deleting applications for a card which it issued. All communications are authenticated and transmitted securely in the system.
For instance, IC card 107 uses the following procedure to load a new application onto the card. IC card 107 is coupled to terminal 153, and the terminal requests that an application be loaded. Terminal 153 contacts application load/delete entity 155 which, as a result and in conjunction with card issuer 171, sends the application code, data, and application permissions data (along with any other necessary data) to terminal 153. Terminal 153 then queries IC card 107 to ensure it is the correct card onto which the application may be loaded. If IC card 107 passes the checks discussed above, the application is loaded onto IC card 107. The CA 157 provides the application load or delete certificate that enables the application to be loaded or deleted from the card. This example shows one way to load the application, but other variations using the same principles could be performed, such as directly loading the application at the application load/delete entity 155.
For example, it will be appreciated that references to "software" include firmware and the like, and that MSM personalization and permissions data may not only be used for loading applications onto IC cards, but also for deleting applications from said cards. The same checks involving MSM permissions and loading applications are made for deleting applications. A delete certificate from the CA authorizing the deletion of an application controls the cards from which the application may be deleted. This is accomplished through the personalization data stored on each IC card and the permissions check as described herein.
In addition, the application's permissions data may actually include data representative of a set or sets of cards to be excluded, instead of included—cards that cannot be loaded with the application.
Furthermore, although the foregoing description of the preferred embodiments revolves around a discussion of IC cards 107 (or "smart cards"), the presently claimed methods and apparati are applicable to all tamper resistant modules generally, and not just to such cards. Thus, the term "tamper resistant module" can be used in lieu of the term "IC card" or "smart card" throughout this written description. The term "tamper resistant module" includes, but is not limited to, one or more IC cards, smart cards, dongles, PC cards, and/or PCMCIA cards. The IC cards, smart cards, dongles, PC cards, and/or PCMCIA cards may be coupled to one or more computers.
Furthermore, the term "personal computer/tamper resistant module combination" can be substituted for "IC card" or "smart card" throughout this written description.
loading the application onto the TRM only after the determining step determines that the TRM is qualified to accept the loading of the application.
deleting the application from the TRM only after the determining step determines that the TRM is qualified to accept the deleting of the application.
loading means responsive to said determining and authenticating means for securely loading said application onto said at least one TRM.
4. The apparatus of claim 3 wherein said at least one TRM further comprises memory means for storing an operating system for instructing said determining means, said authenticating means, and said loading means.
5. The apparatus of claim 3, further comprising personalization means for activating at least one of said TRM's at said personalization bureau.
6. The apparatus of claim 5 wherein said personalization means comprises means for compiling a list of said TRM identifiers and means for forwarding said list to said authority.
7. The apparatus of claim 3 wherein said personalization data block comprises TRM personalization data and an individual key set.
8. The apparatus of claim 3 wherein said at least one TRM further comprises a TRM enablement key for facilitating TRM specific confidentiality.
said TRM enablement key is set upon loading said encrypted data block.
means responsive to said determining and checking means for loading said specific application onto at least one TRM.
loading said application in the event said TRM is qualified and said application is authenticated.
deleting said application in the event said TRM is qualified.
said apparatus further comprising means for determining whether said TRM personalization data falls within said permissions data set.
at least one tamper resistant module (TRM), a software application to be loaded onto a TRM, and means for determining whether a TRM is qualified to accept the loading of said application onto said TRM, wherein each TRM comprises TRM personalization data, and said application is assigned application permissions data representing at least one TRM upon which said application is permitted to be loaded.
15. The apparatus of claim 14, wherein said determining means compares said TRM personalization data with said application permissions data.
16. The apparatus of claim 15, wherein whether said application is loaded onto said TRM depends on the result of said comparison, such that in the event the TRM personalization data matches said permissions data set, the TRM is qualified and the application is loaded.
17. The apparatus of claim 14, wherein said personalization data comprises data representative of a unique TRM identification designation.
18. The apparatus of claim 14, wherein said personalization data comprises data representative of a TRM issuer.
19. The apparatus of claim 14, wherein said personalization data comprises data representative of a product class.
20. The apparatus of claim 14, wherein said personalization data comprises data representative of a date.
said apparatus further comprising means for determining whether said personalization data falls within said permissions data set.
22. The apparatus of claim 21, wherein said application is loaded onto said TRM in the event said determining means determines that said personalization data falls within said set.
23. The apparatus of claim 21, wherein said personalization data comprises data representing a TRM identification designation and an issuer of said TRM.
24. The apparatus of claim 21, wherein said personalization data comprises data representing a product class and a date.
25. The apparatus of claim 21, wherein said permissions data set comprises a plurality of TRM identification designations.
26. The apparatus of claim 21, wherein said permissions data set comprises one or more issuers of said TRM.
27. The apparatus of claim 21, wherein said permissions data set comprises one or more product classes.
28. The apparatus of claim 21, wherein said permissions data set comprises a range of dates.
loading said application onto said TRM, provided said personalization data falls within said set of TRM's upon which said application is permitted to be loaded.
30. The method of claim 29, wherein said personalization data comprises data representative of a TRM identification designation.
31. The method of claim 29, wherein said personalization data comprises data representative of a TRM issuer.
32. The method of claim 29, wherein said personalization data comprises data representative of a product class.
33. The method of claim 29, wherein said personalization data comprises data representative of a date.
34. The method of claim 29, comprising the step of, prior to the determining step, enabling said TRM to be loaded with said application.
35. The method of claim 34, wherein said enabling step comprises setting an enablement bit indicating that the TRM has been enabled.
36. The method of claim 34, wherein said enabling step comprises storing personalization data onto said TRM.
37. The method of claim 36, wherein said enabling step comprises setting an enablement bit indicating that the TRM has been enabled.
38. The method of claim 34, wherein, prior to said enabling step, a checking step is performed to determine whether said TRM has been enabled.
deleting said application from said TRM provided said personalization data falls within said set of TRM's from which said application is permitted to be deleted.
40. The method of claim 39, wherein said personalization data comprises data representative of a TRM identification designation.
41. The method of claim 39, wherein said personalization data comprises data representative of a TRM issuer.
42. The method of claim 39, wherein said personalization data comprises data representative of a product class.
43. The method of claim 39, wherein said personalization data comprises data representative of a date.
means for determining whether a TRM is qualified to delete said application from said TRM, wherein each TRM comprises TRM personalization data, and said application is assigned application permissions data representing at least one TRM from which said application is permitted to be deleted.
45. The apparatus of claim 44, wherein said determining means makes a comparison between said TRM personalization data and said application permissions data.
46. The apparatus of claim 45, wherein whether said application is deleted from said TRM depends on the result of said comparison, such that in the event the TRM personalization data matches said application permissions data the TRM is qualified and the application is deleted.
loading means responsive to said determining and authenticating means for securely loading said application onto said at least one PC/TRM.
means responsive to said determining and checking means for loading said specific application onto at least one PC/TRM.
said apparatus further comprising means for determining whether said PC/TRM personalization data falls within said permissions data set.
a personal computer (PC) having at least one tamper resistant module (TRM), a software application to be loaded onto a PC and TRM combination (PC/TRM), and means for determining whether a PC/TRM is qualified to accept the loading of said application onto said PC/TRM, wherein each PC/TRM comprises PC/TRM personalization data, and said application is assigned application permissions data representing at least one PC/TRM upon which said application is permitted to be loaded.
means for determining whether a PC/TRM is qualified to delete said application from said PC/TRM, wherein each PC/TRM comprises PC/TRM personalization data, and said application is assigned application permissions data representing at least one PC/TRM from which said application is permitted to be deleted.
DE3682476D1 (en) 1985-10-07 1991-12-19 Toshiba Kawasaki Kk geraet portable electronic.
ES2041712T3 (en) 1987-03-04 1993-12-01 Siemens Nixdorf Informationssysteme Ag Data exchange system.
FR2653914A1 (en) 1989-10-27 1991-05-03 Trt Telecom Radio Electr System authentication of a card chip with a personal computer, and process for its implementation óoeuvre.
FR2667171B1 (en) 1990-09-25 1994-08-26 Gemplus Card Int portable media easily programmable microwave circuit and programming method of this microcircuit.
FR2687816B1 (en) 1992-02-24 1994-04-08 Gemplus Card International Method for customizing a smart card.
FR2720848B1 (en) 1994-06-03 1996-07-26 Gemplus Card Int A method of operating a transaction between a chip card and an information system.


text:
module.exports = function (req, res, next) {
    next();
};

redpajama_set_name: RedPajamaGithub


Snowy Cognac Weather Has Water Proof Upper.. Features Faux Suede Materials And A Sweater Knit Collar.New @titude(R) Snowy Weather Boots Boots Rain & Winter @titude(R) New Upper. Knit.
New @titude(R) Snowy weather boots.
Features faux suede materials and a sweater knit collar.
More from Snowy Cognac Weather Has Water Proof Upper.. Features Faux Suede Materials And A Sweater Knit Collar.New @titude(R) Snowy Weather Boots Boots Rain & Winter @titude(R) New Upper. Knit.


text:
You are here: World Cafe // World Cafe Guests // Buffy Sainte-Marie (Encore)
Buffy Sainte-Marie (Encore)
Buffy Sainte-Marie Continues To Not Act Her Age!
74 year old Buffy Sainte-Marie still has all the passion of her youth on her new album Power in the Blood. The Cree songwriter penned songs like " Universal Soldier" and "Until It's Time For You to Go" in the 60s that were hits for others. That was before she was blacklisted from American radio in the 1970s. She also won a Grammy and an Academy Award for her part in the songwriting on "Up Where We Belong" recorded by Joe Cocker and Jennifer Warnes for the climactic scene of the film An Officer and A Gentleman in 1982. She talks with us about her older songs, how she learned about being blacklisted and what drives her to keep writing and advocating for underserved people now.
IT'S MY WAY
NOT THE LOVIN KIND
Recent Release: Power In The Blood
Label: True North Records
Buffy SainteMarie
More in this category: « Joseph On World Cafe	Hear A New Bob Weir Song, 'Lay My Lily Down' »

redpajama_set_name: RedPajamaCommonCrawl


THE ONLY 24 HOUR GYM IN DAVENTRY.
We aspire to be the best and offer Daventry something it has never had! We offer 24-7 access for all members over 21 with no commitment to membership or joining fees.
We have worked hard to provide this facility to our local community and we always inspire others to take control of their lives and help them make the right choices to achieve their goals. Having no time to get to the gym can no longer be an excuse!
We want to give you choice to train when it suits you so you can reach your goals! With our fully equipped gym we are able to help you with anything; bodybuilding to weightlifting and all the fun stuff inbetween that is becomming popular. Whether you are training for general fitness, fat loss or more specific goals we make it our job to be able to offer you everything you need. We also have a variety of membership options for you to choose from to fit your budget and needs. We offer a free 30 minute induction to show you how to use the equipment to ensure your safety and maximise your results.
Come and have a look around, have a chat with us or just go for a workout and see what you think before signing.


Description: Max Pierson is a business categorized under women`s accessory and specialty stores, nec, which is part of the larger category women`s accessory and specialty stores. Max Pierson is located at the address 2991 County Road 10 in Waterloo, Indiana 46793-9587. The Owner is Max Pierson who can be contacted at (260)837-5732.
Location & access map for "Max Pierson"


text:
Harry i Walter jadą do Nowego Jorku - amerykańska komedia kryminalna z 1976 roku w reżyserii Marka Rydella.

Obsada
 James Caan - Harry Digby
 Elliott Gould - Walter Hill
 Michael Caine - Adam Worth
 Diane Keaton - Lissa Chestnut
 Charles Durning - Rufus T. Crisp
 Lesley Ann Warren - Gloria Fontaine
 Val Avery - Chatsworth
 Jack Gilford - Mischa
 Dennis Dugan - Lewis
 Carol Kane - Florence
 Kathryn Grody - Barbara
 David Proval - Ben
 Michael Conrad - Billy Gallagher
 Burt Young - Naczelnik Durgom

Linki zewnętrzne

Amerykańskie filmy komediowe
Amerykańskie filmy kryminalne
Filmy w reżyserii Marka Rydella
Amerykańskie filmy z 1976 roku
Filmy wytwórni Columbia Pictures

redpajama_set_name: RedPajamaWikipedia


Is there a moment in your life that you'd like to do over? A bad first date? A vacation gone wrong? Do you sometimes wish there was a rewind button that you could push?
When my husband and I began dating, we started cooking together for our dates. I invited him to my house where I cooked him Teriyaki Chicken. I chose this recipe because he had lived in Japan for a couple of years and this was a recipe my father got from a Japanese friend.
My date gobbled up every bite and asked for the recipe. My dad was in the room and overheard his request.
"Sorry, I can't give you the recipe. I had to pay for the recipe as it was a 'family recipe.' You'll either have to pay for it or marry her (pointing to me) for it."
Fast forward a year. We did get married and began our lives as full time students. I wanted to make Teriyaki chicken, but didn't want to wait the entire hour for the chicken to cook. I had a great idea: cook it in the microwave. Surely I could save some time, right?
I had no idea how long chicken would take in the microwave, so I guessed 20 minutes. That would be enough time, right? The rice takes 20 minutes and would be done at the same time as the chicken.
I spooned the cooked chicken over the rice. My husband took a few bites.
I spit out the first bite.
It tasted awful! It was burnt, leaving a horrible taste in my mouth.
My husband, too polite to say anything, kept eating, looking down at his plate.
"Doesn't this taste burnt?" I asked.
"I didn't want to hurt your feelings."
He turned his gaze from the burnt chicken and looked into my eyes.
Putting down his fork, he said five magic words: "Let's go out to eat."
I have made Teriyaki Chicken countless times over the years, but only in the oven.
Our 25th anniversary is coming up and I needed a do-over for this recipe ~ during the summer, I don't want to turn the oven on, nor wait an hour for chicken to cook.
What about cooking it on the grill?
I made the Teriyaki sauce, leaving out the cornstarch and using freshly grated ginger. I marinated the chicken in half the sauce, reserving the rest of the marinade for glazing the finished chicken.
Bamboo skewers were soaked in water for about 30 minutes and grilled on a hot grill for 15-20 minutes, turning the chicken every 5 minutes.
Grilling caramelizes the sauce, giving a whole 'nother dimension to this chicken! This chicken has a deep and robust flavor and doesn't need a lot of sauce. The fresh ginger brings makes a big difference in aroma and taste.
"We have a winner!" and gave me a kiss.
This post was sponsored by Frigidaire. When you share your own do-over moment at Facebook.com/Frigidaire, Frigidaire will donate $1 to Save the Children's U.S. programs. Plus, Frigidaire will help cover the costs for one lucky visitor to win the ultimate do-over.
I can't wait to make the chicken and I loved the story! Happy anniversary!
Your hubby sounds like a great guy. This recipe looks simple and yummy. On my to try list. Thanks Frieda!


AFCEA established in 1946, is a non-profit membership association serving the military, government, industry, and academia as an ethical forum for advancing professional knowledge and relationships in the fields of communications, information technology, intelligence, and security.
HIMSS is a cause-based, global enterprise producing health IT thought leadership, education, events, market research and media services around the world. Founded in 1961, HIMSS encompasses more than 52,000 individuals, of which more than two-thirds work in healthcare provider, governmental and not-for-profit organizations across the globe, plus over 600 corporations and 250 not-for-profit partner organizations, that share this cause.
MHDC is dedicated to active and effective collaboration among members of the Commonwealth's health care community in their use of information and technology to achieve sustainable improvements in quality, cost and effectiveness.


text:
Top 10 Black-Hat Hackers in the World | Tech News
By Prosyscom Tech On Jun 20, 2018
1. Kevin Mitnick
Kevin Mitnick was once the most wanted cyber criminal in the world. He had an obsession with computers that escalated into a two and half year hacking spree where he stole millions of dollars of corporate secrets from IBM, Motorola, telecom companies and even the National Defense warning system. He was caught twice in jail twice for his crimes, but now he is a computer security consultant .
Kevin Mitnick
2. Vladimir Levin
Vladimir Leonidovitch Levin is a Russian Hacker of genius proportions. In 1994 while working with a dial-up connection and a laptop from Saint Petersburg, Apartment he accessed the accounts of several large corporate customers of Citibank stealing USD 10.7 million. He ended up spending three years in jail. However, in 2005, an anonymous hacker group came claiming that they were the ones truly responsible for the theft and that they only sold Vladimir the data needed to steal the money.
Vladimir Levin
3. Mathew Bevan and Richard Pryce
In 1996, Mathew Bevan and Richard Pierce were 21 and 17 respectively, when they broke into military computers. They didn't only hack into US military computers, but the officials thought they might have also hacked into North Korean Systems as well. These people have the unique distinction of saying that they almost started a war.
Mathew Bevan
4. Michael Calce a.k.a MafiaBoy
Michael Calce, a Canadian Hacker was responsible for a series of high-profile cyber attacks in 2000. Project Rivolta a project name he called it meaning riot in Italian was a distributed denial of service attack that took down major websites Yahoo, FIFA, Amazon, eBay, CNN, and Dell among others. He was caught after bragging about the attacks in an IRC chat room for which he got eight months in jail. Why such a short sentence? Michael was only in high school at the time.
Michael Calce a.k.a MafiaBoy
5. Adrian Lamo
Adrian Lamo is best-known for hacking into major cooperations like Yahoo, Bank of America, Citigroup, The New York Times and Microsoft but the way he did it made him famous. He used public internet connections like libraries and coffee shops to hack to hack into major sites. Because of that style, he was named as 'Homeless Hacker'. In 2004 after being caught he was given six months house arrest in order to pay $65,000 in restitution.
Also Read: How to Use Google Chrome to Generate Secure Passwords
6. Jeanson James Ancheta
Jeanson James Ancheta has been the first hacker ever to create a botnet a group hijacked computers that work together as a legal means. In 2004, he started to work with botnets robot, a computer worm that can spread his net of infected computers which gave him control to 500,000 computers including US military computers. He was forced to give up his BMW, pay more than $58,000 and serve 60 months in prison.
7. Gary Mckinnon
Gary Mckinnon a.ka Solo is a Scottish hacker who masterminded the largest military computer hack of all time. He hacked into 97 US armed forces and NASA computers between 2001 and 2002within a period of just 24 hours he deleted critical files including weapon logs. In total the damage that his hacking cost, cost the government an estimated $ 700,000.
8. Owen Walker
Owen Walker a.ka AKILL was only 17 when he let in an international hacking group that cause over 26 million dollars in damages. The school teenager was responsible for creating the Bot virus which spread into 1.3 million computers around the world crashing them. Even though he was caught despite all the damage he was released without being convicted.
9. Astra
The hacker named Astra, whose real name was never revealed was a 58-year-old Geek Mathematician, who was operated between 2002 and 2008 during that five-year period. He stole weapons technology data in 3D modeling software from a company called the Salt Group, which he sold up to USD 361 million to buyers all around the world. He was tracked down in an apartment in Athens, Greece.
10. Albert Gonzalez
Albert Gonzalez, over a two year period he stole a total of 175 million credit card numbers selling them online. A massive yet undisclosed amount of money was stolen from his victims through identity theft, leaving them to battle to restore the credit ratings and get their money back. He was sentenced to 40 years jail.
PS: There were a lot more hackers out there, these people are those who got caught
Bonus Article: How to Become an Ethical Hacker?
Alexa for Hospitality: A clear example of IoT benefits for end user and business | Tech News
Couple uses Facebook to raise over $5M to reunite immigrant families | Tech News


At the start of our class on Surface Design class with Michelle Wipplinger of Earthues we each received a bag of primarily mordanted silk to use in the class. This saved us hours of prep work. Many of the pieces were delicate silk scarves. There was also one beautiful cotton shawl.
I totally enjoyed exploring the art of dyeing with these fabrics. I played with silk screens, stenciling and resists, including an interesting Japanese tool that created an effect I absolutely loved and that I will write about later this week.
The photo above shows my first two attempts at working with natural dyes. I did some silk screening and painting with sponges on the left lighter color piece. The darker piece was simple painting with natural dyes.
These two scarves involved more playing with painting with natural dyes. I also added some effects with pigments to the lower scarf.
Finally, here are two of my indigo pieces. I will eventually add some additional touches to the bottom one. I learned that I really loved dyeing with indigo.
Thanks, Gerrie and Margaret. I am excited about doing more.


text:
Home All Ailee - 5th Mini Album [I'm]
Ailee - 5th Mini Album [I'm]
ROCKET3 ENTERTAINMENT
Ailee [I'm]
I wasn't perfect
And longing name, 'us'
Ailee meets the public with her fifth mini-album in 10 months.
This album, [I'm], sung by Ailee with sincerity, contains the first of three stories about the process of Ailee, who was not full of color, gradually finding her perfect me.
Ailee's powerful and intense performance was put down for a while, and her sincere sentiment line and sincere voice met with lyrics and tunes that anyone could relate to.
All five songs included in this new album by Ailee contain an emotional and clear message.
In particular, the title song 'While We Love' is a song that melts the heart of regret, although I sang it sadly only after losing all the names of 'we' that I had only received unconditional love and could not take care of it.


About 36% of these are crusher, 18% are plastic crushing machines. A wide variety of crushers malaysia for sale options are available to you, such as jaw.
48984 products . Alibaba offers 48984 stone crusher machine price products. About 74% of these are crusher, 1% are sand washer, and 1% are other.
Jun 26, 2018 iron ore crusher machine malaysia – budget price iron ore . jaw crusher machines price in malaysia. stone crusher machine china china jaw.
Small diesel stone crusher and mobile crushing plant are technical . plant, How much is 10 " x 16 " diesel crusher price for sale Penang Port Malaysia ?
Powerscreen Stone Crusher - price of stone crusher machine in .
Powerscreen Iron Ore Mining Application Cone crushers, jaw . . price in malaysia jaw crusher powerscreen malaysia price, used stone crusher plant for sale in.
A wide variety of small portable stone crushers Hot Sale Portable Small Diesel Engine Stone Tire Portable Crusher Plant . Small Portable Rock impact crusher,stone crusher machine price in india,. . Portable Crusher Machine In Malaysia.
Jun 7, 2017 . thenewspk 18 Jun 2016, For over 40 years, stone crushers have been . crushing pulverising and screening equipment supplier malaysia.
High Productivity Deep Cavity Jaw Crusher,machine malaysia crushers,crusher . Used stone crusher machine and screening plant for sale in USA. used stone.
Dec 09, 2016· Click and get used stone crushing plant prices price list of stone . . iron ore crusher price in malaysia used cone stone crusher for sale in india.
1058 products . ce certificate malaysia wood crusher machine with factory price ... from wood crushers, my factory also makes plastic crusher, stone crusher, etc.
price dynamo 20 kg stone crusher south … price dynamo 20 kg stone crusher price dynamokg stone crusher Where can I find a suitable rock crusher stone plant.
primary mobile jaw crusher rental malaysia mobile crusher . primary mobile jaw crusher rental malaysia with a capacity range of up to 650 t/h,. Get Price.


Francis' decreasing popularity in Italy has been offset by growing popularity for the reigning populist, Eurosceptic government, and in particular its most charismatic member, interior minister Matteo Salvini.
While prelates and Church bodies have taken to demonizing Mr. Salvini for his determination to put a stop to Italy's mass illegal immigration problem, more and more of the Catholic faithful have found themselves more closely aligned with Salvini than with their own shepherds.
One recent poll showed that fewer than one in five Italians (19 percent) would like the government to reopen the country's closed ports to migrants, while only 12 percent of those surveyed said that it is the responsibility of individual states in whose territorial waters the migrant ships have arrived to resolve the situation.
The pope's marked political character has heightened the willingness of Catholics to disagree with their pastors, Galietti notes, since the pontiff's approximation to United Nations positions on global warming and international immigration can easily be brushed aside as simple leftist slogans with little if anything to do with the gospel of Jesus Christ.
Both in Italy and in Germany, Francis has paid the price of his "unqualified open-door policy toward migrants," Galietti writes, which has created a "double problem" even among practicing Catholics.
On the one hand, it is subject to "excessive vagueness" that seems to ignore the real problems faced by real people, Galietti notes. And thus it is "no coincidence" that Salvini's closure of Italian ports is the most convincing option among Italian Catholics, even who regularly attend mass, as recent surveys have shown.
On the other hand, "the politics of Pope Bergoglio is experienced as an attempt to void national identities," Galietti states, as Francis continually insists on the priority of multinational bodies while pooh-poohing the populist, nationalist, and pro-sovereignty sentiments of many Catholics.
Curiously, this last fear spans the divide between Europhile countries (Germany) and Eurosceptics (Italy), Galietti writes, and even moderately conservative parties throughout Europe are now examining possible alliances with right-wing groups that would have been anathema just a few years ago.
It is evident that the multilateral system as a whole is "going through difficult times, with the re-emergence of nationalistic tendencies," the pope warned a group of diplomats a week ago, as he put forward his conviction that globalist organizations are key to the maintenance of peace and international stability.
These nationalist tendencies "undermine the vocation of international organizations to be a space for dialogue and meeting for all countries," he said.
All in all, Galietti suggests, the pope's declining popularity is a side-effect of having hitched his horse to globalist political platforms and supranational formations, which to many Europeans is looking more like the past than the future.


text:
Home»Coins»Ripple»New episode of Do Kwon saga
New episode of Do Kwon saga
Terra co-founder Do Kwon, wanted by South Korean authorities, seems to live in a digital-era James Bond movie. The businessman, whose whereabouts are currently unknown, reacted via Twitter to Interpol issuing a Red Notice on him. Kwon told his followers that he calmly writes code in his living room, "making zero effort to hide." Active on social media while facing potential arrest and prosecution in South Korea, Kwon showed his location as Singapore on his Twitter account at the time of publication.
Meanwhile, South Korean authorities have requested crypto exchange OKX and Kucoin to freeze 3,313 Bitcoin (BTC) reportedly tied to Do Kwon. Reportedly, he created a new wallet under the name of Luna Foundation Guard (LFG) on Sept. 15, just a day after a Korean court issued an arrest warrant against the fugitive crypto founder. The movement of BTC from the LFG wallet raised many eyebrows, as it contradicts Kwon's early claims of having used all the BTC in the LFG's reserves to defend the peg of TerraUSD — since renamed TerraUSD Classic.
However, Terraform Labs claims that South Korea's case against its co-founder has become political, alleging that prosecutors expanded the definition of a security in response to public pressure. "We believe, as do most in industry, that Luna Classic is not, and has never been, a security, despite any changes in interpretation that Korean financial officials may have recently adopted," Terraform's spokesperson said told the Wall Street Journal last week. The company also believes the case to be "a failure to uphold basic rights guaranteed under Korean law."
Another blow for the SEC in the Ripple case
Ripple Labs scored another victory in its continuing legal battle with the United States Securities and Exchange Commission on Sept. 29, as United States District Court Judge Analisa Torres ruled to release the documents written by former SEC Corporation Finance Division Director William Hinman. The documents predominantly relate to a speech Hinman delivered at the Yahoo Finance All Markets Summit in June 2018 and could make evidence of Hinman stating that Ether (ETH) was not a security. Judge Torres' decision overruled SEC objections to releasing the documents following District Court Judge Sarah Netburn's order declaring that the emails and drafts of the speech were not protected by deliberative process privilege, as the SEC has claimed.
Russia aims to use CBDC for international settlements with China
Russia is reportedly planning to use the digital rouble for mutual settlements with China by next year. The digital rouble is currently being tested for bank settlements and is expected to be completed by early next year. Anatoly Aksakov, head of the finance committee in Russia's lower house of parliament, admitted that the geo-political crisis has limited Russia's accessibility to the international trade market. This is why they have been actively working for alternate modes of payment and trade settlements, and national digital currency seems to be the primary choice at the moment.
UAE Ministry of Economy opens up its headquarters in the Metaverse
The United Arab Emirates Ministry of Economy has announced a new headquarters located where anyone in the world can visit — the Metaverse. The headquarters will feature a multiple-story building, each serving a different purpose. Visitors will be able to take a ticket, which will prompt a "customer happiness center employee" to join the Metaverse and interact with the visitor. Visitors to the virtual headquarters will be able to sign legally binding documents, which eliminates the need for signatories to visit one of their physical locations in order to provide their signatures.


A new beta version (5.68.1) of AmiBroker has just been released.
Fixed crash occuring in 64-bit version when StaticVarGenerateRanks was used on large arrays.
AFL: since 5.63 round() function used 32-bit floorf which resulted in some differnces as compared to 5.60. Previous code version is restored now.
New Analysis: when two Analysis windows were open and running Scan simultaneously with AddToComposite composites could get reset by scan running in second window. Fixed.
Unsettled sale proceeds were settled at the end of the day instead of the beginning of the next day. Fixed.
Using more than 100 Plot() statements in one formula could cause memory corruption sometimes resulting in access violation. Fixed.
Low-level gfx playback engine resets colors to black pen / white background, so it does not get influenced by chart colors like labels.
GfxSetOverlayMode( 2 ) sometimes produced incorrect output in 5.67.0. Fixed.
New Analysis: Optimization continued even if there was error inside custom backtest procedure. Fixed.
Charting: a new "Warning 902 can not plot a chart in logarithmic scale as a data set contains negative value(s)" message is displayed on attempt to use log scale with negative data and the chart is plotted in linear scale instead.
UI: 'Logarithmic scale' item added to "View" menu.
AFL: GfxSetOverlayMode( mode = 1 ) did not work with "alternate background fill". Fixed.
Analysis Settings Load/Save buttons were positioned wrong in RTL (right-to-left) systems. Fixed.
ASCII importer: added DELISTED_DATE to fields available in $FORMAT command.
Information window: added "Delisting date" field.
Information window: it was not possible to set/change Dividend Pay Date and Ex Dividend date from UI. Fixed.
The database save was triggered when opening documents using recent file list. Fixed.
32-bit and 64-bit versions now use different registry key to save list of DLLs so warning messages about non-certified 3rd party plugins are not displayed each time you switch between 32-bit and 64-bit app version anymore.
Foreign("~~~EQUITY" ) within custom backtest proc in old AA returned zero (because of change in 5.65). Fixed.
CBT: when low-level mode was used (no ProcessTradeSignals was called) ~~~Equity open interest field was not filled with number of open positions. Fixed.
When user moved default Formula path somewhere else Report charts were not generated properly. Fixed.
Fixed crash @0048C19A/48C1C4 (click on result list after backtest to show arrows sometimes produced this).
New Analysis: In 5.64.x "stocknum" incorrectly started counting from 1 instead of 0 as in old versions. Fixed.
New Analysis: Walk-forward result list colums had "alpha" type which resulted in alphabetic sort when user clicked on column. Fixed (numeric type is used now).
QuickData did not work properly for not time-based intervals so it is now automatically turned off for charts using such intervals.
Trade profit calculation speeded up. Upto 15% faster optimization with lots of trades.
New Analysis: Multi-threaded Individual Optimization. Upto NumberOfCores faster. Note: no CBT and only exhaustive mode is supported.
Built-in constants such as colorBlack are now read-only and any attempt to overwrite such constant value results in error 55.
New Analysis, list view in scans, explorations and individual optimizations is refreshed less often to gain some speed.
In case of individual backtest / individual optimization the backtester allocates much smaller price cache (just for 2 symbols) – takes less time.
In 5.63 Bar Replay did not with "QuickData" enabled (it required View->Refresh All to start working). Fixed.
Some actions (like import of past data, split, etc) did not trigger automatic chart refresh when QuickData was enabled. Fixed.
QuickData for charts implemented. QuickData is a new feature that greatly decreases time required to prepare compressed/filtered data for real-time charts.
AFL: some transcendental math functions (sqrt, sin,asin, cos, acos, tan, atan, ln, log10, etc) are 10-30% faster now.
When loading and saving quotation files, AmiBroker does not allocate extra memory buffer. This conserves RAM when handling large files.
64-bit version is able to load/save files larger than 2GB per symbol (more than 53 million data bars per symbol). Note that you would need to use huge amounts of RAM as using 50 million data bars requires 6GB of RAM or more for any decent performance.
When user re-arranged tabs in the "Log" window, "Clear" and other right-menu commands used wrong tab. Fixed.
AddSummaryRows treated NULLs as zeros in averages. Now it is fixed and NULLs are not included in calculations.
Drawing tooltip "bars" count starts from 0 (when line is pure vertical) to match status bar X distance display. Status bar coords display is hidden once drawing is done to prevent user confusion.
When "Play" button is pressed Bar replay dialog checks if Start Date is earlier than End date and displays error message if that is not the case.
First line in "Parallel trendlines" tool is snapped to price (if the option is turned on) as normal trendline.
Max. chart rendering time of 1000 ms when multithreaded charts are turned ON can be overriden now by registry setting. See FC#2330 for details.


The theory of multiple intelligences was developed in 1983 by Dr. Howard Gardner, professor of education at Harvard University. It suggests that the traditional notion of intelligence, based on I.Q. testing, is far too limited. Instead, Dr. Gardner proposes eight different intelligences to account for a broader range of human potential in children and adults.


text:
package com.stablekernel.standardlib;

import android.os.Bundle;
import android.support.v4.app.Fragment;
import android.support.v7.app.ActionBarActivity;
import android.support.v7.widget.Toolbar;
import android.view.MenuItem;

public class SingleFragmentActivity extends ActionBarActivity {
    public static final String EXTRA_FRAGMENT_NAME = "EXTRA_FRAGMENT_NAME";
    private Toolbar toolbar;
    private boolean traceLog;

    protected void enableTraceLog(boolean enable) {
        traceLog = enable;
    }

    @Override
    public void onCreate(Bundle savedInstanceState) {
        if (traceLog) Log.d("TRACE", "--> SingleFragmentActivity.onCreate()");
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_single_fragment);
        toolbar = (Toolbar) findViewById(R.id.toolbar);
        setSupportActionBar(toolbar);
        getSupportActionBar().setDisplayHomeAsUpEnabled(true);

        if (savedInstanceState == null) {
            getSupportFragmentManager().beginTransaction()
                                       .replace(R.id.fragment_container, getFragment())
                                       .commit();
        }
        if (traceLog) Log.d("TRACE", "<-- SingleFragmentActivity.onCreate()");
    }

    protected Fragment getFragment() {
        String fragmentName = getIntent().getStringExtra(EXTRA_FRAGMENT_NAME);
        if (fragmentName == null) {
            throw new RuntimeException("You must either provide a fragment name or override getFragment() in a subclass to provide a fragment instance");
        }

        return Fragment.instantiate(this, fragmentName, getIntent().getExtras());
    }

    @Override
    public boolean onOptionsItemSelected(MenuItem item) {
        if (item.getItemId() == android.R.id.home) {
            Fragment currentFragment = getSupportFragmentManager().findFragmentById(R.id.fragment_container);
            if (null != currentFragment && currentFragment.onOptionsItemSelected(item)) {
                return true;
            } else {
                finish();
                return true;
            }
        } else {
            return super.onOptionsItemSelected(item);
        }
    }

    protected void handleError(Throwable e) {
        handleError(null, e);
    }

    protected void handleError(String message, Throwable e) {
        ErrorHandler.handleError(this, message, e);
    }

    protected Toolbar getToolbar() {
        return toolbar;
    }
}


Pretty paisleys mixed with velvet embody all you love about English country manor style. The faux button and flange closure are simple, sophisticated and supremely elegant. The coordination of fabrics and opulent trims add richness to the decorative pillows, and all six have removable covers and feather inserts. The leopard skin pillow adds a touch of the whimsical. The bed skirt has a 21" drop. The comforter reverses to the same fabric as the skirt. The Euro shams have hidden zippers and are reversible. This set is available in either a 13-piece King set, or a 12-piece Queen set.