<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title><![CDATA[ProExe]]></title>
<link><![CDATA[https://resourceit.co.uk/support/]]></link>
<description />
<generator><![CDATA[Kayako Fusion v4.50.1636]]></generator>
<item>
<title><![CDATA[How quickly can I obtain a SSL certificate?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/80]]></link>
<guid isPermaLink="false"><![CDATA[f033ab37c30201f73f142449d037028d]]></guid>
<pubDate><![CDATA[Sat, 06 May 2006 12:25:41 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[ProExe, are able to obtain and install your SSL certificate within 36 hours. ]]></description>
<content:encoded><![CDATA[ProExe, are able to obtain and install your SSL certificate within <strong>36 hours</strong>. ]]></content:encoded>
</item>
<item>
<title><![CDATA[What is an SSL Certificate?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/39]]></link>
<guid isPermaLink="false"><![CDATA[d67d8ab4f4c10bf22aa353e27879133c]]></guid>
<pubDate><![CDATA[Thu, 04 May 2006 14:25:49 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[SSL stands for Secure Socket Layer and is noticed when you visit a website that begins with https://. The &quot;s&quot; in https:// means the site is secure - that is, the connection between your computer and the website server is encrypted.With SSL certi...]]></description>
<content:encoded><![CDATA[<p>SSL stands for Secure Socket Layer and is noticed when you visit a website that begins with https://. The &quot;s&quot; in https:// means the site is secure - that is, the connection between your computer and the website server is encrypted.</p><p>With SSL certificates you can start conducting secure online transactions with confidence, quickly and cost-effectively. All of our SSL certificates enable up to 256-bit encryption and can be used to secure servers used for Web sites, intranets, extranets and other online applications. </p><p>An SSL Certificate can be thought of as a digital piece of paper that states who the SSL connection is being made with and some kind of &quot;Certificate Authority (CA),&quot; which is a third party that verifies the certificate information is accurate. </p><p>SSL Certificates can be self-signed or signed by a CA. If you self-sign a certificate, it will not be trusted by any web browsers or other SSL clients. That is because the entity who generated the certificate signed it themselves and basically said &quot;this information is accurate, trust us!&quot; This will result in a warning in your web browser or SSL client, but the SSL connection will still be created and will still be encrypted. For all intensive purposes, a self-signed certificate is just as good for encryption as a CA-signed one.  </p><p>A certificate that is signed by a CA is usually trusted by most, if not all, web browsers and SSL clients. This is because the SSL clients are preprogrammed to accept certificates provided by entities who have proven their trust (such as Verisign, Thawte, and GeoTrust, the top three CAs). Certificates provided by these CAs will not result in a warning in your web browser or SSL client and looks more professional. </p><p>The certificates are also verified against the domain and company the certificate was issued to. Therefore, if the SSL certificate of the new website you're trying to purchase a book from was issued by Verisign, you can feel confident that the company does exist and the domain belongs to that company. </p>]]></content:encoded>
</item>
<item>
<title><![CDATA[What is SSL?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/41]]></link>
<guid isPermaLink="false"><![CDATA[3416a75f4cea9109507cacd8e2f2aefc]]></guid>
<pubDate><![CDATA[Thu, 04 May 2006 14:31:22 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[SSL stands for Secure Socket Layer. It is an mechanism to transfer information securely across the Internet. SSL will enable your customer's browser to connect to your web site and transparently negotiate a secure communication channel. Once this connecti...]]></description>
<content:encoded><![CDATA[<p>SSL stands for Secure Socket Layer. It is an mechanism to transfer information securely across the Internet. SSL will enable your customer's browser to connect to your web site and transparently negotiate a secure communication channel. Once this connection has been made, information, like credit card numbers, can be exchanged securely.  </p><p>Please note that SSL does not include software to process credit card transactions. Although you can securely receive credit card information through SSL, actual processing of the credit card will require a &quot;Merchant Account&quot; from an accredited financial institution. </p>]]></content:encoded>
</item>
<item>
<title><![CDATA[What is the different between shared SSL and regular SSL?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/40]]></link>
<guid isPermaLink="false"><![CDATA[d645920e395fedad7bbbed0eca3fe2e0]]></guid>
<pubDate><![CDATA[Thu, 04 May 2006 14:29:02 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[Shared SSL means you use your Hosting Provider's SSL Certificate. This will usually result in something like https://yourname.example.com. The benefits are that they are generally free or inexpensive to use and require no maintenance on your part. The dow...]]></description>
<content:encoded><![CDATA[<p>Shared SSL means you use your Hosting Provider's SSL Certificate. This will usually result in something like <a title="Demo Domain Name" href="https://yourname.example.com/">https://yourname.example.com</a>. The benefits are that they are generally free or inexpensive to use and require no maintenance on your part. The downside is that a visitor attempting to purchase a good or service from you may be turned off by the fact that they were referred to &quot;an outside domain&quot; to finish their transaction. Most of the time people do not mind (or notice). </p><p>A regular SSL Certificate means you purchased your own certificate for use with your own domain, for example <a title="Demo Domain Name" href="https://secure.example.com/">https://secure.example.com</a>. This benefit to this is that it looks more professional to your customers. The downside is annual costs and maintenance. </p><p>ProExe do not recommend shared SSL. </p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Why are my secure pages loading slower?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/43]]></link>
<guid isPermaLink="false"><![CDATA[17e62166fc8586dfa4d1bc0e1742c08b]]></guid>
<pubDate><![CDATA[Thu, 04 May 2006 14:33:38 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[SSL pages are slower because of the overhead needed to encrypt and decrypt the data. The web server must spend extra time encrypting the data before it is transmitted to your computer. Likewise, your computer must then decrypt the information. The same ap...]]></description>
<content:encoded><![CDATA[<p>SSL pages are slower because of the overhead needed to encrypt and decrypt the data. </p><p>The web server must spend extra time encrypting the data before it is transmitted to your computer. Likewise, your computer must then decrypt the information. The same applies when you securely submit information from your computer to the Web server. All this requires your CPU and the Web server's CPU to work harder and therefore might cause pages to load more slowly. </p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Why do I get a warning that some items are insecure?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/42]]></link>
<guid isPermaLink="false"><![CDATA[a1d0c6e83f027327d8461063f4ac58a6]]></guid>
<pubDate><![CDATA[Thu, 04 May 2006 14:32:38 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[For a server to serve a page securely all items, including graphics, must be accessed using the https:// protocol. If you are receiving a message stating some items are insecure then you have at least one item that is being served unsecurely. To find out ...]]></description>
<content:encoded><![CDATA[<p>For a server to serve a page securely all items, including graphics, must be accessed using the <strong>https://</strong> protocol. If you are receiving a message stating some items are insecure then you have at least one item that is being served unsecurely. </p><p>To find out which items are not secure, let the browser ignore the unsecure items and you will be able to see where most of the items are. </p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Why does my ecommerce website need SSL?]]></title>
<link><![CDATA[https://resourceit.co.uk/support/index.php?/Knowledgebase/Article/View/111]]></link>
<guid isPermaLink="false"><![CDATA[698d51a19d8a121ce581499d7b701668]]></guid>
<pubDate><![CDATA[Wed, 07 Jun 2006 08:59:50 +0000]]></pubDate>
<dc:creator><![CDATA[James Robshaw (Import)]]></dc:creator>
<description><![CDATA[Customers in a shop can see who they are dealing with and can be sure that if something is wrong with their purchase, they'll have recourse to the shop manager or owner. But on the Internet, website visitors have no reliable way of knowing who owns the ec...]]></description>
<content:encoded><![CDATA[<p>Customers in a shop can see who they are dealing with and can be sure that if something is wrong with their purchase, they'll have recourse to the shop manager or owner. But on the Internet, website visitors have no reliable way of knowing who owns the ecommerce site they are about to buy from. They are also exposed to all the security risks associated with sending data over an open network (the Internet). </p><p>When customers visit a website to make an online purchase, they want to know who they'll be paying and that the personal information they submit to the site cannot be intercepted. This is the purpose of an <strong>SSL</strong> digital certificate. </p><p>Use of <strong>SSL</strong> (Secure Socket Layer) and a digital certificate enable a web browser (your customer) to communicate securely with your website, assuring the customer of 3 things: </p><ol><li>That the website really is who it claims to be. </li><li>That credit card numbers, etc are encrypted and cannot be intercepted. </li><li>That the data sent and received cannot be tampered with or forged. </li></ol>]]></content:encoded>
</item>
</channel>
</rss>