[過去ログ] Let's talk with Jim-san. Part24 (1001レス)
1-
抽出解除 レス栞

このスレッドは過去ログ倉庫に格納されています。
次スレ検索 歴削→次スレ 栞削→次スレ 過去ログメニュー
9
(3): Code Monkey ★ 2014/02/21(金)23:01 ID:??? AAS
>>8
Please wait a moment, I will show you what the database on the ninja server looks like.
10
(2): Code Monkey ★ 2014/02/21(金)23:05 ID:??? AAS
mysql> select * from chinabokan limit 10;

+----------------------------+------------+------+------+------+------+------+------+------------+
| key01 | c00 | c01 | c02 | c03 | c04 | c05 | c06 | c07 |
+----------------------------+------------+------+------+------+------+------+------+------------+
| Danime1375007498009176 | 1392817967 | 1 | | | | | | 1392819720 |
| Dnews4vip1380885646980424 | 1392964900 | 1 | | | | | | 1392965132 |
| Dnewsplus1381114018595306 | 1391404375 | 1 | | | | | | 1391404654 |
| Dasaloon1366703879331048 | 1392855065 | 1 | | | | | | 1392911130 |
| Dgiin1382514070691111 | 1392825876 | 1 | | | | | | 1392825920 |
| Dnews4vip1390903669734016 | 1392962047 | 1 | | | | | | 1392964176 |
省5
11
(2): Code Monkey ★ 2014/02/21(金)23:06 ID:??? AAS
It is just the Ninja Id, post time stamp, ninja dan (I think?), and current server timestamp.
17
(4): Code Monkey ★ 2014/02/21(金)23:23 ID:??? AAS
>>15
I could not find anything else.
If there is anything else, then it is hidden very well!

Only one script has been updated since 2011 when FOX made the system.
Tomorrow, I will read through every line of that script to make sure its not hiding a log somewhere.
18
(2): Code Monkey ★ 2014/02/21(金)23:24 ID:??? AAS
>>17
I made an error. There are more scripts that have been updated, but I can only see one critical script that has been updated recently.
30
(1): Code Monkey ★ 2014/02/21(金)23:53 ID:??? AAS
>>26
The .dat files only contain what you can already see in your browser.
35
(2): Code Monkey ★ 2014/02/21(金)23:54 ID:??? AAS
>>29
Why has it stopped?
68
(1): Code Monkey ★ 2014/02/22(土)00:41 ID:??? AAS
>>59
Please wait a little bit longer for the SSL certificate.
75: Code Monkey ★ 2014/02/22(土)00:57 ID:??? AAS
>>71
Sorry. The script probably picked up some other edge cases also.
81
(1): Code Monkey ★ 2014/02/22(土)01:15 ID:??? AAS
If you guys can give me an idea about where the suspected ninja logs are located, then it would help a lot in my search for them.
91
(2): Code Monkey ★ 2014/02/22(土)01:30 ID:??? AAS
Im going to sleep now. Have a good evening.
278
(2): Code Monkey ★ 2014/02/22(土)12:14 ID:??? AAS
>>174
Okay I will look for a zipped text file that might contain logged data.
Ill tell you if I find it or not.
388
(1): Code Monkey ★ 2014/02/22(土)14:14 ID:??? AAS
Okay I found something strange about the NINJA system.
My plan is to revert the 2ch NINJA system to be the same as BBSPINK's ninja system.
397
(4): Code Monkey ★ 2014/02/22(土)14:27 ID:??? AAS
>>392
I found a bunch of changes to the 2ch NINJA code that do not exist on the bbspink NINJA code.

Specifically this line looks dangerous to me:
外部リンク:<url_removed>?remo=$remo&host=$ENV{REMOTE_ADDR}&maru=$GB->{MARUX}&ota=$GB->{MARUOTA}&ua=$ENV{'HTTP_USER_AGENT'}.......

If you are using NINJA, then it is sending your IP, maru ID, user agent, and all your other identifying information to a special server.
Next I will check that special server to see what it is doing with your data.

I recommend you do not use NINJA on 2ch until I have fixed this problem.
436
(2): Code Monkey ★ 2014/02/22(土)15:25 ID:??? AAS
Okay I found out what the "special server" is doing.

It has a redis nosql server running.
The server is storing the data of every ninja ID and it's IP address.
The data looks like this (I have censored this person's IP and ninja ID):

1393050109.683551 (db 3) "SELECT" "3"
1393050109.683616 (db 3) "EXISTS" "Dfamicom1111111111111111"
1393050109.683686 (db 2) "SELECT" "2"
1393050109.683749 (db 2) "EXISTS" "111.87.58.xxx"
1393050109.683818 (db 2) "SADD" "111.87.58.xxx" "Dfamicom111111111111111"
1393050109.683889 (db 2) "EXPIRE" "111.87.58.xxx" "3600"
省1
438
(1): Code Monkey ★ 2014/02/22(土)15:27 ID:??? AAS
>>435
We will give each board the option to enable or disable captcha via the SETTING.TXT file.
443
(3): Code Monkey ★ 2014/02/22(土)15:30 ID:??? AAS
I still dont think there is enough information being logged by NINJA to allow for a data leak.
What do you think?
459
(3): Code Monkey ★ 2014/02/22(土)15:43 ID:??? AAS
Regarding possible compressed archives on the NINJA server. This is what I have found.
I will move them all off the ninja server and onto an external secured server.

tiger3558# find / -name "*.tar"
/home/admin/ch2ninja_sql.tar
/home/admin/tmp/db.tar
/home/admin/mysql_back/110608.tar
/home/admin/sql_backup.tar
/home/ch2ninja/2chbg.tar
/home/ch2ninja/2chboo.tar
/home/ch2ninja/2chimg.tar
省9
461
(7): Code Monkey ★ 2014/02/22(土)15:49 ID:??? AAS
Here is some more information about the sizes and creation dates of these logs:

1.5G Feb 23 2012 /hd/ch2ninja_120224.tar
4.3G Feb 23 2012 /hd/ch2ninja_sql_120224.tar
4.2G Feb 23 2012 /hd/chinabokan.tar
4.3G Feb 23 2012 /hd/mysql.tar
8.1M Feb 21 2011 /home/admin/ch2ninja_sql.tar
68M Jun 8 2011 /home/admin/mysql_back/110608.tar
1.6G Nov 28 2011 /home/admin/sql_backup.tar
251K Jul 16 2011 /home/admin/tmp/db.tar
168K Feb 8 2011 /home/ch2ninja/2chbg.tar
省15
489
(3): Code Monkey ★ 2014/02/22(土)16:13 ID:??? AAS
>>480
There is possibility.
I have not opened these files, I dont know what is in them.
I will remove them from the server so that they cannot be leaked in the future.
1-
スレ情報 赤レス抽出 画像レス抽出 歴の未読スレ AAサムネイル

ぬこの手 ぬこTOP 0.050s