|
Extra Course Material
In light of recent requests made by students, some supplementary
notes used in course lectures have been posted on the website. They can
be accessed by clicking on the link below. In the third set of slides please
stop at ATM. We didn't cover that.
- Part 1 Data Communications
-
Part 2 Long-Distance Communications
-
Part 3 Integrity in Communications and Newer Technology
March 31, 2015
|
|
Public-key Infrastructure (PKI)
A public-key infrastructure (PKI) is the system
required to provide public-key encryption and
digital signature services. Its purpose is to
manage encryption keys and certificates so that
business transactions can be handled securely
over the internet. In order for the public-key
infrastructure to work effectively, there must
always be some certificate authority (CA)
available to verify the authenticity of
the public key. This certificate authority
can be private, or internal, to a company or
a public outside trusted third party (TTP) like
Verisign. PKI infrastructures support many
services transparently to the user: public key
certificates, certificate repositories,
certificate revocation, key backup and recovery
and histories, automatic updates for key pairs
and certificates, cross-certification, non-
repudiation of digital signatures and client-
side software interacting reliably with all
of the above.
Public and private keys are made in pairs
through the certificate authority (CA). Using
asymmetric key pair encryption implies that
whenever one key in the pair is used to encrypt
data, the other must be used to decrypt it.
The public key and the private key are
mathematically dependent such that the public
key can easily be created from the private key
but the reversal of the public key to the
private key would take literally thousands
of years of computing to accomplish. Public
keys are provided in a certificate signed with
the CA's digital signature and private keys
are never revealed. Client software must be
configured to "trust" certificates
from particular certificate authorities.
Simply put, the two supported actions using PKI
are as follows:
1. To send an encrypted message, the sender
uses the receiver's public key to encrypt.
The receiver then uses his private key to
decrypt the message.
2. To send a digital signature, the sender
uses his private key to encrypt. The receiver
then uses the sender's public key to decrypt
or "authenticate" the sender.
A special thanks for researching this topic
goes to:
Robert Mavrinac
Server & Network Technician
School of Computer Science
|
January 14, 2015:
|
|
Examples of HTML Files.
Here
are the files we have been working with in class. The first
is the skeleton file which you can use as a template. It is
available here. When
you add the HTML code for your web pages then you
have to save it as an HTML file with your chosen file name.
The next file is the example
given in class which is saved as an HTML file with the
necessary boilerplates. You can view it here.
|
January 14, 2015:
|
|
Welcome Students for the winter semester 2014.
REMINDER:
You must activate your WEBMAIL before
Thursday, September 24th., 2014.
|
January 14, 2015:
|
|
E-mail Correspondence
You must use ONLY "uwindsor.ca" e-mail accounts for
course correspondence. E-mail sent from other accounts will be ignored and left unanswered.
|
January 14, 2015:
|
|
A former student of this class sent me a very interesting e-mail containing comments
about this course. You should all read
these comments. Please close the window when you are finished.
|
January 14, 2015:
|
|
A reminder that all text content on your Web-site must be in YOUR OWN WORDS.
Copying text from other sources is strictly forbidden. You will receive a mark
of 0/25 for the final project if you are caught--and you will be caught.
|
[ Main Page ]
[ Current News ]
[ Course Information ]
[ Teaching Assistants ]
[ Class Lists ]
[ Feedback ]
[ Lecture Schedule ]
[ Projects ]
[ Download Utilities ]
[ Help Pages ]
Number of visits
![[counter]](http://electron.cs.uwindsor.ca/cgi-bin/count5)
|
