wiki:TipAndDoc/network/Chrome

Version 35 (modified by mitty, 6 years ago) (diff)

--

  1. Google Chrome
  2. Extensions
  3. SQLite

Google Chrome

  • UltraMonが有効にならない
  • Smart Taskとも相性が悪い
    • Chromeウィンドウをサブディスプレイに移動しても、メインの(通常の)タスクバーにボタンが残る
    • アイコンがおかしくなる
  • Win+Dで最小化・最大化すると変なフローティングウィンドウが残る
  • chrome://flags/#password-autofill-public-suffix-domain-matching

    同じパブリック サフィックス登録ドメインに一致するドメインに対して、ユーザーがユーザー名/パスワードの組み合わせを選択できる機能を有効または無効にします。

    • サブドメインごとにアカウントを違えていても、同じアカウントが提示されるため認証できなくなることがあるので注意を要する模様
    • ​Google Chrome's password autofill to receive new feature | gHacks Technology News

      So, if username and password are stored for www.facebook.com, the browser will now suggested the same user account on other Facebook sub-domains. It displays the information once you start to type the first letter of the username, and will display the domain it has been saved for. It seems possible to currently match sub-domains with each other, at least on Facebook. So, a saved password for ​http://m.facebook.com/ works also on ​http://touch.facebook.com/.

  • ​俺のChrome - クソうざい通知と購読を葬る
    1. Google Chromeを起動する
    2. ロケーションバーにchrome://flags/を入力してシステム設定画面を出す
    3. 検索窓にservice workersと入力して検索する
    4. Servicified service workersのDefaultをDeisabledに変更する

「service worker」で出てくるので全部Disabledにする

  1. どのタブでもいいので「Shift」+「Ctrl」+「I」を叩く（Macなら「Opt」「cmd」「I」）
  2. デベロッパーツールが開くので「Application」を選択する
  3. 左側の「Service Workers」をクリックする
  4. 右側にすでにインストールされたゴミクズ（サービスワーカー）が表示される（表示されてなかったら「Servie Wotkers from other domains」を開く）
  5. ドメインごとに表示されるので「Unregister」で一つ一つ葬る

Extensions

SQLite

  • ​http://log2timeline.net/

    a framework for automatic creation of a super timeline. The main purpose is to provide a single tool to parse various log files and artifacts found on suspect systems (and supporting systems, such as network equipment) and produce a timeline that can be analysed by forensic investigators/analysts.

  • Archived History 
    sqlite> .schema
CREATE TABLE keyword_search_terms (keyword_id INTEGER NOT NULL,url_id INTEGER NOT NULL,lower_term LONGVARCHAR NOT NULL,term LONGVARCHAR NOT NULL);
CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY,value LONGVARCHAR);
CREATE TABLE urls(id INTEGER PRIMARY KEY,url LONGVARCHAR,title LONGVARCHAR,visit_count INTEGER DEFAULT 0 NOT NULL,typed_count INTEGER DEFAULT 0 NOT NULL,last_visit_time INTEGER NOT NULL,hidden INTEGER DEFAULT 0 NOT NULL,favicon_id INTEGER DEFAULT 0 NOT NULL);
CREATE TABLE visit_source(id INTEGER PRIMARY KEY,source INTEGER NOT NULL);
CREATE TABLE visits(id INTEGER PRIMARY KEY,url INTEGER NOT NULL,visit_time INTEGER NOT NULL,from_visit INTEGER,transition INTEGER DEFAULT 0 NOT NULL,segment_id INTEGER,is_indexed BOOLEAN);
CREATE INDEX keyword_search_terms_index1 ON keyword_search_terms (keyword_id, lower_term);
CREATE INDEX keyword_search_terms_index2 ON keyword_search_terms (url_id);
CREATE INDEX urls_url_index ON urls (url);
CREATE INDEX visits_from_index ON visits (from_visit);
CREATE INDEX visits_time_index ON visits (visit_time);
CREATE INDEX visits_url_index ON visits (url);
  • History 
    sqlite> .schema
CREATE TABLE downloads (id INTEGER PRIMARY KEY,full_path LONGVARCHAR NOT NULL,url LONGVARCHAR NOT NULL,start_time INTEGER NOT NULL,received_bytes INTEGER NOT NULL,total_bytes INTEGER NOT NULL,state INTEGER NOT NULL, end_time INTEGER NOT NULL DEFAULT 0, opened INTEGER NOT NULL DEFAULT 0);
CREATE TABLE keyword_search_terms (keyword_id INTEGER NOT NULL,url_id INTEGER NOT NULL,lower_term LONGVARCHAR NOT NULL,term LONGVARCHAR NOT NULL);
CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY,value LONGVARCHAR);
CREATE TABLE presentation(url_id INTEGER PRIMARY KEY,pres_index INTEGER NOT NULL);
CREATE TABLE segment_usage (id INTEGER PRIMARY KEY,segment_id INTEGER NOT NULL,time_slot INTEGER NOT NULL,visit_count INTEGER DEFAULT 0 NOT NULL);
CREATE TABLE segments (id INTEGER PRIMARY KEY,name VARCHAR,url_id INTEGER NON NULL,pres_index INTEGER DEFAULT -1 NOT NULL);
CREATE TABLE "urls"(id INTEGER PRIMARY KEY,url LONGVARCHAR,title LONGVARCHAR,visit_count INTEGER DEFAULT 0 NOT NULL,typed_count INTEGER DEFAULT 0 NOT NULL,last_visit_time INTEGER NOT NULL,hidden INTEGER DEFAULT 0 NOT NULL,favicon_id INTEGER DEFAULT 0 NOT NULL);
CREATE TABLE visit_source(id INTEGER PRIMARY KEY,source INTEGER NOT NULL);
CREATE TABLE visits(id INTEGER PRIMARY KEY,url INTEGER NOT NULL,visit_time INTEGER NOT NULL,from_visit INTEGER,transition INTEGER DEFAULT 0 NOT NULL,segment_id INTEGER,is_indexed BOOLEAN);
CREATE INDEX keyword_search_terms_index1 ON keyword_search_terms (keyword_id, lower_term);
CREATE INDEX keyword_search_terms_index2 ON keyword_search_terms (url_id);
CREATE INDEX segment_usage_time_slot_segment_id ON segment_usage(time_slot, segment_id);
CREATE INDEX segments_name ON segments(name);
CREATE INDEX segments_url_id ON segments(url_id);
CREATE INDEX segments_usage_seg_id ON segment_usage(segment_id);
CREATE INDEX urls_favicon_id_INDEX ON urls (favicon_id);
CREATE INDEX urls_url_index ON urls (url);
CREATE INDEX visits_from_index ON visits (from_visit);
CREATE INDEX visits_time_index ON visits (visit_time);
CREATE INDEX visits_url_index ON visits (url);
  • History Index YYYY-MM 
    sqlite> .schema
CREATE TABLE info(time INTEGER NOT NULL);
CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY,value LONGVARCHAR);
CREATE VIRTUAL TABLE pages USING fts3(TOKENIZE icu,url LONGVARCHAR,title LONGVARCHAR,body LONGVARCHAR);
CREATE TABLE pages_content(  docid INTEGER PRIMARY KEY,c0url, c1title, c2body);
CREATE TABLE pages_segdir(  level integer,  idx integer,  start_block integer,  leaves_end_block integer,  end_block integer,  root blob,  primary key(level, idx));
CREATE TABLE pages_segments(  blockid INTEGER PRIMARY KEY,  block blob);
CREATE INDEX info_time ON info(time);
    • ICU対応のsqlite3をビルドしないとdump出来ないので注意

Attachments (4)

Download all attachments as: .zip