mirror of
https://github.com/CoderSherlock/CoderSherlock.github.io.git
synced 2026-06-13 08:08:10 -07:00
Adding_Google_Analytic
This commit is contained in:
+57
-2
@@ -6,10 +6,65 @@
|
||||
</description>
|
||||
<link>https://codersherlock.github.com//</link>
|
||||
<atom:link href="https://codersherlock.github.com//feed.xml" rel="self" type="application/rss+xml"/>
|
||||
<pubDate>Thu, 27 Oct 2016 01:09:32 -0400</pubDate>
|
||||
<lastBuildDate>Thu, 27 Oct 2016 01:09:32 -0400</lastBuildDate>
|
||||
<pubDate>Mon, 31 Oct 2016 17:08:36 -0400</pubDate>
|
||||
<lastBuildDate>Mon, 31 Oct 2016 17:08:36 -0400</lastBuildDate>
|
||||
<generator>Jekyll v3.0.1</generator>
|
||||
|
||||
<item>
|
||||
<title>Some of my previews experiment works</title>
|
||||
<description><h1 id="time-series">Time series</h1>
|
||||
|
||||
<h2 id="section">2016-10</h2>
|
||||
|
||||
<h3 id="time-experiment-of-rsync">Time Experiment of rsync</h3>
|
||||
|
||||
<p>Patch is based on rsync with version 3.1.2. [<a href="https://download.samba.org/pub/rsync/rsync-3.1.2.tar.gz">Rsync</a>|<a href="/static/2016-10/rsync/rsync-3.1.2-time.patch">Patch</a>]</p>
|
||||
|
||||
<h4 id="how-to-collect-data">How to collect data</h4>
|
||||
|
||||
<p>Basically, everything of transmission time and computation time will be output with overall time will be printed on the console.<br />
|
||||
But we also need some bash script to collect data through different size of random size and with different modification through them.</p>
|
||||
|
||||
<ul>
|
||||
<li>Start from 8K to 64M, modify at beginning, [<a href="/static/2016-10/rsync/small2Big_change_at_begin.sh">Bash script</a>]</li>
|
||||
<li>Start from 8K to 64M, modify at last, [<a href="/static/2016-10/rsync/small2Big_change_at_last.sh">Bash script</a>]</li>
|
||||
<li>Start from 8K to 64M, modify at random place with a (slow) python script, [<a href="/static/2016-10/rsync/small2Big_change_at_anyplace.sh">Bash script</a>|<a href="/static/2016-10/rsync/addbyte.py">Python program</a>]</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="time-experiment-of-seafile">Time Experiment of seafile</h3>
|
||||
|
||||
</description>
|
||||
<pubDate>Fri, 28 Oct 2016 12:27:33 -0400</pubDate>
|
||||
<link>https://codersherlock.github.com//archivers/some-of-my-previews-exper-work</link>
|
||||
<guid isPermaLink="true">https://codersherlock.github.com//archivers/some-of-my-previews-exper-work</guid>
|
||||
|
||||
|
||||
<category>Research</category>
|
||||
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<title>Using charles proxy to monitor mobile SSL traffics</title>
|
||||
<description><p>In this blog, I will generally talk about how to use proper tools to monitor SSL traffics of a mobile devices. Currently, I only can dealing with those SSL traffics which use an obviously certification. Some applications may not using system root cert or they doesn’t provide us a method to modify their own certs. For these situation, I still didn’t find a good solutions for it. But I’ll keep updating this if I get one. <br />
|
||||
My current solution is using AP to forward all SSL traffic to a proxy, <a href="https://www.charlesproxy.com/">charles proxy</a> is my first choice (Prof asked). It’s a non-free software which still update new versions now. So mainly, I’ll talk about how to charles SSL proxy.</p>
|
||||
|
||||
<h3 id="preparations">Preparations</h3>
|
||||
<ul>
|
||||
<li>Monitor device situation: Linux Machine with wireless adapter</li>
|
||||
<li>Download the newest version(4.0.1) of charles</li>
|
||||
<li>Target android devices with root privilege</li>
|
||||
</ul>
|
||||
|
||||
</description>
|
||||
<pubDate>Thu, 27 Oct 2016 22:50:33 -0400</pubDate>
|
||||
<link>https://codersherlock.github.com//archivers/charles-is-not-a-good-tool</link>
|
||||
<guid isPermaLink="true">https://codersherlock.github.com//archivers/charles-is-not-a-good-tool</guid>
|
||||
|
||||
|
||||
<category>Network</category>
|
||||
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<title>Stop Talking is the worst title of one blog</title>
|
||||
<description>
|
||||
|
||||
Reference in New Issue
Block a user