1. Secure Enhanced Geolocking
Masters project By
Ashish Korpe
Department of Computer Science
University of Colorado, Colorado Springs
Good morning everybody. First of all, I Thank Dr. Chow, Dr. Rao and Dr. Ventura for serving in my committee ,providing valuable feedback and allowing me to defend on a short notice.

2. Outline of the Talk Introduction Background, prior work SEG vs SAGE
Design
Implementation
Performance evaluation
Challenges faced
Lessons learnt
Future work
Conclusion
References
9/19/2018
SEG/Ashish Korpe

3. Introduction Keeping important information safe, confidential.
Secrecy – non disclosure.
Hiding – encryption decryption.
Secure , https, digital certificates.
Encryption: AES, RSA and other variants.
9/19/2018
SEG/Ashish Korpe

4. Background ,Prior work
Geo – encryption = ‘geo’ (earth/location) + encryption [Denning 2003]
Various attempts to achieve this. [Khan, et al 2003]: [Scott, et al 2003] discuss using location as a key
Proposed work: Scott, Denning: position + velocity + time
SAGE:
PC and smartphone
Use of a secure Bluetooth connection
Two keys: one for PC, one for smartphone
Access within location and time
With sub-bullet indicating the difference between your proposed research and theirs.
SAGE: key is location-time specific
SEG: location is verified and access is granted
9/19/2018
SEG/Ashish Korpe

5. Secure Enhanced Geolocking
Assumptions:
Clients only need to use browsers which support geolocation reporting.
Client Javascripts are created for encrypting the data, specifying the geolocation areas to retrieve the data, and the receiver address.
The receiver has to have Google Earth installed on their device to view the KML file.
SEG Server software is provided to
the receiver with geolocation area information in KML.
Allow the verification of geolocation provided by the receiver, and provide key/encrypted data if the location is within the geolocation area.
If the receiver uses gmail, its not mandatory to have google Earth installed on system/PC. Need google Earth on handheld devices though
9/19/2018
SEG/Ashish Korpe

6. Design
9/19/2018
SEG/Ashish Korpe

7. Implementation Webpages Encryption Location: geolocation, geocoder API
Database: Maria DB, MySQL
KML
Technologies used: HTML5 CSS3 JavaScript PHP
Libraries used: crypto.js
For each of these efforts, you like to show a figure/diagram of actual artifacts and some brief description.
9/19/2018
SEG/Ashish Korpe

8. Compose screen
9/19/2018
SEG/Ashish Korpe

9. Link - > inbox
9/19/2018
SEG/Ashish Korpe

10. Location - Validation
9/19/2018
SEG/Ashish Korpe

11. Location – Validation
9/19/2018
SEG/Ashish Korpe

12. Geolocation, geocoder code
9/19/2018
SEG/Ashish Korpe

13. Geolocation, geocoder code
9/19/2018
SEG/Ashish Korpe

14. Geolocation, geocoder code
9/19/2018
SEG/Ashish Korpe

15. Receiver
9/19/2018
SEG/Ashish Korpe

16. KML code
9/19/2018
SEG/Ashish Korpe

17. KML file attachment
9/19/2018
SEG/Ashish Korpe

18. Encryption – crypto.js
9/19/2018
SEG/Ashish Korpe

19. Test environment MySQL 5.6.17 Windows 7 Home Basic
WAMP server version2.5 - localhost
VM – Fedora core FC22
Maria DB
Compose.html
credentials
Files
ValidateLocation.php
HTML5
CSS3
JavaScript
Geolocation API
Geocoder API
Crypto.js
Php
HTML5
CSS3
JavaScript
Geolocation API
Crypto.js
Php
Inbox.php
HTML5
CSS3
Php
JavaScript
The environment used for testing (localhost) is as follows:
Windows 7 home basic machine running Wamp server version 2.5.
The database used was MySQL version
Database server: MySQL Community Server (GPL)
Web server: Apache/2.4.9 (Win32)
Once the system worked fine on localhost, the code was migrated to akorpe.csnet.uccs.edu
The production environment (akorpe.csnet.uccs.edu) is described below:
VM running Fedora Core FC22 operating system.
The database used is Maria DB version
Database server: Maria DB
Web server: Apache/ (Fedora)
Google Chrome m
Sender
Receiver
9/19/2018
SEG/Ashish Korpe

20. Html5
CSS
JavaScript
Php
9/19/2018
SEG/Ashish Korpe

21. Performance Evaluation
Time required for composing and sending seconds
Time required for validating location, decrypting and accessing the file: milliseconds
9/19/2018
SEG/Ashish Korpe

22. Challenges faced Validating receiver’s location
Acknowledge Dr Ventura’s help
9/19/2018
SEG/Ashish Korpe

23. Challenges faced Email attachment problems Code line SEG/Ashish Korpe
9/19/2018
SEG/Ashish Korpe

24. Challenges faced Enabling receiver to access the file code
9/19/2018
SEG/Ashish Korpe

25. Challenges faced Enabling receiver to access the file SEG/Ashish Korpe
9/19/2018
SEG/Ashish Korpe

26. Lessons Learnt
Keyhole Markup Language is useful. Google has provided Google Earth program, Geolocation API which can be integrated nicely into my SEG application.
CryptoJS is easy to use just plug in the link in <script> tags,
Crypto js : easy to use just put it in script tags and mention a function. Key management image
9/19/2018
SEG/Ashish Korpe

27. Future Directions
Validation of receiver’s geolocation (through close by Wi- Fi/bluetooth signals/base station locations/images from webcams – facial recognition)
Measures against spoofing
Encrypting multiple files
Encrypting different types of files
Make the app more user friendly
Making it easier to specify the geolocation area.
If asked about spoofing, mention Jahnavi is working on it 
9/19/2018
SEG/Ashish Korpe

28. Conclusion
I have designed and implemented a system for secure geolocking.
Provide authoring tools for specifying geolocation area and encoding them in KML
Provide JavaScript with cryptojS to encrypt the data.
the receiver with guiding information to retrieve data in designated areas.
Verify the receiver’s geolocation and provide key/encrypted if within specified geolocation area.
I have conducted experiments to verify the performance our SEG system and it is capable of providing adequate response and data protection features.
9/19/2018
SEG/Ashish Korpe

29. References
[1] Scott, L. and Denning, D. E. “Location Based Encryption and its Role in Digital Cinema Distribution,” ION GPS/GNSS 2003, September 9-12, Portland
[2] Rajeswari, V., V. Murali, and A. V. S. Anil. "A Navel Approach to Identify Geo-Encryption with GPS and Different Parameters (Locations And Time)." IJCSIT) International Journal of Computer Science and Information Technologies 3.4 (2012).
[3]
[4]
[5] Location-Based Encryption / Decryption (L-BED) WHITE PAPER GeoCodex, LLC June 2010
[6]
[7]
[8]
[9]
[10] Chapter 5 - “Head First HTML5 Programming” by Eric Freeman and Elisabeth Robson
[11] samples.googlecode.com/svn/trunk/interactive/index.html#./Polygons/Polygons.Extruded.k ml
[12]
9/19/2018
SEG/Ashish Korpe

30. Questions ?
9/19/2018
SEG/Ashish Korpe