text:
Web services are a transformational technology for integrating information sources from both inside and outside an enterprise. Web services are the newest incarnation of middleware for distributed computing. Unlike all previous forms of middleware, however, this is a simpler, standards-based, and more loosely coupled technology for connecting data, systems, and organizations. That is good news for architects and developers wanting to quickly become proficient in this technology and deploy real systems. It is also somewhat bad news for architects and developers because all middleware needs strong security practices, and Web services need it more than any middleware of the past. Why more? Because Web services create loosely coupled integrations. Because Web services are not just being used to integrate internal systems, but they are also integrating data sources from outside the organization. Because Web services are based on the passing of readable and self-describing business messages represented in XML. Because Web services are based on underlying Web technologies that already had their own set of security challenges.
It is true that Web services—like most new transformational information technologies introduced—have been overhyped, and it is true that fears of security problems have also been overblown, which has impeded the development and deployment of Web services. It is also true that the standards for Web services are either quite new or in some cases not even fully baked yet. This book is designed to take the mystery and fear out of how to build secure Web services and to shed light on these new standards and how to best use them. It is also designed to show you the richness and complexity of the security issues around Web services so that you, the designers, builders, and operators of Web services, can fully exploit all the capabilities of Web services to your best advantage but do so knowing full well what all the security challenges are and how to face them.
This chapter covers the basics of Web services and information security and the way Web services security builds on existing security technology. This sets the stage for a deeper understanding of the major standards for information security associated with Web services.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
{mospagebreak title=XML, SOAP, and WSDL}
Four technologies form the basis of Web services: eXtensible Markup Language (XML); SOAP (See Footnote 1 at end of article); Web Services Description Language (WSDL); and Universal Description, Discovery, and Integration (UDDI) (Footnote 2).XML and XML Schema
XML was created as a structured self-describing way to represent data that is totally independent of application, protocol, vocabulary, operating system, or even programming language. Many call XML the lingua franca of business because it is being used so broadly across all industries to portably transmit business data. The use of XML presents a broad set of security challenges.
XML Schema is a way of describing the rules for a particular XML instance (also known as a document). XML can be used independently of XML Schema; however, in Web services and most business situations, the XML that you work with will be governed by an XML Schema (perhaps created by a development tool and put into your Web services WSDL file for you).
XML is the foundation of the Web services standards. All standards for describing, discovering, and invoking Web services are based on XML. SOAP and WSDL are described using XML Schema. The core security standards of XML Encryption, XML Signature, Security Assertion Markup Language (SAML), and WS-Security are XML-based and are also described by an XML Schema.
XML and HTML are both text-based formats that came from the same roots. XML was initially developed to overcome the limitations of HTML, which is good at describing how things should be displayed but is poor at describing what the data is that is being displayed. XML being text-based is very important to Web services; because it is human-readable, no tools are needed to parse and render the data, and simple text tools and editors are sufficient for its manipulation. XML documents are very wordy, and although you can easily become lost in the depth and richness of the tags, its markup format of tagged elements arranged in a hierarchical structure makes XML documents easy to comprehend. But there is a security price to pay for the open, text-based structure of XML. As you will see later, to provide data integrity—a guarantee that not one bit in the original document has been changed—with XML, you have to guarantee that not one character—even whitespace—of an XML message has been changed. Verifying data integrity is particularly challenging when using XML since differences in platforms and XML parsers can result in logically equivalent documents being physically different; consequently, a process of canonicalization is necessary to make a valid comparison with the originally signed document. This is just one example of the special considerations needed when considering Web Service Security.SOAP
SOAP was created as a way to transport XML from one computer to another via a number of standard transport protocols. HTTP is the most common of those transports and is, of course, the most prevalent transport used by the Web itself.
SOAP itself is defined using XML, and it provides a simple, consistent, yet extensible mechanism that allows one application to send an XML message to another. SOAP is what makes application integration possible, because after XML defines the contents of a message, it is SOAP that moves the data from one place to another over the network. SOAP allows the sender and receiver of XML documents to support a common data transfer protocol. SOAP allows you to treat XML messages as requests for remote services. The SOAP model allows a clean separation between infrastructure processing and application processing of messages. Figure 1.1 shows the basic structure of a SOAP message.
Figure 1.1 The basic structure of SOAP.
SOAP provides an envelope into which an XML message is placed. This envelope is just a container to hold XML data. The idea is for SOAP to create a uniform container that can then be carried by a variety of transports. SOAP prevents applications from caring about the transport; the applications see consistency in the SOAP envelope and its contents.
Inside the SOAP envelope are two parts: the header and the body.
SOAP header—Contains information about the SOAP message (as opposed to the XML message contained in the SOAP body). This information is used to manage or secure the package. SOAP is designed to be extensible, and a major area for extension is the SOAP header. Chapter 7, "Building Security into SOAP," which describes WS-Security, provides more detail on SOAP header security extensions.
SOAP body—Contains the message payload. This information is being sent from one application to another. It might be a full document such as a purchase order or contract, or it might be a description of remote-procedure call information, including the methods to call and parameters to those method calls.
The simple SOAP message in Listing 1.1 shows an envelope that contains both a SOAP header and a SOAP body.
Listing 1.1 SOAP Envelope
<?xml version="1.0″ ?>
<env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope">
<n:alertcontrol xmlns:n="http://example.org/alertcontrol">
<m:alert xmlns:m="http://example.org/alert">
<m:msg>Pick up Bobby at school at 2PM</m:msg>
To understand SOAP, you need to understand the different "styles" of SOAP bodies. RPC-style SOAP bodies tend to be simple parameters to facilitate calling a remote method. Document-style SOAP bodies tend to be rich XML documents. Document style, in our view, is more appropriate for B2B Web services because it is usually more optimal to have "chunky," coarse-grained calls across a slow network rather than the fine-grained type of RPC call that you might use locally or on a fast network. This is not just due to the network but also due to the cost of marshalling and unmarshalling the XML and performing security-related operations.
SOAP needs to be secured. The messages it carries must be kept secret from unintended recipients. The remote service being called must know who is calling it and know the caller is authorized to do so. SOAP is a packaging mechanism for XML messages and documents. Like any package, it needs to describe important information about its contents, such as who it is from, how a recipient can trust that it really is the sender, what the sender is allowed to do, and much more. These are identity- and trust-related issues; they are the core of SOAP security discussed in detail later in this book.WSDL
WSDL is an XML language that defines the set of operations that a Web service provides and the structure of their related SOAP messages. That is, the WSDL defines what the input and output structure will be for a Web service, and that will define what you expect to see in the payload XML message. WSDL is how one service tells another which way to interact with it, where the service resides, what the service can do, and how to invoke it. WSDL directly supports developers and is absorbed at application development time into developer tools. WSDL's definitions of remote services are presented to programmer-like local objects that can be acted upon as if they were methods in classes, just like any of their other local objects.
When you publish a WSDL for one of your services, you are creating a contract for how other services may interact with you to utilize your service. WSDL is what you publish to describe your Web service and the rules for how to work with it. You might think that security would also be described in WSDL because this is part of the rules for working with a particular Web service; however, the security options (security policy) available are richer than what you typically see in WSDL, so the standards are evolving toward using WS-Policy to describe a Web services security policy and then referring to this policy from the WSDL. Chapter 8, "Communicating Security Policy," goes into more depth on WS-Policy.
A WSDL file has a what section, a how section, and a where section. The what section specifies the input and output messages. The how section defines how the messages should be packaged in the SOAP envelope and how to transfer it. It also defines what information should be included in the SOAP header. The where section describes a specific Web service implementation and ways to find its endpoint.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
UDDI is typically the fourth leg of the stool used to define Web services. Although we view UDDI as a useful standard, we do not see its usefulness beyond internal promotion of reuse inside large organizations. Given that, we do not put it front and center as a part of our discussions of Web services security and will not treat it further in this book.
Before you dive into the security implications of each of these Web services standards, you need some context: What are Web services really for? The answer is, among other uses that undoubtedly will develop as this new paradigm matures, application integration, B2B business process integration, portals, and service-oriented architectures.Application Integration
Application integration is critical to organizations large and small because information integration is so fundamentally important. When organizations integrate all their applications that deal with customers (CRM, ERP, accounting, billing), they are trying to create a single view of all the information about those customers. When they integrate all their trading partners into a single supply chain, they are attempting to create a holistic view of their entire supply chain and all the information that describes their trading processes. This kind of information integration is fundamental to the business process. Rarely does a business process (product development, product marketing, product manufacturing, product ordering, product fulfillment, customer relationships, partner relationships, financials, and so on) utilize one and only one source of information (an application). It is because business processes cross application boundaries and even enterprise boundaries that Web services are needed to create those bridges.
Application integration is hard because systems were not designed with the same data structures, protocols, or even the same vocabulary for describing the items they manipulate. Applications were built at different times by different vendors using different technologies. However, many of these different applications need to communicate to perform certain functions. This is where XML comes in. It makes information easy to interchange and therefore easier to integrate.
The glue used to communicate from one application to another has traditionally been called middleware. Middleware has never been pervasive and was always very expensive. Rarely has anyone ever tried to use middleware between enterprises because simply using it within a single enterprise's boundaries is hard enough. SOAP is a critical step in taking XML messages toward being Web services middleware. In one of its modes, SOAP makes XML into a request/response paradigm that is published via WSDL. Web services are becoming pervasive because they are middleware based on the Web, and the Web is pervasive.B2B Business Process Integration
Business processes don't stop at your company's firewall. Just as internal application integration is partly motivated by the need to break down application barriers, inter-organization business processes motivate B2B application integration. A driving need to integrate across organizations comes from management of supply chains and demand chains with trading partners. Traditional middleware could never be employed to solve this need because it never worked across the Internet.
The good news is that the Internet is pervasive. Most Internet communication occurs via text (for example, HTML is text, email is text), and virtually all applications have some form of text interface. XML is text-based and is designed to make business information transportable and self-describing. XML, plus the fact that all vendors support Web services, has moved us closer to solving the heterogeneous communication problems of different languages, different platforms, and different applications than any middleware technology of the past.
For these reasons, Web services technology is built on XML and Web technologies, which makes it the first middleware that can address the B2B business process integration challenge.Portals
On the Internet and within intranets, portals are the entry point for customers into a site. Portals have been growing in utility and importance for some time as a way to aggregate information and applications into a single site that is accessible by browsers. Portals as major business models have been common for years. Amazon.com, Yahoo!, and Orbitz are all fundamentally portals. They pull information from their partners' repositories into a single site that consumers with browsers visit to buy books, music, and consumer goods; plan trips; and the like. Most of these major Web e-commerce companies built their portals long before Web services standards existed. They effectively built Web services to integrate all their information content using home-grown approaches. Companies trying to do what they have done now can do it much more cheaply and easily and remain much more interoperable by using the new Web services standards.
Companies are rapidly turning their corporate intranets into portals to provide a wide range of company-related information and services to employees, shareholders, and partners. One type of service they are providing employees is a unified benefits information resource. To make that a complete service, the 401k information from third-party providers must be integrated into the corporate portal. That is a perfect use for secured Web services that bring the employees' 401k account information into the corporate benefits portal by accessing the external services of the 401k provider.
Integrated customer information is so much the lifeblood of all companies that both customer relationship management (CRM) and customer information portals have represented large corporate investments for many years. Naturally, because Web services are less expensive and less complex than any previous form of middleware, they have been brought to bear on this common need.Service-Oriented Architectures
In a service-oriented architecture (SOA), the interface is completely separated from the implementation. The software is provided strictly as a service that does not have to be downloaded and installed. SOA promotes reuse and sharing of services by numerous applications and even by different organizations. People describe an "SOA nirvana" when all systems are built as SOA and all applications are composite—built by stitching together several useful shared service components into powerful applications. Many people look to Web services to bring us to this SOA nirvana (Footnote 3).
The idea of services as being a powerful computing paradigm is not new. A service is an application that can be consumed by software as opposed to a human at a browser. It is software that does work for other software. It is how RPC mechanisms work. This was the premise of the client/server computing revolution of the early '90s. In this model, the server provided the service.
The benefits of a service-oriented architecture are legion. The complexities of a software system are hidden behind its interface. A complex software system becomes a simpler black box defined only by its external interface. The service so constructed becomes a shared resource that can support many applications.
Web services combine the concept of software-as-a-service with the ubiquity and connectedness of the Web. This is what makes Web services so compelling and so exciting: They create a Web API. We are talking about building applications with a broadly accepted standard API based on Web technologies. Web services enable you to wrap legacy applications with this Web API and turn them into shared services. Now these applications can be integrated with other applications and with trading partners. Previously inaccessible information resident in these legacy applications can be brought out to portals and combined with other application information and all made accessible to any user with a browser. Any application can be modified to provide this type of Web API and therefore can be integrated with any other application, allowing you to use the entire Web for application-to-application integration. This, then, is the power of Web services.Definition of Web Services
A good working definition of a Web service, then, is an application that provides a Web API. The API enables the software resource to act as a service. Being a Web API means that this service is accessible at an Internet URI. Further, an API supports application integration, so a Web API allows application-to-application integration using XML over Web protocols and infrastructure. All the security and trust issues of being part of the open Web infrastructure will concern us. All the information security and message security issues inherent in sending messages from one network point to another will concern us. All the authorization and authority security issues inherent in middleware that performs RPCs will concern us. Now, let's cover some security basics to build a foundation for our deeper discussions in later chapters.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
The Web is an interconnected global information system that provides resources suitable for consumption directly by humans. In this model, security is critical for many of these resources (login-password authentication at restricted sites, SSL encryption of credit cards and other personally identifiable confidential information). It only makes sense, then, that application-to-application Web services need at least this much security as well.
In fact, because Web services expose critical and valuable XML-encoded business information, Web services security is a critically important concept to fully understand. For one thing, trade secret pilfering is already a large problem, and without security, Web services might even make this situation worse. The reason is that Web services can be thought of as allowing in strange, new users who might take your company's valuable business secrets out.
This section covers basic security concepts to establish the vocabulary that will be used throughout this book. Keeping communications secret is the heart of security. The science of keeping messages secret is called cryptography. Cryptography is also used to guarantee trust in a known identity across a network by "binding" that identity to a message that you can see, interpret, and trust. An identity asserting itself must be authenticated by a trust authority to a previously established identity known to the authority for the binding to be valid. After you know the identity, authorization allows you to specify what the individual with that identity is allowed to do. When you receive a secret message, you need to know that nothing in the message has been changed in any way since it was published, an attribute called integrity. When cryptography successfully keeps a message secret, it has satisfied the requirement for confidentiality. At times, you might want to know that someone who received confidential information cannot deny that she received it, an important security concept called non-repudiation.
Most of these core security concepts depend on encryption technologies, so before you look at any of them more closely, take a look at the fundamentals of encryption.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
We won't get very far in our security discussions without bumping into shared key and public key technologies. They, in turn, stem from cryptography. We will briefly introduce these concepts here so that we can apply them where needed throughout the rest of the book.Cryptography
Cryptology is the branch of mathematics focused on designing algorithms to keep information (data) secret. Cryptography is the work of applying these algorithms to secure systems, protocols, applications, and messages (Footnote 4).
The first and most important area of cryptography to discuss is encryption. Encryption is the basis for XML Encryption and also for XML Signature, which encrypts a digested form of a message. The message digest encrypted in a digital signature is created using another important cryptographic algorithm called a hash function, which is a special class of one-way function that creates a fixed-size (small) output that is unique for all input messages and that is not, in practice, reversible. In the Web services arena, you will find common uses for both shared key (Footnote 5) and public key encryption.
A message that is completely readable and is in no way scrambled or disguised is called plaintext. Plaintext is unencrypted data. Encryption is the process of scrambling or disguising plaintext by applying a cryptographic algorithm to produce ciphertext. Ciphertext is encrypted data. Decryption reverses the encryption process and turns ciphertext back into its original plaintext form. These concepts are shown in Figure 1.2.
Figure 1.2 The relationships between plaintext and ciphertext, and the encryption and decryption processes that transform them.
The goal of encryption—and therein the way to achieve confidentiality—is to create ciphertext from plaintext that is undecipherable to anyone except the intended recipient. A special cryptographic algorithm that creates seemingly random permutations on the message, but which in fact are reversible under the right circumstances, performs the encryption process.
The algorithms for encryption and decryption require a key, which is a special numeric value that is required as a parameter for the algorithm to perform its task. The wrong key will get garbage out, not the correct output.
Shared key algorithms use the same key performing encryption and decryption symmetrically and are relatively fast. Public key encryption uses different but mathematically related (a public and private pair) keys performing encryption and decryption asymmetrically and is primarily used for secure shared key distribution and digital signatures.
Throughout this book, we will use the term shared key when we refer to symmetric encryption and public key when we refer to asymmetric encryption. We will use the term subject to refer to the holder of a key. A subject may be an individual or an entity (computer).
The magic is in the keys. But what is a key, and what does it have to do with encryption?Keys
A key is a set of bits that acts as an input parameter to a crypto-algorithm. Think of the crypto-algorithm like the lock on your house door. That lock is standard, and so is your door. Lots of other people have doors and locks that are outwardly exactly the same as yours. But inside the lock on your door are some unique (or almost (Footnote 6)) settings of tumblers that exactly match your and only your key.
Algorithms for encryption and decryption do not need to be and normally are not kept secret. It is the key that is kept secret. It is an important fundamental principle of cryptography that the algorithms be public, standard, and widely distributed and carefully scrutinized. This principle ensures that all the world's cryptographers fully shake out the algorithms for any security flaws.
The key is the variable that makes the algorithm result unique and secret. For some crypto-algorithms, the key may be a random number. For others, such as public key algorithms, it must be carefully chosen—a complex, time-consuming mathematical operation by itself. The key space needs to be large, so a large number of possible keys is available to prevent guessing attacks. Different algorithms require different key lengths for good security. Most keys today are typically 200 bits or larger.Shared Key Cryptography
Shared key cryptography uses the same key to encrypt and decrypt the data. This requires that both communicating parties share the same key and, vitally important, keep it secret from the rest of the world. As shown in Figure 1.3, plaintext is encrypted into ciphertext by the sender using the shared secret key. The ciphertext is then decrypted by the receiver using the same shared secret key.
Figure 1.3 The shared key (symmetric) encryption process.
The advantage of shared key encryption/decryption is that the algorithms are fast and can operate on arbitrarily sized messages. The disadvantage is that this approach creates great difficulties managing a shared key that must be kept secret across a network between message sender and recipient. Within Web services security, you will run into shared key cryptography as the basis of Secure Socket Layer (SSL) security and as the foundation for XML Encryption. Much effort has been put into XML Encryption to take care of most of its details for you. But you will be exposed at the minimum to choices you will have to make about algorithms, key information, and the like, so it is important you gain a foundation in these concepts.Public Key Cryptography
Public key cryptography uses a key pair called a private and public key. Whichever one is used to encrypt the data is not the one used to decrypt the data; only the other half of the pair can decrypt the data. Of vital importance is that the private keys are never shared. Only the public key can be, and it is widely distributed to others. We repeat that it is an absolute tenet of public key cryptography that each subject keeps his private key confidential, never sharing it with anyone.
Either key can be used to encrypt, but only the matching key from the pair can then be used to decrypt. In Figure 1.4, the sender uses the public key of the recipient to encrypt her plaintext message into ciphertext. The resulting ciphertext is sent to the recipient who uses her private key to decrypt the ciphertext back into the original plaintext message.
Figure 1.4 The public key (asymmetric) encryption process.
If you want to make sure only the recipient can read your message, use that person's public key to encrypt, and then he and only he using his private key can decrypt. If you want everyone who gets your message to know it came from you and only you, use your private key to encrypt and then the recipients can use your public key to decrypt. Because you keep your private key highly secure, the message could have been encrypted only by you.
Now that you have a basic understanding of encryption and digital signature, we can establish working definitions for critical security concepts that will be used throughout this book.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
Authentication, authorization, integrity, confidentiality, and non-repudiation are critical concepts for your understanding of Web services security, so the following sections provide a bit more detail on each one.Authentication
Authentication involves comparing provided identity information (a "challenge") to something already stored about this individual. Authentication is classically divided into three types: something you know, something you have, or something you are:
Something you know—Pin, password, pass phrase, shared secret
Something you have—Key, card, token
Something you are—Biometrics such as fingerprint, retinal scan, voice print, palm print
Single-factor authentication (using just one of the preceding types) is the simplest but is not very strong. Stealing or guessing a password is easy, and the rightful individual has no way to refute this is the case. Furthermore, because a password is something you know, you can tell it to someone or she can guess it, and with no other factor checked, that person is into the system with nothing stopping her.
Two-factor authentication, also known as strong authentication, is much stronger and is considered the standard when authentication is for anything of high value. Either something you have or something you are is added to the something you know category of shared secret. Something you have is typically a card, token, or device of some sort. Something you are is a biometric such as a fingerprint, retinal scan, or voice print. Outside military applications, authentication stronger than two-factor is rarely found. To strengthen two-factor authentication, you must strengthen the process used to create the individual factors.
How rigorous the authentication needs to be and what types of factors should be used in the one-, two-, or more factors of authentication require that you think about the level of trust needed. What is it that you are trying to protect? If the Web service is one that integrates vendors into your supply chain, and they have no access to critical corporate or customer data, the level of authentication may be lower than for a Web service that integrates an employer to its 401k provider and represents an employee requesting fund reallocation.Authorization
Authorization is the process of establishing what someone who has been authenticated is allowed to do. The entity receiving the request for service will be granting permissions for each identity to access certain items.
Most Web services coming in over the public network to an enterprise require authentication; it is not usually acceptable to provide services that you expect to be paid for without knowing who is using them. So fundamentally, authorization requires authentication. Additionally, Web services frequently expose vital business data to the requestor, who must be identified and not remain anonymous. Exceptions to this rule are free services that do not care who use them. If a service provides different levels of access depending on who is using it, that service also requires authorization to determine, based on identity, what services are accessible to whom.
One way that authorization is implemented is through a set of credentials that a subject identity carries and presents; those credentials are then mapped into access to certain restricted items. Alternatively, rights can be attached to restricted content, and these rights are mapped to identities and the permissions they will be granted to this content.
On the HTML-based Web, authorization has typically been very coarse grained and either gives access to entire sections of a Web site or denies access completely. With Web services, on the other hand, very fine-grained control specifying access to messages, parts of messages, or content carried by a message is possible. Unlike many security concepts, authorization is actually very easy to understand, but it turns out to be exceedingly complex technologically as well as socially. You will see why in Chapter 6, "Portable Identify, Authentication, and Authorization," which discusses standards such as SAML that are involved with this aspect of identity.Integrity
Integrity is an assertion that no one has tampered with a message since it was initially created. This assures the sender and the receiver that every bit produced by the sender is received by the recipient in precisely unaltered form. In cryptographic terms, data integrity is accomplished by using digital signatures. Messages in which data integrity is required (Footnote 7) must explicitly or implicitly include the identity and credentials of the sender to enable this kind of message-level security. Why? Because proving integrity means proving no bits have been changed in the message, which involves sending something with the message that no one in the middle could fraudulently create. That, in turn, requires signing that data with a key that only the sender could have had (more on this in Chapter 4, "Safeguarding the Identity and Integrity of XML Messages"). Message integrity- and identity-related issues (authentication and authorization) are often inter-related. Ironically, no matter how sophisticated your security technology becomes, the core security issue comes down to this: Do you know whom you are dealing with and do you trust those people?Confidentiality
Confidentiality is keeping the message secret. This process requires encryption, which scrambles the message in such a way that only authorized identities can decrypt and see the data. To do this, you exchange a shared secret and an algorithm for encrypting and decrypting the message. You could imagine Bob and Alice agreeing that they were going to encrypt their messages to each other by adding some number to each letter in the alphabet (the algorithm) and that number would be 2 for the next five days (the key). Thus, the message from Bob to Alice would look scrambled to a reader, and even if you knew the algorithm, you would have to do some analysis (not much in this case) to figure out how to decode the message. In the real world, these algorithms are very challenging mathematical functions with keys that are very large numbers, and the time to do the analysis is technically infeasible even with modern computers.
With typical contemporary encryption strategies, you provide the algorithm openly and rely on the strength of the key to keep the encryption secure. The trick is keeping the key secret. You could keep the key secret by giving it to the recipients in some way outside the message exchange, such as mailing it to them or phoning them. However, this approach doesn't scale up very well to large numbers of participants, so exchanging this key usually requires Public Key Infrastructure (PKI) technology, which is designed to manage and exchange keys. Chapter 3, "The Foundations of Distributed Message-Level Security," describes PKI in more detail, and Chapter 5, "Ensuring Confidentiality of XML Messages," goes into a lot of detail about encryption, specifically XML Encryption.Non-repudiation
As digital transactions are used in more and more legal contracts and as the acceptability of digital signatures becomes commonplace, the legal aspects of identity will become critical for Web services. First and foremost among those legal aspects of identity is non-repudiation.
Non-repudiation proves that one identity sent the data only to another identity. This then proves that this specific transaction was entered into by the recipient, and neither party can refute or deny that it occurred later. If the transaction is challenged legally, a contract that was supposedly executed must be shown to have been entered into by both parties. Each party must have seen the contract as signed, and their identities—confirmed traditionally by validating "wet" signatures on paper and notary witnesses—must have been confirmed at the time of signing. These are difficult, and as yet legally unchallenged, tenants to uphold in a digital and anonymous world, but that day is coming.
Non-repudiation depends on public key cryptography technology. You prove that one identity sent the data only to another identity because the sender used the recipient's public key, and it is only the recipient with his secret private key who can decrypt the data. To achieve legal non-repudiation, more is needed, such as a separate time-and-date-stamp notary to prove when the transaction occurred as well as independent verification of the participants' identities.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
Building on the brief introduction to Web services and information security, you can now delve into Web services security basics. A basic tenet of Web services security is that no new security technologies were invented. Instead, you will build on established security technologies and purpose them to your message-level security needs.XML Signature
XML Signature is foundational technology for the standard called WS-Security, covered in detail in Chapter 7, and for Web services security in general. XML Signature is built on top of mature digital signature technology. The purpose of digital signatures is to provide a mechanism for message integrity (no one has changed the message since it was created) and non-repudiation (you cannot refute that this message exchange occurred). XML Signature enables you to encode digital signatures into XML.
Electronic signatures were approved by Congress in June 2000. This approval gives legitimacy to electronic signatures and prevents the contesting of a signed contract solely because it is signed electronically. This event set the stage for digital signature standards. The genesis of XML Signature was a joint IETF/W3C working group called XML-DSig that was established to create a highly extensible signature syntax tightly integrated with existing XML technologies, but one that could also handle composite documents from diverse application domains as well. The XML-Signature Syntax and Processing W3C Recommendation defines the XML Signature syntax and associated processing rules. Its ancestors include PKCS#7 Signature and S/MIME. PKCS#7 is part of Public Key Cryptography Standards (PKCS) created by RSA Data Security. With this standard, someone could sign XML, but not in a way consistent with standardized XML format. And it was not possible to sign just part of an XML document as it is with XML Signature. Secure Multipurpose Internet Mail Extensions (S/MIME) already provided a way to bind a digital signature to an email message in a way that allowed the recipient to verify both integrity and non-repudiation of the signer.
XML Signature is a core foundation for Web services security. It was the first XML security standard to reach recommendation status. It is core to WS-Security, XKMS, and other Web services security standards you will be learning much more about. It will be core to your being able to provide integrity and non-repudiation, and you will also find it to be invaluable in the process of transporting shared secret keys that are needed by XML Encryption.
XML Signature is the topic of Chapter 4.XML Encryption
Like XML Signature, XML Encryption is built on top of mature cryptographic technology—in this case, shared key encryption technology. Core requirements for XML Encryption are that it must be able to encrypt an arbitrarily sized XML message, and it must do so efficiently. Those two factors led its creators to choose shared key (symmetric) encryption as the foundation for XML Encryption. Encryption provides for message confidentiality (the message will be secret from all but the intended recipient). The reason XML Encryption is needed over and above transport-level encryption such as SSL is that you need to maintain confidentiality of messages in the face of the message taking multiple hops on its way to its destination. This will be common when shared services are utilized. You also need confidentiality when the XML message is stored even after it reaches its final destination. This requirement is called persistent confidentiality.
Like XML Signature, XML Encryption applies standard algorithms to data and then stores that encrypted result in XML. And as with XML Signature, you can apply encryption selectively only to portions of a document.
XML Encryption builds on and shares several concepts with XML Signature. Like XML Signature, it is a W3C Recommendation. It is a vitally important second foundation to Web services security because it is the way you will achieve confidentiality in your XML messages. Remember, the key benefit XML Encryption brings over any other encryption strategy is that it allows confidentiality to be satisfied across more than just the context of a single SOAP request.
XML Encryption is the topic of Chapter 5.SAML
The purpose of SAML is to allow trust assertions to be specified in XML. Assertions apply to an individual or an entity and are "attached" to a message and go where it goes, leading to the simple description of SAML as enabling "portable trust." SAML assertions take the form of authentications, authorizations, or attributes of entities. Assertions can be claims, statements, or declarations. Assertions are accepted as true only in the context of the integrity and authenticity of the entity making the assertions. At this point, the situation becomes really complicated: Everything you are counting on depends on third parties; you have to trust them to trust the individual on whose behalf claims and assertions are being made.
SAML defines a set of Web APIs (that is, Web services) to be used to obtain these assertions from trust services that make authorization and authentication decisions about individuals and entities. After the SAML authority has made its assertions, SAML also provides a way to exchange this information with other systems. As you will see, WS-Security is enabled to use SAML as one of its security tokens applied to a SOAP message. You will also look at a large project called Project Liberty that is setting out to use SAML (and actually extend it) assertions across multiple security domains, allowing single sign-on to a circle of trust established between business partners.
SAML came from a blending of the two early standards efforts around portable trust called S2ML and AuthML. SAML is developed through the Organization for the Advancement of Structured Information Standards (OASIS) XML-based Security Services Technical Committee (SSTC). SAML 1.0 was approved as a standard in November 2002, version 1.1 was approved as an OASIS standard in August 2003, and a working group is already discussing v2.0.
SAML is the topic of Chapter 6.WS-Security
XML Signature and XML Encryption are about XML security. So what is WS-Security about? It is about SOAP security.
WS-Security is an overarching conceptual model that abstracts different security technologies into "claims" and "tokens." Ways to package security tokens into SOAP messages are the nuts and bolts of WS-Security. The broader context of WS-Security is a set of additional road-map specifications built on these concepts and solidified into XML specifications. They involve how to apply for a security token, how tokens are linked to identity, how they are linked to a Web service, and more.
Microsoft initially released WS-Security in October 2001. In April 2002, IBM and VeriSign joined Microsoft in releasing their joint document called "Security in a Web Services World." This initial security framework was submitted to OASIS in June 2002. OASIS formed the Web Services Security (WSS) technical committee in September 2002 to standardize this specification. Most platform and tools vendors will have shipped support for the initial WS-Security draft specification by early 2004. The WS-Security specification reached "committee draft" status in January 2004.
WS-Security provides a mechanism that allows you to digitally sign (using XML Signature) all or part of a SOAP message and pass the signature in the SOAP header. It provides a mechanism that allows you to encrypt (using XML Encryption) all or part of a SOAP message. It also provides a way to pass information in a SOAP header about the encryption keys needed to decrypt the message or verify the digital signature. And it allows trust assertions about the SOAP message to be passed in the SOAP header as well. A variety of bindings for security tokens have been defined. All these tokens will be explained in detail later.
WS-Security is the topic of Chapter 7.Trust Issues
WS-Policy allows organizations exposing Web services to specify the specific requirements of their Web services for such issues as privacy or security. WS-Policy is a high-level specification providing the basic constructs needed to compose a particular policy language (such as WS-SecurityPolicy). Closely related to WS-Policy is WS-PolicyAssertions, which provides some basic policy assertions that would apply to any type of policy (for example, the Language assertion), and WS-PolicyAttachment, which gives guidance on how to attach a policy to a resource (for example, a WSDL). WS-SecurityPolicy is a specific type of policy using the WS-Policy framework that answers certain security requirement and configuration questions for a Web service, such as What encryption algorithms are supported? What parameters must be encrypted? What types of security tokens are understood?
The WS-Policy family is the topic of Chapter 8.Other WS-Security–Related Specs
WS-Security is a broad description of a framework indicating how to secure Web services. To complete the picture begun with the discussions of WS-Security and how it can be used to secure SOAP messages and continued with the policy framework described by WS-Policy and its constituents, we need to fill in the other technologies related to and used by WS-Security. They include more policy-related specifications such as WS-Privacy; the WS-Trust API to trust services; topics related to federation such as WS-Federation, WS-Authorization, and WS-SecureConversation; and a suite of supporting standards not directly in the WS-* family. Those other important standards include The XML Key Management Specification (XKMS), eXtensible Access Control Markup Language (XACML), and eXtensible Rights Markup Language (XrML).
Coverage of other WS-Security–related specifications and technologies appears in Chapter 9, "Trust, Access Control, and Rights for Web Services."
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
This chapter asked the question "What are Web services, and why do they need security?" The answer is that Web services are the latest evolution of middleware that creates a loosely coupled RPC mechanism for application and information integration.
This chapter provided a brief introduction to XML, SOAP, and WSDL. The XML language is not only the way Web services messages are formatted, but it is also the language in which all other Web services standards are defined. XML is not new, and there are mature standards for securing XML messages. SOAP is the packaging mechanism for transporting XML messages over networking protocols and for treating XML as an RPC mechanism. WSDL separates the interface for a Web service from its implementation.
There are many types of application integration, and this chapter briefly covered the most common types and described why they need security. Internal application integration is most commonly used to integrate information from different sources within an organization to create more useful and more powerful composite applications. These types of integration need security from prying internal eyes and to comply with internal as well as external business practice policy regulations. B2B business process integration allows organizations to integrate with their supply chain or demand chain. Knowing for sure who is using what information is critical because these types of integration involve business-critical information exchange. Portals are used internally and externally as a way to aggregate information and applications into a single browser-accessible Web site. Users of portals must be authenticated to prove they are part of the group allowed access to the information. Service-oriented architecture is an approach more and more in favor as organizations try to leverage their information-processing assets maximally. SOA allows reuse of useful components and rapid construction of new applications. In SOA, messages move from point to point to point and need to maintain integrity and confidentiality all throughout their journey.
To fulfill all the security requirements Web services will place on you, this chapter asked the question "What are the core concepts of security that you need to know?" The answer starts with cryptography, a branch of mathematics focused on keeping secrets. The crypto-algorithms used to make messages secret are called encryption. The key to keeping secrets is in the keys to these algorithms. In shared key encryption, both sender and receiver share the same key for encryption and decryption of the message. In public key encryption, a matched pair of keys is used, one for encryption and its mate, and only its mate, for decryption. When you know what basic encryption is, the other critical concepts to understand and embrace are authentication (who is it?), authorization (what are they allowed to do?), integrity (is their message unaltered since they sent it?), confidentiality (was the message indecipherable by anyone intercepting it?), and non-repudiation (can you prove the message was indeed sent?).
Finally, this chapter introduced the Web services security basics that build on the security concepts just described. XML Signature provides integrity and non-repudiation for XML messages. XML Encryption provides confidentiality for XML messages. SAML assures the identity of a subject is made trustable and portable so that it can be attached to XML messages. WS-Security makes the entire SOAP system secure. And associated with WS-Security are also a host of other standards that help address a variety of trust issues brought on by Web services.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.
SOAP used to stand for Simple Object Access Protocol, but in the W3C SOAP 1.2 specification, SOAP is now just a name and is no longer an acronym. The reason for the change is that the W3C realized that SOAP is neither especially simple, nor is it related to objects in any way.
Most authors consider the base set of Web services standards to include UDDI as well as SOAP and WSDL. UDDI stands for Universal Description, Discovery, and Integration. Advertising Web services so that systems can automatically discover them sounds like a good idea, but we don't believe it is practical for the public Internet. Instead, we view UDDI as a powerful mechanism to be used inside larger organizations to promote reuse of shared services. So, although we do view it as a useful standard, we don't view it as part of the core set of things that define Web services.
In an SOA, UDDI will have a strong, meaningful role.
Recommended text on cryptography: Applied Cryptography by Bruce Schneier (John Wiley & Sons, 1996).
5. The terms shared key, secret key, and symmetric key are used interchangeably in various texts. To be consistent in this book, we choose to use the term shared key throughout, but occasionally context requires we also use the term symmetric key.
"Almost unique" because, like door locks, there is not an absolute certainty that two keys are unique. But the chances of two keys being the same is infinitesimally small, just as is the chance that your key will happen to open a neighbor's door lock.
On the Web, for example, message integrity is not required and not possible. You request HTML documents from Web sites and assume you are getting what was sent; because the risks of a bit or a word or even the entire document having been modified is low, you don't worry about message integrity. When the message is a patient record, a purchase order, or a contract, as you expect Web services to carry, you care a lot about integrity.
This chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.


text:
Art Brokerage: Steve Alan Kaufman: American Artist: On February 12, 2010, the world lost Steve Alan Kaufman, one of the greatest American pop artists and a generous humanitarian. Steve Kaufman, former assistant to Andy Warhol, passed away at the young age of 49. His memory, as well as his paintings, will live on forever. From his warm smile and generous heart, to his ability to tell a great story and his incredible knack of making every day an adventure filled with humor, drama, and laughter - Steve Kaufman was a legend. His paintings have found their way into the homes and hearts of so many, capturing the true American pop art experience. Steve Kaufman painted such timeless pieces such as: Coca Cola, Marilyn Monroe, Mozart, Beethoven, Wizard of Oz, Muhammad Ali, his money series, and his paintings of famous singers, actors and icons. His audience is vast and large, and his contribution to society was enormous. Steve Kaufman launched and operated the "Give Kids a Break Fund," a successful charity which helped inner city kids from troubled homes or straight from jail. Steve Kaufman gave these kids a job and his trust when no one else would, allowing them opportunities that they would have never had. Steve Kaufman lived for forty nine years, and in that time, he lived the life of 10 men. He will be so painfully missed, but his art will live forever. Steve Kaufman's paintings have been exhibited in many museums including The Andy Warhol Museum of Modern Art in Slovakia; the Reiss-Engelhorn Museum in Mannheim, Germany; The Museum of Contemporary Art in Hot Springs, AR; The Motown Historical Museum in Detroit, MI; the Blues & Legends Hall of Fame Museum in Memphis,TN; The American Sport Art Museum & Archives in Daphne, AL; The Pop Culture Gallery at The World of Coca-Cola in Atlanta, GA; Sala U. Veruda, Palazzo Costanzi in Trieste, Italy; The Palazzo Guiscardo in Pietrasanta, Italy; Museum of Passion in Valladolid, Spain; Marcos Valcarcel Cultural Center in Galicia, Spain and running from November 21, 2013 through May 6, 2014 a grand exhibition in the House of Enzo Ferrari Museum in Modena, Italy. Steve Kaufman's paintings are also in two presidential libraries. Listings wanted.
Original Painting
Unique Oil on Screenprint on Canvas
Original Painting
Unique Hand Painted Oil And Silkscreen on Canvas
Original Painting
Hand Painted Oil And Silkscreen on Canvas
Original Painting
Acrylic Unique Work
Original Painting
Oil on Canvas
Andy Warhol
Sunday B. Morning
Keith Haring
Mel Smothers
Peter Max
Simon Bull
Russell Young
Daniel Authouart
Vik Muniz
Ronnie Cutrone
James F. Gill
Bob Kane
Charles Fazzino
James Rizzi
Dan Rizzie
Linnea Pergola
John Van Hamersveld
Mr. Brainwash
Crash (John Matos)
Mark Kostabi
Ronnie Wood (Rolling Stones)
Scott Jacobs
Frederick Prescott
Sebastian Kruger
Jean Michel Basquiat
Kenny Scharf
Jack Dowd
Pietro Psaier
Doug London
Alexander Chen
Toby Bluth
Marc Ferrero
Mario Sanchez
Francesco Scavullo
Michael Kalish
Denny Dent
David Garibaldi
Tom Everhart
Hiro Yamagata
Neil J. Farkas
Allan McCollum
James Talmadge
Steven Gagnon
Steve Penley
Marjorie Strider
Li Shan
Gregory Siff
Sid Maurer
John Stango
Charles Lutz
Adam Licsko
Ashley Longshore
David Banegas
Ron English
Byron Galvez

subset: commoncrawl


text:
Mitch Gold tried to steal its name. Seven states banned it. One state even seized its bank accounts.
Yet the American Deputy Sheriffs' Association endures.
For more than a decade the Monroe, La., group has been raising upward of $4 million a year, promising to provide bulletproof vests to deputies and benefits to their families.
Most of the money has gone to telemarketers like Gold and former Gold associates Brian Wright and Duane Kolve.
In 2004 the group spent $49,357, less than a penny on the dollar, on benefits, records show.
State and federal regulators usually direct their legal muscle at fundraisers, treating charities as innocent victims. Not the deputies group.
Iowa's attorney general, for example, alleged in a November 2004 lawsuit that the deputies' association "exists primarily to rent its worthy-sounding name to telemarketing operations."
California, which has not sued the group, is its biggest source of funds. Between August 2004 and May 2005, according to an incomplete tally provided by the charity, Californians gave $1.2 million.
The group said it provided benefits to sheriffs in three rural California counties.
But only one of those counties – Trinity, population 13,000 – actually got four bulletproof vests as promised. The Mono and Plumas sheriff's departments said they got nothing.
" We applied, but we never heard from them again," Mono County Sheriff Dan Paranick said.
Asked about the discrepancy, secretary-treasurer Lee Warner said the group's board had voted to provide benefits to all three counties. But it couldn't write checks after a court-appointed conservator in Ohio seized its funds.
Tom Buchman, a former Gold subcontractor who now supervises the group's telemarketing, says the group delivers benefits when requested. He blamed Gold for poisoning state regulators against the group.
" I am so fed up with defending myself from Mitch Gold," Buchman said. "He haunts me."
Contact the writer: (714) 796-5030 or firstname.lastname@example.com


text:
Website | Twitter | Facebook | Womanthology
Wow, that's amazing....
Wow, that's amazing....
I'm with Base. Wow.
Very very beautyful. Congrats!
Gorgeous. Doing a new Amethyst has been a dream of mine, too. She was one of the big inspirations behind my webcomic.
Thank you for sharing!
These are beautiful, I don't know if you considered it but DC has been having some issues with their PR when it comes to female creative teams. You should try pushing this to them now while the door is still open.
Oh! These are wonderful. I would definitely pick this up. I have the whole original run (plus the Annual), and would like to see a re-imagining (if you have any ideas for an Angel Love re-imaging Love to see those as well).


text:
New Oxford American Dictionary has announced the verb "unfriend" as its word of the year, confirming the social networking term's ubiquity.
The definition: "To remove someone as a 'friend' on a social networking site such as Facebook."
On its blog, Oxford University Press quotes Senior Lexicographer Christine Lindberg as saying: "It has both currency and potential longevity. In the online social networking context, its meaning is understood, so its adoption as a modern verb form makes this an interesting choice for Word of the Year. Most 'un-' prefixed words are adjectives (unacceptable, unpleasant), and there are certainly some familiar 'un-' verbs (uncap, unpack), but 'unfriend' is different from the norm. It assumes a verb sense of 'friend' that is really not used (at least not since maybe the 17th century!). Unfriend has real lex-appeal."
Other techie terms that were considered: hashtag, intexticated, netbook, paywall and sexting.
Oxford didn't ignore Twitter either, citing a notable word cluster including Twitt, Tweeple and other Twitterish terms.
Last year's Word of the Year: "hypermiling," which involves "maximising gas mileage by making fuel conserving adjustments to one's car and one's driving techniques."


text:
After a two week vacation from WoW, I decided to reinstall. Yeah, I'm an addict. Still, taking a break from WoW every once in a while is a good thing. So let me post with some thoughts on Tier 3.
There is a schism in the paladin and raiding community. On one side you have restrictive guilds, who believe that paladins should just stay back and heal. On the other side you have free guilds who believe that paladins should melee and heal. And because the stakes are so low, both sides regard the other as heretics.
(Personal bias: I am firmly in the 'melee and heal' camp.)
The problem with Tier 3 is that it is a clear sign that Blizzard thinks the restrictive guilds are correct.
Of course, the counter-argument is that Blizzard just made a healadin set, like Avenger was a Retribution set. However, I don't think that people really see the Tier sets in that manner. To my mind, Tier sets are your default upgrade path as you progress through the endgame. A warrior replaces her Might armor with Wrath. She will replace Wrath with Dreadnaught. A similar progression happens with the other classes, and should happen with paladins. Redemption should replace Judgement which replaced Lawbringer.
Judgement is the perfect 'base' armor for paladins. It's not the best healing armor, it's not the best damage armor, but it's a solid base set. A hybrid set for a hybrid class. There have always been healing pieces (Peacekeeper, for example) and damage pieces (Legguards of the Fallen Crusader), but the Tier set functions as a solid base.
If Redemption had been an extra set in Naxx, it would have been great. I have extra pure healing gear, just like every other paladin. But for Redemption to be the base, the 'default' set, is an argument that almost totally destroys the 'melee and heal' side of the paladin schism.


text:
(From left) Deborah Brown, Sarah Schmerler, and Gwendolyn Skaggs © Photo by Allen Ying
Sarah Schmerler, guest curator of Norte Maar's first show of this year, published a piece in the February issue of the Williamsburg Greenpoint News+Arts. In "3 Ladies of Chill Repute," Schmerler proposed a 'round robin series of interviews and gallery visits' and invited Deborah Brown of StorefrontBushwick and Gwendolyn Skaggs of Sugar to visit and discuss each respective space's current shows, including her own show Gʉilty / (NOT) Guilty, which recently closed at Norte Maar. Asked by Skaggs who her influences are Schmerler states, "I've been very influenced by the radical art historian Aby Warburg, who died in 1929 (Luis Perez-Oramas of MoMA turned me on to him). Also by Hudson, of Feature Gallery, who makes idiosyncratic yet totally trackable decisions in what he chooses to hang."
To see the article in it's entirety click here.


text:
For more information please contact us
Port de Plaisance
Beaulieu sur Mer
Thank You
Your form has been submitted successfully. A representative will be in touch shortly
Request cannot be completed
You may have entered incorrect information or server is temporarily down. Please reload this page and try again later.


text:
The ultimate choice together with the initially cost-free throw developed 1 within the most well-known moments. Antonina Bengka FIFA 18 Coins for his Czechoslovakia in West Germany blocked the victory, the Germans in this way although within the important game the sole failure. They may be also certainly one of your couple of possibilities for the goalkeeper, in my quite own consideration, a single of the underrated members of the football workforce.
The thrill of playing FIFA 18 is certainly something that's unlike anything else. While playing, you can enjoy rivalry against people from all corners of the world. Best of all, you can set your own custom team and compete against others to become the top FIFA 18 player on the planet. But in order to get a great team going, you will have to acquire plenty of FIFA 18 coins. You Will Need to get coins through a variety of places so as to succeed: Start by competing in several of events in the FIFA 18 world class. These include various challenges between your team. A few of those challenges are intended to be timed together with the specific events that are happening in the soccer world.
Regardless of where you happen NBA 2K MT Coins to be playing the game you are going to possess a wonderful time! Find out to become better than other individuals at gaming by reading extra about it. If Giggs chose to NBA Live Coins retire after the season, then it will be the last miracle he left to Manchester United. Wilson shines dream theater new version of Owen turned out yesterday morning, the Premier League 34 rounds of a match within the old Trafford stadium fight, Manchester United residence 3-1 win Hull City. It really is worth mentioning that the teenager Wilson scored twice shine the audience.
It really is correct that FIFA 18 consists of a lot of strange moments that definitely make you think about it. FIFA subreddit and EA's personal forums are full of FIFA 18 clips and may Goldofu not be thought like that really should be performed like a player.
Commit Madden Mobile coins on acquiring distinct packs
There are some possibilities for obtaining new content with on line games. You may buy it with money, operate for it, or earn rewards to pay for it. Appear more than all the advantages that happen to be being provided before you make a purchase. Bought products can enhance your level of playing and make the expertise a lot more rewarding. But they could also save time. Be sure to realize the content and safety settings of one's gaming consoles. You'll be able to frequently use them to ensure children never see items they shouldn't. One of the most advanced systems will even provide you with the choice to customize the settings for every user like a computer system would.


text:
|International Space Station Imagery
high res (0.6 M) low res (68 K)
|JSC2004-E-35556 (August 2004) --- This artist's rendering depicts the port side of the International Space Station following activities of August 14, 2004. The resupply vehicle Progress 15 docks to the aft end of the Zvezda Service Module. Soyuz 8 is docked to the FGB Zarya's nadir port.
Curator: JSC PAO Web Team | Responsible NASA Official: Amiko Kauderer | Updated: 11/19/2012


text:
Product Categories
Contact Us
Shenzhen Grit Technology Co.,Ltd
Add:RM.1106, A8 Alive Bldg.,No. 1002, Keyuan Rd., Nanshan Dist. Shenzhen City
Con:Jason Zhang
robotic cleaner Side BrushSide Brush makes Yubot robot cleaner the best cleaning performance. With the side brush, Yubot is much easier to clean the wall side and corners.Read More
Auto robot cleaner Door MagnetDoor magnet is an important accessory of Yubot. Once the door is open, the door magnet will connect Yubot robot cleaner via wireless module, and Yubot will send short message to the smart phone.Read More
robot vacuum cleaner Lithium Ion BatteryThe battery of Yubot vacuum cleaner is Lithium Ion Battery with the capacity 2200mAh. The charging time is about 3-4 hours, the cleaning time is about 2 hours, and the video call time is about 4 hours.Read More
Privacy Security Camera CleanerYubot Privacy Security Camera Robot Cleaner with APP Wi-Fi remote control and no server storage & cloud transfer.Read More
Smart Home Security Robot CleanerYubot Smart Home Security Robot Cleaner is a loyal guard to monitor and protect your family when you are not at home.Read More
home security robot vacuum cleaner Virtual WallVirtual Wall is also called Space Isolator.It uses an invisible infrared signal to protect Yubot while it is cleaning. When a room cleaning is finished, it directs Yubot to clean the next room.Read More
Camera robot cleaner Docking StationPlease put the docking station on the flat floor and behind the wall, no obstacle or hollow areas 3mm away from the charging station in the front and 0.5m on the right and left.Read More
APP Controlled Robot CleanerYubot APP Controlled Robot Cleaner is a latest robot cleaner that can be controlled via huiba APP.Read More
Smart Video Robot Cleaner with mobile app controlYubot (YB-R162) Smart Video Robot Cleaner: Give you a real-time video call with your family.Read More
Auto Update Camera Robot CleanerYubot Auto Update Camera Robot Cleaner is a top sale Robot as its auto-updating APP system.Read More


text:
Vol. LXV, No. 24
Wednesday, June 15, 2011
Rigolot-Severson. Stephanie Rigolot, daughter of Carol and Francois Rigolot of Princeton, to Scott Severson, son of Nancy and Richard Severson of Scottsdale, Ariz. The wedding took place at the Hermosa Inn in Scottsdale, Ariz. On May 7, 2011.
The bride, 32, is a graduate of both Princeton High School and Princeton University. She received her masters degree in architecture from UCLA. She is in the marketing department of Cushman & Wakefield, after working for Michael Graves & Associates and for Morphosis Architects, where she was part of the design team for the Phare Tower in Paris.
Mr. Severson, 32, graduated from the University of Colorado-Boulder and received a masters degree in architecture from UCLA. He works for Morphosis Architects in Los Angeles, Calif.
OHara-Hall. Aisling Catherine OHara, the daughter of Mary and Henry Thomas OHara, of County Cavan, Ireland, to Turney Hall, the son of Colleen Coffee Hall and Robert Turnbull Hall III, of Princeton. The couple was married on May 7 at Trinity Church, Princeton. The Rev. Paul Jeanes, an Episcopal priest, performed the ceremony, with Father Pat Connor, a Catholic priest, taking part.
The bride, 33, is a Ph.D. candidate in immunology at the University of Pennsylvania. She graduated from Allegheny College and received a masters degree in biotechnology from Johns Hopkins University.
The bridegroom, 33, works for the New Jersey Office of Administrative Law, a state government agency. He graduated from Washington and Lee University and received a J.D. from Rutgers University.
The couple lives in Philadelphia.
Carnevale-Papafilipakis. Nicolina Renée Carnevale, daughter of Mr. and Mrs. Nicholas R. Carnevale of Princeton, to Stavros Vasillias Papafilipakis, son of Mr. and Mrs. Konstandinos (Gus) Papafilipakis of Chania, Crete, Greece.
The bride-to-be is a graduate of Villa Victoria Academy High School and Moravian College. She received her teaching certification from The College of New Jersey, and is currently a teacher at Dietrich Johnson School, Princeton.
The future groom graduated from Lawrence High School and attended Mercer County Community College, and received a Culinary Arts Degree. He is employed by the State of New Jersey, Division of Revenue, and is currently pursuing a career in law enforcement.
An August 2011 wedding is planned.
Town Topics® may be purchased on Wednesday mornings at the following locations: Princeton McCaffreys, Coxs, Kiosk (Palmer Square), Krauszers (State Road), Olives, Speedy Mart (State Road), Wawa (University Place); Hopewell Village Express; Rocky Hill Wawa (Route 518); Pennington Pennington Market.
Copyright© Town Topics®, Inc. 2011.
Contact Us | Masthead | Advertise | Submit | Last Week | Back Issues


text:
autoblog needed a new logo design and created a contest on 99designs.
A winner was selected from 27 designs submitted by 7 freelance designers.
We need a design for a simple and clean new logo. The subject is a website about women and cars.
Carwoman.nl is a Dutch website where a female car-journalist writes about her life and the cars she drives. The header of the site is often changing with pictures, but we need a logo so people can recognize that.
- A symbol (logo)
- No tagline, just the logo and the url ("carwoman.nl")
- A picture of a blond woman in a convertible, with her hair in the wind; if possible... (other designs are welcome)
- Pink stuff
Find out how a design contest works or learn more about our logo design services.


text:
Tuesday, March 01, 2011
Estonian Soda Bread Recipe
If you think you've already seen a recipe for Estonian soda bread here @ Nami-Nami, then you're not mistaken - I indeed blogged about it some three years ago. However, that recipe was with ricotta/curd cheese, and this one uses kefir or cultured buttermilk. There isn't such a huge taste difference - and they're both quick to make and delicious to eat. Caraway seeds are a traditional flavouring, but if you're not keen on that spice, you can leave it out.
It's best served warm - I usually devour it with some butter and honey (see photo above) or lingonberry jam.
The original recipe is from an Estonian cult baking book, Ida Savi's "Saiad, pirukad, koogid" (1989). I haven't changed it, really, as if it ain't broke, don't fix it :)
Estonian Soda Bread
a 23x23 cm square tin, buttered
250 ml cultured buttermilk, kefir or fermented milk (1 cup)
1 large egg
1 tsp salt
1 tsp caster sugar
2 Tbsp vegetable oil or melted butter
1 tsp caraway seeds
175 g barley flour (about 300 ml, I used wholemeal)
90 g wheat flour (150 ml)
1 tsp baking soda
Pre-heat the oven to 200 C/400 F.
Sift both flours and soda into a bowl.
Whisk the egg with salt and sugar, add the kefir, oil/melted butter, caraway seeds and the flour mix. Stir until just combined.
Pour into a buttered tin and bake in a pre-heated oven for 20-25 minutes, until the soda bread is golden brown on top.
14 comments:
- Su said...
This bread looks just wonderfull.
- 10:49 am, March 01, 2011
This sounds very nice. I made the oat soda bread from 101cookbooks the other day and devoured it. This one with barley and caraway seeds is right up my alley. Besides, since falling in love with kama (which you kindly sent me), I am always keen to try your estonian recipes :-) Thanks for sharing!
- 11:01 am, March 01, 2011
- Mari-Liis said...
Nii ilus karaski pilt!
Ma teen vanaema kaustikusse eiteakust kirjutatud retsepti järgi, kus on väga lühike koostisainete loetelu:), ei ole ei muna ega nisujahu. Minust on saanud tõeline karaskifänn, uskumatult lihtne küpsetada ja maitse on nii hea ja kodune.
- 11:19 am, March 01, 2011
- Saee Koranne-Khandekar said...
Lovely recipe! I haven't tried a soda bread yet and this one's probably going to be where I start! Look at that melting butter!
- 11:58 am, March 01, 2011
- maxivida said...
I made the Irish soda bread last year and it was delicious, but I have to say the Estonian variety looks much nicer and sounds more interesting. I love caraway seeds! :)
- 1:41 pm, March 01, 2011
- Sabrine d'Aubergine said...
I make many types of soda bread: I'll try this too!
- 3:53 pm, March 01, 2011
- Guilherme said...
Muito interessante esse pão. So muito interessado em comida e culturas diversase esse pão é muito diferente do que já fiz.
certamente farei.
- 3:57 am, March 02, 2011
- Gitte said...
Simply just love bread made with buttermilk and you're so right "if it aint broke don't fix it". Looks wonderful.
- 11:17 am, March 03, 2011
I made the bread today - it's very nice :-)
- 7:11 pm, March 03, 2011
- Nezumi said...
I love Irish soda bread but have never tried Estonian soda bread, thank you for posting this recipe I will be adding it to my "to bake" list.
- 12:44 pm, March 13, 2011
- Pille said...
Su, Guilherme, Gitte - thank you!
Agnes - so pleased to hear about kama and that you love the soda bread!
Mari-Liis - no mul on klassikaline Ida Savi retsept, ei hakka muutma. Vanaema retsept on muidugi veelgi põnevam :)
Saee - I love the butter-honey thing as well!
Maxivida - lots of people are very suspicious about caraway seeds - glad to hear you're not one of them..
Sabrine & Nezumi - please do!
- 9:19 am, March 16, 2011
This looks very interesting and as I happen to have some barley flour I want to try this - but I also wanted to remind you that you promised to post your recipe for naturally leavened rye bread back in 2009, and many of us have been patiently waiting!
- 1:57 pm, March 23, 2011
I had an "Estonian" dinner party for my daughter and her fiance and his family on Sunday and made two of your recipes - the Smoked Cheese & courgette soup (huge hit!) and the barley soda bread, which received a mixed reaction, but was all eaten.
- 8:26 am, March 30, 2011
- Simona said...
I made this yesterday, using my homemade kefir and local barley flour and it was really really good. In fact, it is almost gone. I will make it soon and the write about it. With a group of bloggers we are doing a virtual tour of the EU and we are now visiting your country.
- 5:49 pm, November 04, 2013


text:
Instant Parcel or Pallet delivery rates
- UK parcel delivery
- International delivery
- Pallet delivery
- Import back to the UK
- Same day courier
- Business enquiries
Your goods must be on a pallet, wrapped and stable for lift (?)
Same Day Service
If you have a parcel, pallet or document you need to ship in a hurry within the UK, get an instant quote right here for a Same Day collection and delivery.
P4D POST is only available from our Banbury office. Book online and drop it into us, from £1.50 per item.


text:
Employment Specifications for Grant/Contract Funded Positions
8220.1 Required Information about Funding and Contracts
All personnel requests, position announcements, contracts, and salary notices for positions funded by grants or contracts for faculty and staff must specify that the position is dependent on funding from non-university sources and that continued employment is contingent on that grant or contract. All contract personnel will be employed on special contracts, and faculty on such contracts will not be eligible for tenure.
8220.2 Documentation and Certification of Funds
The requisitioner is responsible for placing a statement regarding the nature of the funding and contract (8220.1) on the appropriate documents and for specifying the grant/contract number or the source of special funding. The Department of Human Resources will check to make certain that such a statement appears and will return the document to the requisitioner if it does not. The Office of Research and Sponsored Programs will certify that the funds are available before any position is posted.
8220.3 Discussion with a Prospective Employee
In discussions with any prospective employee hired under a grant or contract, the employer (grant director) should make it clear, both verbally and by the written notation on the contract or salary notice, that the individual will be employed by the university only so long as grant or contract funds are available.
8220.4 Personnel Regulations
Even though a position may be funded by a grant, the employee will be subject to all Wright State University personnel regulations. Supervisors must give the usual notice before the employee is terminated, and vacation time is expected to be taken before the end of the contract period.
8220.5 Exception for University Employee on Continuing Status
This policy does not apply to a previously hired university employee on continuing status who subsequently may be funded by a grant or contract for all or part of his/her time.


text:
Team Honda Muscle Milk To Fly Red, White and Blue Colors at Red Bud
Torrance, CA: For the next round of the 2013 Lucas Oil AMA Pro Motocross championship taking place in Michigan, Team Honda Muscle Milk will showcase its bikes and riders in patriotic-themed Red, White and Blue designs to celebrate the Fourth of July holiday weekend. Round seven of the 2013 Lucas Oil AMA Pro Motocross championship will mark the 39th annual Red Bud National in Buchanan, MI, and the team CRF450R race bikes will feature Red, White and Blue graphics and seat cover designed by Throttle Jockey, along with blue D.I.D wheels. In addition, Justin Barcia and Trey Canard will both don patriotic-themed riding gear for the holiday weekend.
"What better way to celebrate our country's birthday than with special graphics on our race bike?" said American Honda's Manager of Motorcycle Sports, Gary Martini. "Red Bud has a rich tradition with motocross fans throughout the entire country. Like our original Red, White and Blue team jerseys we first wore 40 years ago, the design was inspired by the colors of our nation's flag."
About Honda: American Honda Motor Co., Inc. was established in 1959 and is the sole distributor of Honda motorcycles, scooters, ATVs and side-by-sides in the U.S. The American Honda Motorcycle Division is responsible for the sales, marketing, and operational activities for these products through authorized Honda dealers. For more information on Honda products, go to www.powersports.honda.com.
About Muscle Milk: Muscle Milk® Ready-to-Drink is a protein-enhanced functional beverage that promotes workout recovery, lean muscle growth, and sustained energy. Muscle Milk takes the guesswork out of high performance nutrition, delivering a precise blend of premium proteins, complex carbohydrates, functional fats, vitamins & minerals. CytoSport™, the maker of Muscle Milk®, is among the largest sport nutrition protein beverage companies in the U.S. and offers a complete line of protein-enhanced powders, shakes and bars. Muscle Milk® was named Ready-to-Drink Beverage of the Year by bodybuilding.com, Best Functional Beverage and Beverage of the Year by BevNet and Company of the Year by Beverage Forum presented by Beverage Marketing Corporation and Beverage World.


text:
Click on the headline for a sample of the features only in the Dec. 27 print edition of the Middletown Transcript, now on sale in stores throughout the M.O.T. area.
The Dec. 27 issue of the Middletown Transcript newspaper contains features only available in the print edition, including:
• Local soccer players visit U.S. Olympic training center, page 29A;
• This week in Delaware history, page 32A;
• 20 years ago from the Transcript archives, page 32A.


text:
To scale out or not to scale out, that is the question
Hi folks, Ned here again. If Shakespeare had run Windows, Hamlet would be a play about configuring failover clusters for storage. Today I discuss the Scale-Out File Server configuration and why general use file server clustered shares may still have a place in your environment. These two types of Windows file servers have different goals… Read more


text:
Golf Live Lines
More Live Lines / Wagering Channel / Bullz-Eye Home
Get in on all the links action with these PGA Live Lines, powered by Bodog!
You can follow us on Twitter and Facebook for content updates. Also, sign up for our email list for weekly updates and check us out on Google+ as well.


text:
Italian restaurant chain Olive Garden says, "When you're here, you're family," but in recent years, it's been more like a dysfunctional family, struggling with dipping sales and a mixed reputation, the Chicago Tribune reported.
The restaurant's parent company, Darden (also the owner of Red Lobster), acknowledged that they let Olive Garden get into a rut, but that they're expecting a comeback, according to the Tribune. With Olive Garden making up nearly half of the company's sales, they need it.
"To improve sales, Olive Garden will remodel restaurants and revamp the menu, adding lower-priced dishes," the Tribune said. "Its long-running ads with actors portraying perky families will get replaced, with an as-yet undisclosed new campaign."
Consumerist is cautiously hesitant, expecting perhaps more cheap gimmicks to come with the revamp of Olive Garden.
"One strategy will be to get rid of those ads with families that are just over the goshdarn moon to be lucky enough to eat at Olive Garden," the blog said. "No word on what kind of campaign will replace it, but let's hope it's not a couple of sassy galpals gabbing about love, loss, unlimited soup, salad and breadsticks, either."


text:
Email email@example.com. He has a great set up -- Hal 02/15/2018 1:08PM
Anybody have any experience using a satellite at your tailgate? -- HartwoodHokie 02/12/2018 1:03PM
A lower cost option: Get Google Chromecast and cast WatchESPN to your TV -- BazHokie 02/14/2018 2:14PM
Yes. If you plug the holes, it holds a helluva lot of queso dip. ** -- Dogbert 02/14/2018 2:01PM
Any advice for easiest/best method for Direct TV users? ** -- bghokie 02/13/2018 1:44PM
I have Dish Network -- HokiefromBedford 02/13/2018 10:30AM
Just started doing it this past season..... -- BleedinOandM 02/13/2018 06:55AM
You mind if I ask how much the pay as you go service costs? ** -- HartwoodHokie 02/13/2018 10:00AM
There are different packages that differ based on movie channels, etc.... -- BleedinOandM 02/13/2018 11:35AM
It's easy. My group has done it with a directv receiver in the past. -- vtbones 02/12/2018 9:09PM
You can watch the network games with an HDMI antenna ** -- Baltimore Hokie 02/12/2018 8:36PM
Just not the ones on ABC ** -- hoosnowahokie 02/13/2018 09:06AM
What do you mean, not the ones on ABC? ** -- Atlee Hokie 02/14/2018 1:34PM
The ABC antenna is between Roanoke and Bedford. Unless you have a super -- hoosnowahokie 02/14/2018 1:35PM
Valley Tribe has a Dish setup we use..can get you contacts... ** -- HOKIE75-79 02/12/2018 5:03PM
I'm probably not going to get one for this season but thinking future -- HartwoodHokie 02/12/2018 5:09PM
Well, you need to get to GEO, and Blacksburg isn't an ideal launch site. ** -- VT_Consul 02/12/2018 4:28PM
How about the DirecTV app streaming over unlimited data to HDMI output -- Boiler Hokie 02/12/2018 3:53PM
Are you expecting to have enough bandwidth at a VT football game? -- EDGEMAN 02/12/2018 5:03PM
Have you ever tried that? My througput always seems WAY too spotty -- GusDaMan 02/12/2018 4:10PM
Assuming you mean receiver and not the actual satellite..... -- 48zip 02/12/2018 1:40PM
I've currently got Directv but am contemplating a switch to dish ** -- HartwoodHokie 02/12/2018 2:02PM
Haven't done it personally, but... -- EDGEMAN 02/12/2018 1:35PM
I've seen some that are meant for RV's that are shaped like a dome -- HartwoodHokie 02/12/2018 1:37PM
Yeah, those are convenient. -- EDGEMAN 02/12/2018 2:14PM
Dish has something called a Playmaker -- hoolu 02/12/2018 1:13PM


text:
< Features
(→Release Notes)
|Line 19:
|Line 19:
* Targeted release: [[Releases/17 | Fedora 17 ]]
* Targeted release: [[Releases/17 | Fedora 17 ]]
* Last updated: 2011-02-07
* Last updated: 2011-02-07
* Percentage of completion:
* Percentage of completion: %
== Detailed Description ==
== Detailed Description ==
Revision as of 07:30, 27 March 2012
A new storage architecture for KVM based on SCSI.
- Name: Paolo Bonzini
- Email: firstname.lastname@example.com
Current status
- Targeted release: Fedora 17
- Last updated: 2011-02-07
- Percentage of completion: 100%
Detailed Description
virtio-scsi improves the storage stack in terms of scalability (easily overcomes the current limit of ~30 freely hot-pluggable/unpluggable storage devices), flexibility (support features such as SCSI passthrough or persistent reservations), extensibility (exposing new features to the guest does not require updating drivers in both the host and the guest).
Benefit to Fedora
Fedora users will be able to use an industry-standard storage stack for their virtual machines.
The guest driver will be included as part of the distribution's kernel and as part of the seabios ROMs installed together with QEMU. The host drivers will be included in the qemu package. Management tools based on libvirt should support this too.
How To Test
- Install the qemu-kvm package.
- Download an install image for this release of Fedora (network or DVD).
- Prepare a large file to be used as the disk for a Fedora virtual machine.
- Use the following command to install Fedora:
qemu-kvm -drive if=none,id=hd,file=/path/to/test.img -device virtio-scsi-pci,id=scsi --enable-kvm -device scsi-hd,drive=hd -cdrom /path/to/boot.iso.
- Reboot and test that the virtual machine can boot from the virtio-scsi hard disk.
- Use the following command to (re)install Fedora:
qemu-kvm -drive if=none,id=cd,file=/path/to/boot.iso -device scsi-cd,drive=cd,bootindex=0 -drive if=none,id=hd,file=/path/to/test.img -device virtio-scsi-pci,id=scsi --enable-kvm -device scsi-hd,drive=hd. The virtual machine will boot from the virtio-scsi image.
Contingency Plan
Each piece (kernel, qemu, libvirt) can be included separately, so there is no need to revert partial changes.
Documentation will be included as part of the changes to libvirt.
Release Notes
KVM and libvirt support a new advanced SCSI-based storage stack, virtio-scsi. Right now, virtio-scsi can be used on guests running Fedora 17. It should be included in the mainline kernel starting at release 3.4.


text:
REAL NAME: Mike and Todd Shane
Mike 6'4", Todd: 6'5, Both: 304 pounds
NICKNAMES: Chazz and Biff Wentworth, the Regulators, Gymini
When fitness guru Simon Dean threw out an open challenge on Smackdown recently, it wasn't meant for a one-on-on match, it was on behalf of Smackdown's newest tag team, the Gymini, who long-time watchers of the Florida indy scene know as the Shane Twins.
Former tennis players at Galesburg High School in Illinois, Mike and Todd Shane were trained by Dean Malenko and Eddie Sharkey and made their debuts in Florida in 1998. They remained in Florida for the early few years of their respective careers, wrestling for Independent Pro Wrestling and known as Chazz and Biff Wentworth. Between 1999 and 2001, they enjoyed three reigns as the Independent Pro Wrestling Tag Team Champions, winning a 1999 tournament (defeating Mike Marcello and Pepe Prado in the finals) and then defeating the teams of Buck Quartermaine on September 11, 1999 and Freedom Ryder and Rod Steele and Mark Zout on April 21st, 2001 to regain the titles.
On July 21, 2001, the Shane Twins would add another championship to their resume when they defeated the New Heavenly Bodies and the Market Crashers to win the vacant NWA Florida Tag Team titles. In addition to tag team gold, Mike and Todd would also win singles titles during their early careers: Mike would win the IPW Television title while Todd would later gain the NWA Florida Heavyweight Championships.
The Shane Twins would leave Florida in May 2002, to defeat the Hit Squad and win the Jersey All Pro Tag Team titles but they would return to their native Sunshine State three weeks later to begin a second reign as NWA Florida Tag Team Champions.
In early June 2002, Mike and Todd headed to Peru where they defeated the Heavenly Bodies (Casanova Chris & Vivacious Vito) and became the NWA World Tag Team Champions. By June 28th, the Shane Twins were the co-holders of three different tag team titles: the NWA World Tag Team Championships, the NWA Florida Tag Team titles and the Jersey All Pro Tag belts. After a successful title defence that night, they vacated the NWA World Tag Team titles.
A week earlier, Mike And Todd had debuted in NWA-TNA, as Rod and Richard Johnson. The Johnsons, managed by Mortimer Plumtree, defeated James Storm and Psichosis on the very first edition of NWA-TNA's pay-per-views. After a loss to America's Most Wanted two weeks later, the Johnsons turned on Plumtree and headed back to Florida and life as the Shane Twins.
They had retained their Florida Tag Team titles during their time in TNA, before losing the titles on October 11, 2002 and began a third title reign on February 8, 2003 when they regained the titles from Scoot Andrews and Mikey Tenderfoot, a victory that also netted them another run as IPW Tag Team Champions. The Shane Twins would retain the Florida Tag Team titles at the 2003 Jeff Peterson Memorial Cup, with a win over Danny Doring and Steve Corino but lost the titles to the Vandalz on June 14th, before heading to Japan.
Mike and Todd Shane spent most of the summer of 2003 in Japan, wrestling for World Japan Wrestling and defeated no less than the Road Warriors before returning to Florida in August and quickly regaining the NWA Florida Tag Team titles, in mid-August, and enjoyed a lengthy title reign.
In December 2003, the Shane Twins worked a dark match against the Hurricane and Rosey during a WWE match taped for Heat.
On March 20th, Todd Shane won the NWA Florida Heavyweight Championship, a title he would retain until losing to Steve Madison on September 4th. Todd and Mike reunited in late 2004 and continued to team in NWA Florida until the beginning of 2005.
It was then, after working a dark match during a January 2005 Tampa, Florida Smackdown taping (in which they defeated Shannon Moore and Steve Madison) that Todd and Mike Shane were signed to a three-year developmental deal with WWE.
The Shane Twins split time between Ohio Valley and working dark matches for WWE until September, when they were assigned to Deep South Wrestling. Known as the Regulators, Mike and Todd remained in Deep South Wrestling for the rest of 2005, wrestling tag matches almost exclusively. And as 2005 turned to 2006, the Shane Twins were brought up to WWE full-time.
Introduced by Simon Dean who looks to be their manager, the Shane Twins became Gymini, and destroyed Paul London and Brian Kendrick on the first Smackdown of 2006. Two weeks later, Gymini picked up a win over London and Kendrick.
However, Gymini didn't find much success on Smackdown, making only a few appearances on the show, being regulated to Velocity and returning to Deep South Wrestling to feud with Freakin' Deacon and Bill Demott.
--- compiled by John M. Milner


text:
Rays, Ripken join to buy FSL team
Tampa Bay affiliate to play in Port Charlotte in 2009
By Brittany Ghiroli / MLB.com | August 27, 2008 3:49 PM
"Florida is a baseball hotbed and we have been anxious to have a base of operations here for some time," Cal Ripken, president and CEO of Ripken Baseball, said. "When the opportunity to partner with the Rays presented itself, we jumped at it."
Although Ripken acknowledged that Minor League Baseball is about selling a family product, the former Major Leaguer was equally optimistic in creating a successful team.
"It's awfully great when you have good players, good prospects you can sell," Ripken said. "We're not in for the short term. We're in it for the long term, so we're looking forward to that."
Ripken said he serve an active and visible part in the new team and Ripken Baseball has hired Joe Hart as the team's general manager. Hart formerly was GM of the Nashville Sounds, the Triple-A affiliate of the Milwaukee Brewers in the Pacific Coast League.
Full-season seat packages (70 games) start at $285 and the team is taking deposits for seating now. Those interested should call (866) 272-9789. Single-game pricing as well as smaller ticket plans will be announced at a later time.
"We are thrilled to be partnering with Cal Ripken and Ripken Baseball on this unique venture," Rays president Matt Silverman said. "Ripken Baseball is an established and proven Minor League operator and the Ripken name is synonymous with success."
Prior to Wednesday's Rays game, Ripken was equally impressed with the success of the Major League club.
"I think it's marvelous," Ripken, who threw out a ceremonial first pitch, said of the Rays' success. "There's a lot of energy. They're the talk of the nation."
Brittany Ghiroli is an associate reporter for MLB.com. This story was not subject to the approval of the National Association of Professional Baseball Leagues or its clubs.View More


text:
Performance when you need it
Think of your PC as a race car with a powerful turbocharger sitting under the hood. You're driving along at a casual pace when the urge to speed up grips you, so you flip the switch to "turbo," and – in an instant – your engine's full capacity kicks in and rockets you down the road. This is your PC with AMD Turbo Core technology under the hood.* Just as a turbocharger increases torque and power output, AMD Turbo Core technology can provide more performance when you need it from your AMD APU.
Dynamically adjusts performance
AMD Turbo Core technology dynamically adjusts to give you a performance boost just when the operating system requests the highest processor performance. If a core is operating below maximum limits and your workload demands additional performance, the processor frequency will dynamically increase until the upper limit of frequency is reached. As your workload subsides, the core returns to normal frequency. This gives you optimized application performance within the thermal and power limits of your APU.
Your PC is already equipped
Unlike the nitrous oxide tank in a race car, AMD Turbo Core technology doesn't require extra add-ons – many AMD APU-powered PCs come fully equipped with it.*
Maximize your performance now
There are technologies on the horizon such as HSA that promise to maximize the processing capacity of your AMD APU, but, for the moment, there are relatively few applications that take full advantage of multicore processors. With AMD Turbo Core technology, you don't have to wait for new technological advancements to make it down the pipeline – you can get incredible performance out of your AMD APU now.
*Additional hardware (e.g. HD or 4K monitor, USB, 3.0 ports, wirelessly enabled HDTV) and/or software (e.g. multimedia applications and/or Wi-Fi access) are required for the full enablement of some features. HD/4K Video display requires an HD/4K video source. Not all features may be supported on all components or systems - check with your component or system manufacturer for specific model capabilities and supported technologies.
*For more information on AMD features and software go to amd.com/featuredetails.