-
Notifications
You must be signed in to change notification settings - Fork 15
/
Copy pathgsoc2015.html
704 lines (630 loc) · 31.9 KB
/
gsoc2015.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
---
title: Linear
layout: default
---
<style media="screen">
#proposals h2{
font-size: 1.3em;
color: #000;
font-weight: bold;
}
</style>
<!-- Main -->
<div id="main">
<div class="container">
<div class="row">
<div id="content" class="12u skel-cell-important">
<section>
<header>
<h2>Google Summer of Code 2015</h2>
</header>
<p>
Welcome to the SCoRe Lab Google Summer of Code (GSoC) 2015 project ideas page. We are a dynamic and enthusiastic nonprofit research
group pioneering in Internet of Things (IOT), Embedded Systems, Computer Security and 'Wireless Adhoc and Sensor Networks' and is
one of the best groups in South Asia. We are based in the University of Colombo School of Computing, Sri Lanka. This is the first time
that we are participating in the GSoC, we will use this page to develop possible project ideas that have on the above mentioned areas.
Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest
possible project ideas. You can also talk to us about possible project ideas and we are happy to improve or heip you with them.
Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working
full time for about eight weeks. Thanks!
</p>
<p>
<b>Mailing list: </b><a href="http://groups.google.com/d/forum/score-community" target="_blank">[email protected]</a>
</P>
<p>
IRC Channel: #scorelab
</p>
</section>
<section>
<header>
<h2>Important Guidelines on Submitting Ideas</h2>
</header>
<p>There are some important guidelines to submit ideas, please read these carefully before adding your ideas:</p>
<ul style="list-style:inherit">
<li>
There is a fixed time period for implementing and coding your ideas.
</li>
<li>
Come up with attainable goals and you will be able to complete what you set out to do. You can always contact our mentors and community and get an idea about the workload and whether you might be able to complete them.
</li>
<li>
You are free to come up with your own ideas. The ideas should be about Internet of Things (IOT), Embedded Systems, Computer Security and 'Wireless Adhoc and Sensor Networks’. Also if you love to work on any of these subjects but do not have an idea you can always contact us.
</li>
<li>
Lets Talk! The best way to solve problems that you might have is to contact our mentors and also our community. This will help you to not get bogged down in your ideas and to move on.
</li>
<li>
We encourage you to do documentation so that we can keep track of your progress and also help you if things are not going according to plan. Although not compulsory we have a strong belief that this method can cut down your time to code and also the workload of the mentors drastically.
</li>
</ul>
</section>
<section>
<header>
<h2>Proposals list for GSoC 2015</h2>
</header>
<ol style="padding-left: 25px;">
<li><a href="#opendf-1">Proposal 1 : Forensics Timeline Module for OpenDF</a></li>
<li><a href="#opendf-2">Proposal 2 : Auto-Installer and Easy Deployments for OpenDF</a></li>
<li><a href="#opendf-3">Proposal 3 : Browser Data Module for OpenDF</a></li>
<li><a href="#opendf-4">Proposal 4 : Image,video & audio metadata Module for OpenDF</a></li>
<li><a href="#opendf-5">Proposal 5 : Test Automation for OpenDF</a></li>
<li><a href="#tracker-1">Proposal 6 : User Interfaces for Tracker</a></li>
<li><a href="#tracker-2">Proposal 7 : Auto Installer for Tracker</a></li>
<li><a href="#packtrack-1">Proposal 8 : Create adding stations and carriers module for Pack-Track</a></li>
<li><a href="#packtrack-2">Proposal 9 : Connect Pack-Track with Tracker for Pack-Track</a></li>
<li><a href="#packtrack-3">Proposal 10 : REST API to get data for Pack-Track</a></li>
<li><a href="#tikiridb">Proposal 11 : Redesign Tikiri-DB</a></li>
<!--
<li><a href="#snsm">Proposal 12 : Social Networks for situation mining</a></li>
-->
<li><a href="#IoTDatastore">Proposal 12 : IoT Datastore powered by Distributed Software Transactional memory</a></li>
<li><a href="#androphsy-1">Proposal 13 : Improve root exploit support for Androphsy</a></li>
<li><a href="#androphsy-2">Proposal 14 : Advanced phonographic content search for Androphsy</a></li>
<li><a href="#androphsy-3">Proposal 15 : Unknown binary analysis for Androphsy</a></li>
<li><a href="#taxi">Proposal 16: Top-k publish/subscribe model for intelligent Taxi allocation</a></li>
<li><a href="#17">Proposal 17 : Data acquisition module + screen lock for androphsy</a></li>
<li><a href="#18">Proposal 18 : Search optimization/Text Indexing + Report Generation for Androphsy</a></li>
<li><a href="#19">Proposal 19: End-to-End Encryption of Android Phone Calls</a></li>
<li><a href="#20">Proposal 20: Discriminatively trained deformable part models</a></li>
<li><a href="#21">Proposal 21: Smartphone Support for People who Stutter</a></li>
<li><a href="#22">Proposal 22: PokuruPC configuration for Raspberry Pi 2</a></li>
<li><a href="#23">Proposal 23: Developing query parser for Senze language</a></li>
<li><a href="#24">Proposal 24: BASSA-Automated download queue</a></li>
<li><a href="https://docs.google.com/document/d/11xs5Au4FQsWI9v-P5bsbvEqjR5nFge0T8yXEaZ4RPqg/pub">Proposal Template for Students</a></li>
</ol>
</section>
<section id="proposals">
<div id="opendf">
<h2>OpenDF</h2>
<p>An effort to build an Open Source tool to help Digital Forensics Investigations by bringing all the related processes in digital forensics into one complete solution.
<br>Site : <a href="http://www.scorelab.org/OpenDF" target="_blank">www.scorelab.org/OpenDF</a></p>
</div>
<br/>
<div id="opendf-1">
<h2>Proposal 1 : Forensics Timeline Module for OpenDF</h2>
<p>Develop a module that can visually represent, in user friendly way, the activities recorded in a Disk Image, like file access activities, browser histories, etc. This should extract different kind of time series data and represent in a way that the investigators can get an indea of the last activities done on a given Disk Image.
<br/>
<b>Required Knowledge: </b>
<ul>
<li>Sleuth Kit</li>
<li>Java EE</li>
<li>AngularJS</li>
</ul></p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul>
</p>
</div>
<br/>
<br>
<div id="opendf-2">
<h2>Proposal 2 : Auto-Installer and Easy Deployments for OpenDF</h2>
<p> Auto installer should install the db script and create an admin account with the details provided by the user. It should also display the User Agreement and get user agreed to the terms before initialization. This includes setting up organisation details, report header templates etc.</p>
<p> Since this task is little bit easy, we like you to work on Easy Deployments task also. The ideas is to use <a href="http://vagrantup.com">Vagrant</a> to let anyone spawn an OpenDF configured VM within minutes. What has to be done is, write some shell scripts to install needed platforms( Git, Java, Glashfish, etc ) on top of a Linux distro and exposing the application to the outer environment. We can shre this Vagrant configuration on <a href="http://docs.vagrantup.com/v2/share/">Vagrant Share</a>. Then anyone who likes to use OpenDF can simply use <code>vegrant up</code> command and visit the url from the user's browser once the VM successfully started
<br>
<b>Required Knowledge: </b>
<ul>
<li>Sleuth Kit</li>
<li>Java EE</li>
<li>Vegrant</li>
</ul></p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<br>
<div id="opendf-3">
<h2>Proposal 3 : Browser Data Module for OpenDF</h2>
<p>Develop a web browser data module for OpenDF using the Sleuth Kit's browser data extractions feature. Browser data may include browser history, cookies, saved passwords, browser bookmarks, etc. You should find a way to present these data in user friendly way.
<br>
<b>Required Knowledge: </b>
<ul>
<li>Sleuth Kit</li>
<li>Java EE</li>
<li>AngularJS</li>
</ul>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<br>
<div id="opendf-4">
<h2>Proposal 4 : Image,video & audio metadata Module for OpenDF</h2>
<p>Develop a module for OpenDF to extract meta data of images( Photos ),video & audio and present in user friendly way. There are several Photographic Metadata Standards like, Exif ( Exchangeable image file format ), etc. Your task is to query for media files and extract these metadata from them. This should be done in whole or for a given media file. And these data should be presented to the user while browsing the files on the Disk Images.
<br>
<b>Required Knowledge: </b>
<ul>
<li>Sleuth Kit</li>
<li>Java EE</li>
<li>AngularJS</li>
</ul>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<br>
<div id="opendf-5">
<h2>Proposal 5 : Test Automation for OpenDF</h2>
<p>GSoC is not only about developing, it is also about testing! We need a mechanism to automate the functional testing, something like Selenium may be ideal ( Cucumber test framework may also be a good fit ). If we can have a test script, a continious intrigation tool can execute these tests for every build. Therefor the task is to come up with a suitable test automation mechanism and start writing the test scripts. ( You can refer the OpenDF's test documents to get an idea of test cases. )
<br>
<b>Required Knowledge: </b>
<ul>
<li>AngularJS</li>
<li>Test automation</li>
<li>mechanisms</li>
</ul>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<br>
<div id="tracker">
<h2>Tracker</h2>
<p>Tracker is to help developers to jumpstart developping anykind of mobility tracking applications.
It lets any type or number of GPS devices to post their locations to a nodejs server through a ReST service.
<br/>
This consists of several main modules
<ul>
<li>HTML5+AngularJS Front-end</li>
<li>NodeJS+MongoDB API for collecting and quering tracker data</li>
<li>Php+MySQL back-end to manage the trackers & etc.</li>
<li>Android app to push data to the API</li>
<li>Documentation</li></ul></p>
<br/>
</div>
<div id="tracker-1">
<h2>Proposal 6 : User Interfaces for Tracker</h2>
<p>
We still are not done with the UIs of the Tracker, we have to write UIs that consumes the web servise and help users to interact. UIs includes following,
</p>
<ul>
<p><b>Managers’ Dashboard</b></p>
<ul>
<li>This page should be able to display the current active trackers that the manager is tracking.</li>
<li>A separate section should display a map with the current positions of the devices along with their paths for a pre-defined time.</li>
<li>When a tracker is selected, details about the selected trackers’ location and path should be highlighted on the map along with other relevant details.</li>
</ul>
<p><b>Create ResourceM</b></p>
<ul>
<li>This should allow the managers to create a resource along with the resource name, details and icon. This will be the type of the trackers.</li>
</ul>
<p><b>Create Tracker</b></p>
<ul>
<li>Manager should be able to add a new tracker. The tracker will be referenced from the MAC address of the tracking device. The type of the tracking device will be selected from a pre-created resources list.</li>
</ul>
<p><b>Tracker Details Page</b></p>
<ul>
<li>A tracker device should have its own details page. It will show the path and the location of the tracker and its relevant details. The manager should be able to send any message to the tracker device if the device supports that service.</li>
</ul>
</ul>
<br>
<p><b>Required Knowledge: </b>
<ul>
<li>NodeJS</li>
<li>MongoDB ( NoSQL )</li>
<li>HTML5</li>
</ul>
</p>
<p><b>GitHub Repo :</b><a href="https://github.com/scorelab/Tracker">https://github.com/scorelab/Tracker</a></p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<div id="tracker-2">
<h2>Proposal 7 : Auto Installer for Tracker</h2>
<p>
Auto installer should start the first time the app is run. It should take the necessary information about the organization and initiate the system accordingly.
<br>
<b>Required Knowledge: </b>
<ul>
<li>NodeJS</li>
<li>MongoDB ( NoSQL )</li>
<li>HTML5</li>
</ul>
</p>
<p><b>GitHub Repo :</b><a href="https://github.com/scorelab/Tracker">https://github.com/scorelab/Tracker</a></p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br/>
<br/>
<div id="packtrack">
<h2>Pack Track</h2>
<br/>
<p>
Pack Track is basically a low cost parcel management and parcel tracking system.
<br>Site <a href="http://www.scorelab.org/Pack-Track/" target="_blank">www.scorelab.org/Pack-Track/</a>
</p><br>
<div id="packtrack-1">
<h2>Proposal 8 : Create adding stations and carriers module for Pack-Track</h2>
<p>
Add modules to create new warehouses and carriers. Connect it with existing modules. Automate the process parcel assignment to carriers.
<br>
<b>Required Knowledge: </b>
<ul>
<li>Java EE</li>
<li>Struts 2</li>
<li>Hibernate 3</li>
</ul>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<br>
<div id="packtrack-2">
<h2>Proposal 9 : Connect Pack-Track with Tracker</h2>
<p>
Connect Pack-Track with tracker to get real-time locations of the parcels and display them on a map.
<br>
<b>Required Knowledge: </b>
<ul>
<li> Java EE</li>
<li>Struts 2</li>
<li>Hibernate 3</li>
<li>NodeJS</li>
<li>MongoDB</li>
</ul>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
<br>
<br>
<div id="packtrack-3">
<h2>Proposal 10 : REST API to get data for Pack-Track</h2>
<p>
Improve the API to get parcel data for third parties and develop the security measures for access control
<br>
<b>Required Knowledge: </b>
<ul>
<li>Java EE</li>
<li>Struts 2</li>
<li>Hibernate 3</li>
<li>ReST Services</li>
</ul>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Charitha Madusanka</li>
</ul></p>
</div>
</div>
<br/>
<br/>
<div id="tikiridb">
<h2>Proposal 11 : Redesign Tikiri-DB</h2>
<p>
TikiriDB is a database abstraction layer to enable a query interface to acquire required data in highly efficient manner. After setting up the sensor network with TikiriDB It is possible to gather data without having the knowledge of programming sensor nodes. TikiriDB will provide a query language which is more similar to conventional query language with additional syntax to comply with sensor network environment. TikiriDB system is composed in three parts on is installed in sensor nodes, one is installed in base-stations and the other is installed in computer connected with the base-station. The application installed in computer will provide an API to connect the your application with the database. Query processor of TikiriDB is located at sensor node. The other part which installed in base-station node will mainly handle the routing of the queries. In this project main objective is make TikiriDB compatible with newer Contiki vision.
</p>
<p>
<b>TikiriDB: </b><a href="https://github.com/scorelab/TikiriDB" target="_blank">https://github.com/scorelab/TikiriDB</a>
</p>
<p>
<b>Contiki: </b><a href="https://github.com/contiki-os/contiki" target="_blank">https://github.com/contiki-os/contiki</a>
</p>
<p>
<b>Required Knowledge: </b>
<ul>
<li>Contiki OS</li>
<li>C</li>
<li>Database</li>
</ul>
</p>
</div>
<br>
<br>
</br/>
<div id="IoTDatastore">
<h2>Proposal 12 : IoT Datastore powered by Distributed Software Transactional memory</h2>
<p>One of the challenges associated with the internet of things is figuring out where to put all that data. If you have dozens of connected devices talking to the cloud you’ve got to think about where that data lives, how to normalize it and how to grant others access to it so it becomes useful. The goal of this project is to optimize read/write operations in such data store which can be used as a platform to build concurrent systems. Software Transactional Memories (STMs) are emerging as a powerful paradigm to develop concurrent applications. By relishing the programmer from the burden of managing locks or other low-level concurrency control mechanisms, the reliability of the code is increased and the software development time significantly shortened.
</p>
<br/>
<p>
<b>Deliverables: </b>
<ul>
<li>Model IoT data in single data framework (You can use existing tools)</li>
<li>Implement STM on cluster nodes which can plug into above framework</li>
<li>Solve conflicts between STMs running on different nodes of the cluster which requires nodes to obtain exclusive access to the datastore during the commit phase</li>
<li>Build a debug tool to explore performance metrics</li>
</ul>
</p>
<p>
<b>Skills Needed: </b>
<br/> - Basic concepts behind Software Transactional Memory, Modeling dynamic data using existing data-structures
</p>
<p>
<b>References: </b>
<br/> - http://pastramy.gsd.inesc-id.pt/
</p>
</div>
<br/>
<br>
<div id="androphsy-1">
<h2>Proposal 13 : Improve root exploit support for Androphsy</h2>
<p>
The process of gain superuser access to Android file system root folder is known as device rooting. There is no general way to gain root access in all Android smartphones as it is highly coupled with vendor, Android version, build number, kernel and model. Improve the device rooting module of androphsy by implementing more root exploits so that the tool will support wider range of Android smartphones. It is expected to automate the rooting process.
<br>
<br>
<b>Required Knowledge: </b>
<ul>
<li>Android platform</li>
<li>Suitable Android kernel exploits / vulnerabilities</li>
<li>Scripting language (i.e. shell script)</li>
<li>Java</li>
</ul>
</p>
<p>
<b>Androphsy: </b><a href="https://github.com/scorelab/androphsy" target="_blank">https://github.com/scorelab/androphsy</a>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Indeewari Akarawita</li>
<li>Amila Bhagya Perera</li>
</ul></p>
</div>
<br>
<br>
<div id="androphsy-2">
<h2>Proposal 14 : Advanced phonographic content search for Androphsy</h2>
<p>
This module will identify visual phonographic content (i.e. images. Video, documents) and should provide a phonographic URL identification based on URL lookup. Using a URL lookup technique is required as there may be URLs that does not contain any explicit words but real content falls in phonographic category.
<br>
<br>
<b>Required Knowledge: </b>
<ul>
<li>Android platform</li>
<li>Image processing</li>
<li>Java</li>
</ul>
</p>
<p>
<b>Androphsy: </b><a href="https://github.com/scorelab/androphsy" target="_blank">https://github.com/scorelab/androphsy</a>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Indeewari Akarawita</li>
<li>Amila Bhagya Perera</li>
</ul></p>
</div>
<br>
<br>
<div id="androphsy-3">
<h2>Proposal 15 : Unknown binary analysis for Androphsy</h2>
<p>
This module includes several tasks. Initially the module should identify known good binary files, known bad binary files and unknown binary files. This could be done by maintaining a hash value repository of binary files in Android platform. At the moment there is no such up-to-date repository available internet (NSRL does not contain comprehensive list of hashes of Android applications).
After categorization, the module should enable analysis of binary files. Analysis can start by identifying permissions requested by the application. Further binary file decomposable and debug functionality need be developed in this module in order to identify malicious artifacts of the unknown binaries.
<br>
<br>
<b>Required Knowledge: </b>
<ul>
<ul>
<li>Hashing techniques</li>
<li>Android application structure and security model</li>
<li>Java</li>
<li>.apk file decompile</li>
</ul>
</p>
<p>
<b>Androphsy: </b><a href="https://github.com/scorelab/androphsy" target="_blank">https://github.com/scorelab/androphsy</a>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Indeewari Akarawita</li>
<li>Amila Bhagya Perera</li>
</ul></p>
</div>
<br/>
<div id="taxi">
<h2>Proposal 16: Top-k publish/subscribe model for intelligent Taxi allocation</h2>
<p>Publish/subscribe systems are widely recognized in processing continuous queries over data
streams and are augmented by algorithms coming from the field of data stream processing. Existing functions which are capable of matching publications & subscriptions in state-of-the-art publish/subscribe systems are depended on a stateless function which provides only a Boolean decision on whether a given publication is to be notified to relevant subscriber or not. But in such systems, the large quantity of received publications may be considered as a sort of spam, while a system that delivers too few publications might be recognized as non-working.
We have implemented an advanced publish/subscribe matching model to control the unpredictable number of delivered publications over a continuous data-stream, where at a given time t our model limits the number of delivered publications by parameter k, while ranks them within a size w of sliding window. A general scoring mechanism is exploited where publications get scored against personalized user subscription spaces based on the relevancy. We adopt an inverted-list data structure to index the subscription space to enhance the efficiency of matching process. Also we focus on the problem of selecting the k-most diverse items from a relevant result set, in a dynamic setting where Top-k results change over time. An incremental indexing mechanism is proposed for handling streaming publications that is based on Locality Sensitive Hashing (LSH) to diversify Top-k results continuously. Our prototype model is implemented in a cloud based message broker system and we have designed it to scale on top of Amazon Web Services (AWS): a scalable cloud-service provider.</p>
<br>
<p><b>Deliverables:</p></b>
<ul>
<li>Intelligent Taxi allocation</li>
<li>Solve ACM DEBS 2015 Grand Challenge problem based on Top-k publish/subscribe concepts</li>
</ul>
<br/>
<p><b>Skills Needed: </b></p>
<ul>
<li>Basic concepts behind publish/subscribe</li>
<li>Complexity theory</li>
<li>Data-structures & algorithms</li>
</ul>
<br>
<p><b>References:</b><br/>
<a href="http://github.com/SamTube405/EC2PubSubK">http://github.com/SamTube405/EC2PubSubK</a><br>
<a href="http://www.debs2015.org/call-grand-challenge.html">http://www.debs2015.org/call-grand-challenge.html</a></p>
<br>
<p><b>Possible Mentors:</b></p>
<ul><li>Sameera ([email protected])</li></ul>
</div>
<div id="17">
<h2>Proposal 17 : Data acquisition module + screen lock for Androphsy</h2><br/>
<h3>Task 1: Data acquisition module for non-rooted Android smartphones</h3>
<p>The development should enable acquisition of raw evidence from an Android smartphone file system that does not have root access.</p>
<p><b>Required Knowledge:</b></p>
<ul>
<li>Android platform, architecture and security model</li>
<li>Android application development</li>
<li>Java</li>
</ul>
<br/>
<h3>Task 2 : Screen lock – pattern, pin unlock or bypass</h3>
<p>This functionality should bypass or unlock screen lock in form of pattern or pin. In here there are several scenarios to consider. As an instance consider situation device is not rooted, and device is locked at the time of seize. Another easy case is device is rooted and device was unlock at the time of seize.</p>
<p><b>Required Knowledge:</b></p>
<ul>
<li>Android architecture and security model</li>
<li>Android application development</li>
<li>Cryptography knowledge</li>
<li>Matrix manipulation</li>
<li>Java</li>
</ul>
<p>
<b>Androphsy: </b><a href="https://github.com/scorelab/androphsy" target="_blank">https://github.com/scorelab/androphsy</a>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Indeewari Akarawita</li>
<li>Amila Bhagya Perera</li>
</ul></p>
</div>
<br><br>
<div id="18">
<h2>Proposal 18 : Search optimization/Text Indexing + Report Generation for Androphsy</h2><br/>
<h3>Task 1 : Search optimization/Text Indexing</h3>
<p>At the moment Androphsy has a very basic searching facility. It is expected to improve the searching by handling an indexing mechanism. There are opensource text content indexing tools. You are free to decide what will be the best way to improve the search option in tool.</p>
<p>Required knowledge</p>
<ul>
<li>Search optimization/index</li>
<li>Database - MySQL</li>
<li>Java</li>
</ul>
<br/>
<h3>Task 2 : Report Generation</h3><br/>
<p>Androphsy has a very simple report generation module. It will export evidence to a .pdf file. The development is expected to improve the reporting module in terms of below suggestions.
Export evidence in multiple formats including .pdf, .tex,, .html, .xml, .csv
Well formatted report layout: You are free to use any open source reporting library under GNU license. Currently it uses iText.</p>
<p>Report should support not only text, but also images: You are free to modify the existing reporting module in order to give a better solution.</p>
<p><b>Required knowledge:</b></p>
<ul>
<li>Java</li>
<li>Xml,xsl, iText or Jasper etc.</li>
</ul>
<p>
<b>Androphsy: </b><a href="https://github.com/scorelab/androphsy" target="_blank">https://github.com/scorelab/androphsy</a>
</p>
<p><b>Possible Mentors</b>
<ul>
<li>Indeewari Akarawita</li>
<li>Amila Bhagya Perera</li>
</ul></p>
</div>
<br><br>
<div id="19">
<h2>Proposal 19: End-to-End Encryption of Android Phone Calls</h2></br>
<p>Mobile phones are regularly used to discuss sensitive personal and business information. However, little attention is given to the security of these conversations, which can be particularly important for international businessmen. Current encrypted phone call solutions for this problem require either an Internet connection for VOIP or a specialized handset. We want to develop real-time phone encryption module for Android operating system.</p>
<p><a href="http://worldcomp-proceedings.com/proc/p2012/SAM9723.pdf">http://worldcomp-proceedings.com/proc/p2012/SAM9723.pdf</a></p>
</div><br/><br/>
<div id="20">
<h2>Proposal 20: Discriminatively trained deformable part models</h2>
<br/>
<p>Deformable part models is one of the famous object detection approach. Implementation of deformable part models object detection is open-source and accessible to everyone. Implementation include object detection and model learning code, as well as models trained on the PASCAL and INRIA Person datasets. It come with proceder to train models using your own dataset but the problem is building own dataset is very complex process. Objective of this project is developing a tool to building own dataset to trained deformable part models.</p>
<p><b>Reference:</b></p>
<ul><li><a href="http://www.cs.berkeley.edu/~rbg/latent/">http://www.cs.berkeley.edu/~rbg/latent/</a></li>
<li><a href="http://www.cs.berkeley.edu/~rbg/latent/voc-release5-faq.html">http://www.cs.berkeley.edu/~rbg/latent/voc-release5-faq.html</a></li></ul>
</div><br/><br/>
<div id="21">
<h2>Proposal 21: Smartphone Support for People who Stutter</h2>
<p>Stuttering is a very complex speech disorder that
affects around 0.7% of adults while around 5% of the population
have stuttered at some point. A large percentage of the affected
people tend to speak more fluently when their own speech is
played back to their ear with some type of alteration. While
this has been done with special devices, smartphones can be
used for this purpose. We report on our initial experiences on
building such an application and demonstrate problems with
delay caused by the lack of real-time support for audio playback
in the Android operating system. We also discuss ideas for future
work to improve app support for people who stutter.</p>
<br/>
<p><b>Required Knowledge: </b></p>
<ul>
<ul>
<li>Android SDK</li>
<li>Android NDK</li>
<li>Audio Manipulation</li>
</ul>
</div><br/><br/>
<div id="22">
<h2>Proposal 22: PokuruPC configuration for Raspberry Pi 2</h2>
<br/>
<p>Definition :<a href="http://www.ucsc.cmb.ac.lk/PokuruPC">PokuruPC</a></p>
<p>Pokuru-PC was made with adding automseat to popular Ubuntu GNU/linux distribution. Which has been revolutionizing managed desktop computing. We have been tested under different hardware platforms. As GSoC project, we requied to port PokuruPC to Raspberry Pi 2 hardware platform. Pi 2 come up with one HDMI port, Display interface (DSI) and 4 USB ports, it need to configure into two seat.</p>
<p>Source code: <a href="http://automseat.sourceforge.net/">http://automseat.sourceforge.net/</a></p>
<p>Video: <a href="https://www.youtube.com/watch?v=qD4IgIBa-q4">https://www.youtube.com/watch?v=qD4IgIBa-q4</a></p>
<img src="../images/pokuru.png">
</div>
<br/><br/>
<div id="23">
<h2>Proposal 23: Developing query parser for Senze language</h2>
<p>
Main component of the MySensors platform is the Senzes which are very similar to twitter messages. These Senzes can be used to build various applications and integrated into the existing systems. Senzes are capable of expressing any kind of sensing to the target devices. In this project we want to develop dynamic generator and parser for Senzes language queries and responses.
</p>
<br/>
<p><b>Required Knowledge: </b></p>
<ul>
<ul>
<li>Java</li>
<li>Python</li>
<li>JavaScript</li>
<li>Lanuage Grammer Deasign</li>
</ul>
<br/><br/>
<p><b>Reference:</b></p>
<ul><li><a href="http://www.mysensors.info">http://www.mysensors.info</a></li>
<li><a href="http://www.mysensors.info/API/#senzes ">http://www.mysensors.info/API/#senzes</a></li></ul>
</div><br/><br/>
<div id="24">
<h2>Proposal 24: BASSA-Automated download queue</h2>
<br/>
<p>Bassa is a download queue where users can log in and submit their download as a link or torrent magnet link. Then Bassa will automatically download it in the night time and will inform the user that his/her download is ready. Then the downloaded files will reside in local server for limited amount of time based on other user’s ratings, so anyone in the same organization can get the file without downloading it again.
Then after some time Bass will automatically remove the old files from server.</p>
<br/>
<p><b>Required Knowledge: </b></p>
<ul>
<li>C++</li>
<li>PHP</li>
<li>Angular JS</li>
<li>MongoDB</li>
<li>MySQL</li>
</ul>
</div>
</section>
</div>
</div>
</div>
</div>
<!-- /Main -->