Step 64 Text Encryption ===Dec.11.2011-written by JCPMA===
This is the inaugural post for the Javascript Encryption series. The series begins with Step 64 Text Encryption.
Step 64 can encrypt messages written with contemporary text. It accepts most text characters of another language, unusual symbols, or non-standard punctuation.
Step 64 was hosted at http://jcpma.bravehost.com/js-encr/step64-tnk.html
Step 64 is hosted at http://bigarrow.tripod.com/js-encr/step64-tnk.html
If the IFrames link below, does not work in your browser, then here is a screenshot of what it looks like.
----Download a copy of Step 64 Text Encryption----
Step 64 is a 20 KB standalone webpage. Its complement logo is 2 KB, but is not necessary for for the script operation. (It just makes the webpage prettier.) Saving a copy from the website will work, however, it is recommended to download from the file sharing site Mediafire or Box.net for reasons of html purity.
The webhost I am using is advertisment-supported. They inject ad-related code into the webpage inflating it to a size of 35 KB. Also, they anchor the page by associating it with approximately 20 (ad and marketing related) extra files of 104 KB. Thus a total of 22 files at 139 KB instead of the original 2 files at 22 KB. None of these extra files are necessary to the function of the encryption.
Download the ad-free original webpage, step64-tnk.html, from Mediafire: http://www.mediafire.com/download.php?nol5eomkagx97sn
Download the ad-free original webpage, step64-tnk.html, from Box.net: http://www.box.com/s/tdcb24rz49jdjhmpnxbf
Download the logo, step64logo32.png 2 KB
(This is an old link - do not go here: http://jcpma.bravehost.com/js-encr/step64logo32.png)
Bravehost site has restructured, therefore ignore any ref's to their links mentioned in this site.
The newer sites are Tripod and others.
http://bigarrow.tripod.com/js-encr//step64logo32.png
step64logo.32.png at Mediafire: http://www.mediafire.com/download.php?oecqrxvsrcyle6v
step64logo.32.png at Box.net: http://www.box.com/s/973aboc02x42tq019zyk
Javascript Encryption series preamble (Links to the series follow below)
I have assembled and modified a compilation of html webpages which run on Javascript and perform to encrypt text. (This includes one of my own creations, that is, a javascript webpage made by a non-programmer!)
Why I am a proponent for encryption. Briefly explained, the promotion of privacy is one of the pillars of a coveted civilization. (If convenient, this may be discussed in a future post.)
Why I chose javascript. In my own words, javascript is ubiquitous and is supported in most if not all current popular web browsers. Operations are performed locally, ie., at your computer terminal whether you are connected to the internet or not. Javascript has one aspect of superiority over "Java". Most web browsers are ready to perform with javascript, whereas with Java, the computer must undergo a one-time installation of Java software/plug-in in order to work. Many but not all computers have Java installed. Another way of saying this is that at any given moment, the likelihood of a web browser having Java ability is less than javascript ability. Also, the webpages when saved locally should function even at a moment when the hardware is disconnected from the internet.
Why the creator of Javascrypt, John Walker of www.fourmilab.ch, supports javascript. (The quote is not exact verbatim, but the thoughts are his.) "...Transparency and Security. Transparency refers to the opportunity to view/inspect the javascript code/source code to ensure it does what it claims to. Security refers to performing encryption at your unique browser terminal. It does not rely on a constant calling of software from another location or across the internet. ..."
---PLAN A---
My intention was to publish each webpage of this series as a separate post. Notice the series header begins with three hash (###) marks. I wanted to start each post with an identifying number unique to this blog.
The Obstacle. The obstacle to this plan was the incompatibility with Blogger. I experimented by posting a webpage via Blogger's html editor, and the interim result showed only a partially functioning javascript post with most of the formatting and colours incomplete or mishandled. I reviewed some of the solutions from the internet on how to enable javascript in Blogger. The answers distil down to two categories.
One, make the javascript a part of your template/layout; or
Two, make the javascript a part of a post by altering the code.
Method One is unacceptable as I do not want the javascript to be loaded (UNIVERSALLY) with each and every post.
Method Two is IMPRACTICAL as altering the javascript is labour-intensive; Tremendously a massive amount of effort is needed, and not guaranteed to work. (The information I found on the internet claims the javascript in a post will function if you write the code as a single line. Remove all components which 'freak out' Blogger's editor thus preventing it from 'hiccupping' and inserting line breaks defacing the code.) Method Two may be adequate for small short pieces of javascript, but my compilation contains huge lumps of the stuff.
---PLAN B---
This is instead how I will proceed. The collection will be uploaded via FTP to a traditional non-blogging webpage hosting site. This permits employing or trying out the webpage directly from cyberspace without having to download anything. The disadvantage is that there are host inserted ads, usually banner ads at the top and or bottom of the page, which inflate the size (KB) of the webpage. Surprisingly the dvertisements and its components can take up a lot of space. (see above)
These pages will be linked by IFrames (experimentally) to this blog. For archiving redundancy the original (unaltered) webpages will be uploaded to file sharing sites Mediafire.com and Box.net (My current two favourite file sharing sites).
[Cloud Impermanence. A rehashing of my own biassed opinion: One of my favourite web 2.0 ("cloud") services, was Drop.io, a file sharing and archiving site from a southwestern company. The convenience it offered was slick and beyond excellence. Then one day business forces resulted in a restructuring of the current terms of service. Reasonable and adequate notice was given for Drop.io users to prepare for service termination. For the informed user, no loss of digital files happened. Unfortunately, any user hyperlinks pointing to the site were nullified. Thusly, so was the work put into setting up the links. I only had a handful of dead-links, but others had many many links. What a frustrating process. Here is some good news. As powerful as Google is, they remain surprisingly ethical. Like Mr. Spock would say, I wish Google, Bravenet, Mediafire, and Box.net "long-life and prosperity" so their current excellence can be maintained. My skeptical nature however tells me any service can decline/cease with time. There will be more dead-links.]
So far, the entire series is hosted at this website in this directory:
http://jcpma.bravehost.com/js-encr/
This is the js-encr folder at Mediafire: http://www.mediafire.com/?yz2o4lrg3xplq
This is the js-encr folder at Box.net: http://www.box.com/s/g3mjclevtqh5zucy5hi2
The files:
http://jcpma.bravehost.com/js-encr/11jscram.htm
http://jcpma.bravehost.com/js-encr/ba_index-b64-6.html
http://jcpma.bravehost.com/js-encr/base64logo32.png
http://jcpma.bravehost.com/js-encr/block-tea7.html
http://users3.jabry.com/jonjonbadboy/js-encr/j4jscrypt.html
http://jcpma.bravehost.com/js-encr/js-encr.txt
http://jcpma.bravehost.com/js-encr/js-encr-checksum.md5.txt
js-encr-checksum.md5.txt at Mediafire: http://www.mediafire.com/download.php?fqv0agszmuzepg7
js-encr-checksum.md5.txt at Box.net: http://www.box.com/s/uy95tayfxx9lburtj33v
http://jcpma.bravehost.com/js-encr/js-encr.zip <== this file represents all the files in the directory.
js-encr.zip at Mediafire http://www.mediafire.com/download.php?28i307t6nktfhi9
js-encr.zip at Box.net http://www.box.com/s/ay3l6q9zlojbdqqfaaeg
http://jcpma.bravehost.com/js-encr/m_aes8.html
http://jcpma.bravehost.com/js-encr/md5logo32.png
http://jcpma.bravehost.com/js-encr/md_index-md5-6.html
http://jcpma.bravehost.com/js-encr/n-alphac8.html
http://jcpma.bravehost.com/js-encr/PG1pubkeya.htm
http://jcpma.bravehost.com/js-encr/PG2encodi.htm
http://carpediem2100.fcpages.com/js-encr/sereg7.htm
http://bigarrow.tripod.com/js-encr/step64-tnk.html
http://jcpma.bravehost.com/js-encr/step64logo32.png
http://jcpma.bravehost.com/js-encr/v2c-JEnc.htm
md5 hashes of the directory:
11jscram.htm,292edb74be45bc5114f725d215786180
base64logo32.png,15fe14a4e58b6777942190ed84ea6833
ba_index-b64-6.html,9f7bbe60e1e2c19ddaef9e7291b8f6c3
block-tea7.html,989ad5c2c5dbadfeb0328ae6519a36f5
j4jscrypt.html,c0374cced40bbfb97ea992f7c8ca44d5
js-encr.txt,09cd9a9bbb94a3bc23854cd43a9e8573
js-encr-checksum.md5.txt,00e5ff886491a1a62acb43c8f13a3de7
js-encr.zip,71e86697e6589075e3f05eb4592871cc
md5logo32.png,d898a1ee216ab264edc677d2efec7be6
md_index-md5-6.html,5a5f9d940b5abab1ce5224a50fb61b18
m_aes8.html,5803a81cc5f10314325a7ceb6d2be398
n-alphac8.html,ee0733a05ab84a81ba5efe6d8e0a94a4
PG1pubkeya.htm,f6a6e06a1e6b89d4b789ad90d3f610c2
PG2encodi.htm,b7d5fb7e29d353271767d732d0e4988b
sereg7.htm,833585e0d25fa79d5fcbe23074f90ec2
step64-tnk.html,a418dd41773e3a58cf8e6e73b3fb52f2
step64logo32.png,1ca4e881eb2216b2d46e2aac85eb4ac7
v2c-JEnc.htm,93289a6e0e14ab51962f79fc43ae89f7
---PLAN A---
My intention was to publish each webpage of this series as a separate post. Notice the series header begins with three hash (###) marks. I wanted to start each post with an identifying number unique to this blog.
The Obstacle. The obstacle to this plan was the incompatibility with Blogger. I experimented by posting a webpage via Blogger's html editor, and the interim result showed only a partially functioning javascript post with most of the formatting and colours incomplete or mishandled. I reviewed some of the solutions from the internet on how to enable javascript in Blogger. The answers distil down to two categories.
One, make the javascript a part of your template/layout; or
Two, make the javascript a part of a post by altering the code.
Method One is unacceptable as I do not want the javascript to be loaded (UNIVERSALLY) with each and every post.
Method Two is IMPRACTICAL as altering the javascript is labour-intensive; Tremendously a massive amount of effort is needed, and not guaranteed to work. (The information I found on the internet claims the javascript in a post will function if you write the code as a single line. Remove all components which 'freak out' Blogger's editor thus preventing it from 'hiccupping' and inserting line breaks defacing the code.) Method Two may be adequate for small short pieces of javascript, but my compilation contains huge lumps of the stuff.
---PLAN B---
This is instead how I will proceed. The collection will be uploaded via FTP to a traditional non-blogging webpage hosting site. This permits employing or trying out the webpage directly from cyberspace without having to download anything. The disadvantage is that there are host inserted ads, usually banner ads at the top and or bottom of the page, which inflate the size (KB) of the webpage. Surprisingly the dvertisements and its components can take up a lot of space. (see above)
These pages will be linked by IFrames (experimentally) to this blog. For archiving redundancy the original (unaltered) webpages will be uploaded to file sharing sites Mediafire.com and Box.net (My current two favourite file sharing sites).
[Cloud Impermanence. A rehashing of my own biassed opinion: One of my favourite web 2.0 ("cloud") services, was Drop.io, a file sharing and archiving site from a southwestern company. The convenience it offered was slick and beyond excellence. Then one day business forces resulted in a restructuring of the current terms of service. Reasonable and adequate notice was given for Drop.io users to prepare for service termination. For the informed user, no loss of digital files happened. Unfortunately, any user hyperlinks pointing to the site were nullified. Thusly, so was the work put into setting up the links. I only had a handful of dead-links, but others had many many links. What a frustrating process. Here is some good news. As powerful as Google is, they remain surprisingly ethical. Like Mr. Spock would say, I wish Google, Bravenet, Mediafire, and Box.net "long-life and prosperity" so their current excellence can be maintained. My skeptical nature however tells me any service can decline/cease with time. There will be more dead-links.]
So far, the entire series is hosted at this website in this directory:
http://jcpma.bravehost.com/js-encr/
This is the js-encr folder at Mediafire: http://www.mediafire.com/?yz2o4lrg3xplq
This is the js-encr folder at Box.net: http://www.box.com/s/g3mjclevtqh5zucy5hi2
The files:
http://jcpma.bravehost.com/js-encr/11jscram.htm
http://jcpma.bravehost.com/js-encr/ba_index-b64-6.html
http://jcpma.bravehost.com/js-encr/base64logo32.png
http://jcpma.bravehost.com/js-encr/block-tea7.html
http://users3.jabry.com/jonjonbadboy/js-encr/j4jscrypt.html
http://jcpma.bravehost.com/js-encr/js-encr.txt
http://jcpma.bravehost.com/js-encr/js-encr-checksum.md5.txt
js-encr-checksum.md5.txt at Mediafire: http://www.mediafire.com/download.php?fqv0agszmuzepg7
js-encr-checksum.md5.txt at Box.net: http://www.box.com/s/uy95tayfxx9lburtj33v
http://jcpma.bravehost.com/js-encr/js-encr.zip <== this file represents all the files in the directory.
js-encr.zip at Mediafire http://www.mediafire.com/download.php?28i307t6nktfhi9
js-encr.zip at Box.net http://www.box.com/s/ay3l6q9zlojbdqqfaaeg
http://jcpma.bravehost.com/js-encr/m_aes8.html
http://jcpma.bravehost.com/js-encr/md5logo32.png
http://jcpma.bravehost.com/js-encr/md_index-md5-6.html
http://jcpma.bravehost.com/js-encr/n-alphac8.html
http://jcpma.bravehost.com/js-encr/PG1pubkeya.htm
http://jcpma.bravehost.com/js-encr/PG2encodi.htm
http://carpediem2100.fcpages.com/js-encr/sereg7.htm
http://bigarrow.tripod.com/js-encr/step64-tnk.html
http://jcpma.bravehost.com/js-encr/step64logo32.png
http://jcpma.bravehost.com/js-encr/v2c-JEnc.htm
md5 hashes of the directory:
11jscram.htm,292edb74be45bc5114f725d215786180
base64logo32.png,15fe14a4e58b6777942190ed84ea6833
ba_index-b64-6.html,9f7bbe60e1e2c19ddaef9e7291b8f6c3
block-tea7.html,989ad5c2c5dbadfeb0328ae6519a36f5
j4jscrypt.html,c0374cced40bbfb97ea992f7c8ca44d5
js-encr.txt,09cd9a9bbb94a3bc23854cd43a9e8573
js-encr-checksum.md5.txt,00e5ff886491a1a62acb43c8f13a3de7
js-encr.zip,71e86697e6589075e3f05eb4592871cc
md5logo32.png,d898a1ee216ab264edc677d2efec7be6
md_index-md5-6.html,5a5f9d940b5abab1ce5224a50fb61b18
m_aes8.html,5803a81cc5f10314325a7ceb6d2be398
n-alphac8.html,ee0733a05ab84a81ba5efe6d8e0a94a4
PG1pubkeya.htm,f6a6e06a1e6b89d4b789ad90d3f610c2
PG2encodi.htm,b7d5fb7e29d353271767d732d0e4988b
sereg7.htm,833585e0d25fa79d5fcbe23074f90ec2
step64-tnk.html,a418dd41773e3a58cf8e6e73b3fb52f2
step64logo32.png,1ca4e881eb2216b2d46e2aac85eb4ac7
v2c-JEnc.htm,93289a6e0e14ab51962f79fc43ae89f7
Posts
No comments:
Post a Comment