Jengyic's 正義部落

從 NCBI 的 BLASTN 對武漢肺炎冠狀病毒基因序列的小小觀察

2020-01-28T01:21:00.001+08:00

一開始本來只是想看看冠狀病毒的 DNA 序列和 SARS 的差異.
不過似乎從搜尋工具沒辦法直接做到這點, 所以就從 wuhan 開始吧.

https://www.ncbi.nlm.nih.gov/nuccore/?term=wuhan

選擇用 Viruses 過濾, 從 3. 4. 看到重點了.

Wuhan seafood market pneumonia virus isolate Wuhan-Hu-1, complete genome

29,903 bp linear RNA

Accession:: MN908947.3
GI:: 1798172431

Assembly Protein Taxonomy

GenBank FASTA Graphics

Wuhan seafood market pneumonia virus isolate Wuhan-Hu-1, complete genome

29,903 bp linear RNA

Accession:: NC_045512.2
GI:: 1798174254

Assembly BioProject Protein Taxonomy

GenBank FASTA Graphics

這不就是熱騰騰的全基因體序列, 得來全不費功夫.
重點這是海鮮市場的, 就是這場瘟疫的重點之一.
至於起點, 直到今日(01/28)還全無頭緒.

接下來就用 3. 4. 進行 BLASTN https://blast.ncbi.nlm.nih.gov/Blast.cgi
請輸入 MN908947.3 |NC_045512.2 (分兩行), 使用 Highly similar sequences (megablast)
因為病毒基因體只有 29.9kb 左右, 所以迅速找到相似的序列.

Select for downloading or viewing reports	Description	Max Score	Total Score	Query Cover	Per. Ident	Accession
Select seq MG772933.1	Bat SARS-like coronavirus isolate bat-SL-CoVZC45, complete genome	26943	35336	95%	89.12%	MG772933.1
Select seq MG772934.1	Bat SARS-like coronavirus isolate bat-SL-CoVZXC21, complete genome	22223	35276	94%	88.65%	MG772934.1
Select seq AY395003.1	SARS coronavirus ZS-C, complete genome	15213	22564	88%	82.34%	AY395003.1
Select seq AY394996.1	SARS coronavirus ZS-B, complete genome	15213	22600	88%	82.34%	AY394996.1
Select seq AY304488.1	SARS coronavirus SZ16, complete genome	15202	22531	88%	82.33%	AY304488.1
Select seq AY304486.1	SARS coronavirus SZ3, complete genome	15202	22529	88%	82.33%	AY304486.1
Select seq AY390556.1	SARS coronavirus GZ02, complete genome	15191	22548	88%	82.32%	AY390556.1
Select seq EU371564.1	SARS coronavirus BJ182-12, complete genome	15186	22483	88%	82.32%	EU371564.1
Select seq AY394985.1	SARS coronavirus HSZ-Bb, complete genome	15186	22276	87%	82.31%	AY394985.1
Select seq AY278554.2	SARS coronavirus CUHK-W1, complete genome	15186	22577	88%	82.32%	AY278554.2
Select seq EU371559.1	SARS coronavirus ZJ02, complete genome	15180	22548	88%	82.31%	EU371559.1
Select seq AY559093.1	SARS coronavirus Sin845, complete genome	15180	22507	88%	82.31%	AY559093.1
Select seq AY394994.1	SARS coronavirus HSZ-Bc, complete genome	15180	22566	88%	82.31%	AY394994.1
Select seq AY394986.1	SARS coronavirus HSZ-Cb, complete genome	15180	22526	88%	82.31%	AY394986.1
Select seq MK211376.1	Coronavirus BtRs-BetaCoV/YN2018B, complete genome	15176	22618	91%	82.32%	MK211376.1
Select seq KY417146.1	Bat SARS-like coronavirus isolate Rs4231, complete genome	15176	22534	91%	82.30%	KY417146.1
Select seq JX163927.1	SARS coronavirus isolate Tor2/FP1-10851, complete genome	15175	22417	88%	82.30%	JX163927.1
Select seq JX163926.1	SARS coronavirus isolate Tor2/FP1-10912, complete genome	15175	22424	88%	82.30%	JX163926.1
Select seq JX163923.1	SARS coronavirus isolate Tor2/FP1-10912, complete genome	15175	22417	88%	82.30%	JX163923.1
Select seq JQ316196.1	SARS coronavirus HKU-39849 isolate UOB, complete genome	15175	22529	88%	82.30%	JQ316196.1
Select seq FJ882963.1	SARS coronavirus P2, complete genome	15175	22450	88%	82.30%	FJ882963.1
Select seq DQ898174.1	SARS coronavirus strain CV7, complete genome	15175	22574	88%	82.30%	DQ898174.1
Select seq AY864806.1	SARS coronavirus BJ202, complete genome	15175	22579	88%	82.30%	AY864806.1
Select seq AY714217.1	SARS Coronavirus CDC#200301157, complete genome	15175	22529	88%	82.30%	AY714217.1
Select seq AY559096.1	SARS coronavirus Sin850, complete genome	15175	22516	88%	82.30%	AY559096.1
Select seq AY559095.1	SARS coronavirus Sin847, complete genome	15175	22504	88%	82.30%	AY559095.1
Select seq AY559086.1	SARS coronavirus Sin849, complete genome	15175	22502	88%	82.30%	AY559086.1
Select seq AY559085.1	SARS coronavirus Sin848, complete genome	15175	22504	88%	82.30%	AY559085.1
Select seq AY559084.1	SARS coronavirus Sin3765V, complete genome	15175	22526	88%	82.30%	AY559084.1
Select seq AY559083.1	SARS coronavirus Sin3408, complete genome	15175	22513	88%	82.30%	AY559083.1
Select seq AY559082.1	SARS coronavirus Sin852, complete genome	15175	22502	88%	82.30%	AY559082.1
Select seq AY274119.3	Severe acute respiratory syndrome-related coronavirus isolate Tor2, complete genome	15175	22568	88%	82.30%	AY274119.3
Select seq AY323977.2	SARS coronavirus HSR 1, complete genome	15175	22579	88%	82.30%	AY323977.2
Select seq AY291451.1	SARS coronavirus TW1, complete genome	15175	22539	88%	82.30%	AY291451.1
Select seq AY502928.1	SARS coronavirus TW5, complete genome	15175	22533	88%	82.30%	AY502928.1
Select seq AY502926.1	SARS coronavirus TW3, complete genome	15175	22526	88%	82.30%	AY502926.1
Select seq AY502923.1	SARS coronavirus TW10, complete genome	15175	22539	88%	82.30%	AY502923.1
Select seq AY394999.1	SARS coronavirus LC2, complete genome	15175	22511	88%	82.30%	AY394999.1
Select seq AY394998.1	SARS coronavirus LC1, complete genome	15175	22561	88%	82.30%	AY394998.1
Select seq AY394995.1	SARS coronavirus HSZ-Cc, complete genome	15175	22555	88%	82.30%	AY394995.1
Select seq AY394993.1	SARS coronavirus HGZ8L2, complete genome	15175	22561	88%	82.31%	AY394993.1
Select seq AY394992.1	SARS coronavirus HZS2-C, complete genome	15175	22566	88%	82.31%	AY394992.1
Select seq AY394991.1	SARS coronavirus HZS2-Fc, complete genome	15175	22566	88%	82.30%	AY394991.1
Select seq AY394987.1	SARS coronavirus HZS2-Fb, complete genome	15175	22548	88%	82.30%	AY394987.1
Select seq AY394983.1	SARS coronavirus HSZ2-A, complete genome	15175	22535	88%	82.30%	AY394983.1
Select seq AY394978.1	SARS coronavirus GZ-B, complete genome	15175	22461	88%	82.30%	AY394978.1
Select seq AY357075.1	SARS coronavirus PUMC02, complete genome	15175	22563	88%	82.30%	AY357075.1
Select seq AY282752.2	SARS coronavirus CUHK-Su10, complete genome	15175	22561	88%	82.30%	AY282752.2
Select seq AY427439.1	SARS coronavirus AS, complete genome	15175	22522	88%	82.30%	AY427439.1
Select seq AY283796.1	SARS coronavirus Sin2679, complete genome	15175	22528	88%	82.30%	AY283796.1
Select seq AP006561.1	SARS coronavirus TWY genomic RNA, complete genome	15175	22535	88%	82.30%	AP006561.1
Select seq JX163925.1	SARS coronavirus isolate Tor2/FP1-10895, complete genome	15173	22415	88%	82.30%	JX163925.1
Select seq JX163928.1	SARS coronavirus isolate Tor2/FP1-10895, complete genome	15171	22424	88%	82.30%	JX163928.1
Select seq JX163924.1	SARS coronavirus isolate Tor2/FP1-10851, complete genome	15169	22420	88%	82.30%	JX163924.1
Select seq GU553363.1	SARS coronavirus HKU-39849 isolate TCVSP-HARROD-00001, complete genome	15169	22415	88%	82.30%	GU553363.1
Select seq EU371563.1	SARS coronavirus BJ182-8, complete genome	15169	22504	88%	82.30%	EU371563.1
Select seq EU371561.1	SARS coronavirus BJ182b, complete genome	15169	22509	88%	82.30%	EU371561.1
Select seq EU371560.1	SARS coronavirus BJ182a, complete genome	15169	22509	88%	82.30%	EU371560.1
Select seq AY864805.1	SARS coronavirus BJ162, complete genome	15169	22574	88%	82.30%	AY864805.1
Select seq AY278741.1	SARS coronavirus Urbani, complete genome	15169	22535	88%	82.30%	AY278741.1
Select seq AY559087.1	SARS coronavirus Sin3725V, complete genome	15169	22518	88%	82.29%	AY559087.1
Select seq AY394989.1	SARS coronavirus HZS2-D, complete genome	15169	22561	88%	82.30%	AY394989.1
Select seq AY485278.1	SARS coronavirus Sino3-11, complete genome	15169	22546	88%	82.30%	AY485278.1
Select seq AY502927.1	SARS coronavirus TW4, complete genome	15167	22526	88%	82.29%	AY502927.1
Select seq GU553365.1	SARS coronavirus HKU-39849 isolate TCVSP-HARROD-00003, complete genome	15165	22406	88%	82.29%	GU553365.1
Select seq KJ473816.1	BtRs-BetaCoV/YN2013, complete genome	15163	21673	85%	82.29%	KJ473816.1
Select seq EU371562.1	SARS coronavirus BJ182-4, complete genome	15158	22498	88%	82.29%	EU371562.1
Select seq MK211377.1	Coronavirus BtRs-BetaCoV/YN2018C, complete genome	15149	22403	88%	82.29%	MK211377.1
Select seq KY417145.1	Bat SARS-like coronavirus isolate Rf4092, complete genome	15134	22372	86%	82.26%	KY417145.1
Select seq MK211375.1	Coronavirus BtRs-BetaCoV/YN2018A, complete genome	15117	22368	88%	82.26%	MK211375.1
Select seq KF294455.1	SARS-related bat coronavirus isolate Anlong-111 orf1ab polyprotein and orf1a polyprotein genes, complete cds	15084	16332	64%	82.35%	KF294455.1
Select seq JX993988.1	Bat coronavirus Cp/Yunnan2011, complete genome	15043	21834	86%	82.18%	JX993988.1
Select seq KJ473814.1	BtRs-BetaCoV/HuB2013, complete genome	14970	22339	87%	82.20%	KJ473814.1
Select seq DQ648857.1	Bat coronavirus (BtCoV/279/2005), complete genome	14916	22163	87%	82.16%	DQ648857.1
Select seq JX993987.1	Bat coronavirus Rp/Shaanxi2011, complete genome	14892	21819	88%	82.00%	JX993987.1
Select seq KF294457.1	SARS-related bat coronavirus isolate Longquan-140 orf1ab polyprotein, spike glycoprotein, envelope protein, membrane protein, and nucleocapsid protein genes, complete cds	14759	23767	91%	81.89%	KF294457.1
Select seq MK211374.1	Coronavirus BtRl-BetaCoV/SC2018, complete genome	14731	21836	87%	82.02%	MK211374.1
Select seq KJ473813.1	BtRf-BetaCoV/SX2013, complete genome	14722	21360	87%	81.82%	KJ473813.1
Select seq KJ473812.1	BtRf-BetaCoV/HeB2013, complete genome	14683	21261	86%	81.79%	KJ473812.1
Select seq KJ473811.1	BtRf-BetaCoV/JL2012, complete genome	14683	21067	86%	81.79%	KJ473811.1
Select seq GQ153542.1	Bat SARS coronavirus HKU3-7, complete genome	14683	21958	88%	81.82%	GQ153542.1
Select seq GQ153543.1	Bat SARS coronavirus HKU3-8, complete genome	14678	21996	88%	81.82%	GQ153543.1
Select seq KY770860.1	Bat coronavirus isolate Jiyuan-84, complete genome	14628	21416	87%	81.74%	KY770860.1
Select seq DQ648856.1	Bat coronavirus (BtCoV/273/2005), complete genome	14556	21386	87%	81.66%	DQ648856.1
Select seq DQ412042.1	Bat SARS coronavirus Rf1, complete genome	14556	21394	87%	81.66%	DQ412042.1
Select seq GQ153547.1	Bat SARS coronavirus HKU3-12, complete genome	14550	21830	88%	81.68%	GQ153547.1
Select seq KF294456.1	SARS-related bat coronavirus isolate Jiyuan-331 orf1ab polyprotein gene, complete cds	14539	15829	66%	81.66%	KF294456.1
Select seq FJ211859.1	Recombinant coronavirus clone Bat SARS-CoV, complete sequence	14517	21878	89%	81.65%	FJ211859.1
Select seq DQ084199.1	bat SARS coronavirus HKU3-2, complete genome	14512	21810	88%	81.64%	DQ084199.1
Select seq GQ153540.1	Bat SARS coronavirus HKU3-5, complete genome	14506	21791	88%	81.63%	GQ153540.1
Select seq GQ153539.1	Bat SARS coronavirus HKU3-4, complete genome	14506	21797	88%	81.63%	GQ153539.1
Select seq GQ153546.1	Bat SARS coronavirus HKU3-11, complete genome	14501	21780	88%	81.63%	GQ153546.1
Select seq DQ022305.2	Bat SARS coronavirus HKU3-1, complete genome	14501	21863	89%	81.63%	DQ022305.2
Select seq DQ084200.1	bat SARS coronavirus HKU3-3, complete genome	14501	21849	89%	81.63%	DQ084200.1
Select seq GQ153548.1	Bat SARS coronavirus HKU3-13, complete genome	14495	21769	88%	81.63%	GQ153548.1
Select seq GQ153541.1	Bat SARS coronavirus HKU3-6, complete genome	14495	21797	88%	81.62%	GQ153541.1
Select seq GQ153545.1	Bat SARS coronavirus HKU3-10, complete genome	14484	21758	88%	81.61%	GQ153545.1
Select seq GQ153544.1	Bat SARS coronavirus HKU3-9, complete genome	14484	21758	88%	81.61%	GQ153544.1
Select seq KU182964.1	Bat coronavirus isolate JTMC15, complete genome	13501	20280	79%	82.94%	KU182964.1
Select seq KY938558.1	Bat coronavirus strain 16BO133, complete genome	13452	20206	79%	82.88%	KY938558.1

使用圖形化顯示

Distribution of the top 200 Blast Hits on 100 subject sequences

Query

1

5500

11000

16500

22000

27500

發現武漢海鮮市場樣本大致上包含第一與第二筆, 但是有一段卻多出來了.
那一段大概在 22000 ~ 23400 約 1400 bps.

此時調出武漢海鮮市場樣本 01/23 的較新版全基因體
https://www.ncbi.nlm.nih.gov/nuccore/MN908947.3

找出 22000 ~ 23400 序列.
aaaaacaacaaaagttggatggaaagtgagttcagagtttattctagtgcgaataattgcacttttgaatatgtctctcagccttttcttatggaccttgaaggaaaacagggtaatttcaaaaatcttagggaatttgtgtttaagaatattgatggttattttaaaatatattctaagcacacgcctattaatttagtgcgtgatctccctcagggtttttcggctttagaaccattggtagatttgccaataggtattaacatcactaggtttcaaactttacttgctttacatagaagttatttgactcctggtgattcttcttcaggttggacagctggtgctgcagcttattatgtgggttatcttcaacctaggacttttctattaaaatataatgaaaatggaaccattacagatgctgtagactgtgcacttgaccctctctcagaaacaaagtgtacgttgaaatccttcactgtagaaaaaggaatctatcaaacttctaactttagagtccaaccaacagaatctattgttagatttcctaatattacaaacttgtgcccttttggtgaagtttttaacgccaccagatttgcatctgtttatgcttggaacaggaagagaatcagcaactgtgttgctgattattctgtcctatataattccgcatcattttccacttttaagtgttatggagtgtctcctactaaattaaatgatctctgctttactaatgtctatgcagattcatttgtaattagaggtgatgaagtcagacaaatcgctccagggcaaactggaaagattgctgattataattataaattaccagatgattttacaggctgcgttatagcttggaattctaacaatcttgattctaaggttggtggtaattataattacctgtatagattgtttaggaagtctaatctcaaaccttttgagagagatatttcaactgaaatctatcaggccggtagcacaccttgtaatggtgttgaaggttttaattgttactttcctttacaatcatatggtttccaacccactaatggtgttggttaccaaccatacagagtagtagtactttcttttgaacttctacatgcaccagcaactgtttgtggacctaaaaagtctactaatttggttaaaaacaaatgtgtcaatttcaacttcaatggtttaacaggcacaggtgttcttactgagtctaacaaaaagtttctgcctttccaacaatttggcagagacattgctgacactactgatgctgtccgtgatccacagacacttgagattcttgacattacaccatgttcttttggtggtgtcagtgttataacaccaggaacaaatacttctaaccaggttgctgttctttatca

再到 BLASTN 用這段序列進行搜尋, 這次找到不多序列. 但是有趣的結果來了.

Distance tree of results

Sequences producing significant alignments:
Select for downloading or viewing reports	Description	Max Score	Total Score	Query Cover	E value	Per. Ident	Accession
Select seq KY417148.1	Bat SARS-like coronavirus isolate Rs4247, complete genome	237	237	22%	1e-57	80.51%	KY417148.1
Select seq KC880992.1	Bat SARS-like coronavirus Rs4085 spike protein (S) gene, partial cds	231	231	20%	5e-56	81.10%	KC880992.1
Select seq KC880989.1	Bat SARS-like coronavirus Rs3267-2 spike protein (S) gene, partial cds	231	231	20%	5e-56	81.10%	KC880989.1
Select seq KC880984.1	Bat SARS-like coronavirus Rs3262-2 spike protein (S) gene, partial cds	231	231	20%	5e-56	81.10%	KC880984.1
Select seq LC469301.1	Bat coronavirus Rc-CoV-3 S gene for Spike protein, partial cds	230	230	25%	2e-55	78.18%	LC469301.1
Select seq MK211375.1	Coronavirus BtRs-BetaCoV/YN2018A, complete genome	226	226	22%	2e-54	79.94%	MK211375.1
Select seq MK211378.1	Coronavirus BtRs-BetaCoV/YN2018D, complete genome	220	220	22%	1e-52	79.56%	MK211378.1
Select seq MG772933.1	Bat SARS-like coronavirus isolate bat-SL-CoVZC45, complete genome	198	198	23%	5e-46	77.98%	MG772933.1
Select seq KY417147.1	Bat SARS-like coronavirus isolate Rs4237, complete genome	193	193	22%	2e-44	78.06%	KY417147.1
Select seq KY417143.1	Bat SARS-like coronavirus isolate Rs4081, complete genome	193	193	22%	2e-44	78.06%	KY417143.1
Select seq FJ588686.1	Bat SARS CoV Rs672/2006, complete genome	193	193	22%	2e-44	78.06%	FJ588686.1
Select seq KJ473816.1	BtRs-BetaCoV/YN2013, complete genome	191	191	23%	9e-44	77.31%	KJ473816.1
Select seq MG772934.1	Bat SARS-like coronavirus isolate bat-SL-CoVZXC21, complete genome	187	187	22%	1e-42	77.74%	MG772934.1
Select seq KY417149.1	Bat SARS-like coronavirus isolate Rs4255, complete genome	187	187	22%	1e-42	77.74%	KY417149.1
Select seq KC881003.1	Bat SARS-like coronavirus Rs4087-2 spike protein (S) gene, partial cds	187	187	20%	1e-42	78.45%	KC881003.1
Select seq KC880995.1	Bat SARS-like coronavirus Rs4096 spike protein (S) gene, partial cds	187	187	20%	1e-42	78.45%	KC880995.1
Select seq KY770859.1	Bat coronavirus isolate Anlong-112, complete genome	185	185	23%	4e-42	77.01%	KY770859.1
Select seq KY770858.1	Bat coronavirus isolate Anlong-103, complete genome	185	185	23%	4e-42	77.01%	KY770858.1
Select seq KC881001.1	Bat SARS-like coronavirus Rs4108 spike protein (S) gene, partial cds	176	176	20%	2e-39	77.78%	KC881001.1

Distribution of the top 19 Blast Hits on 19 subject sequences

Query

1

250

500

750

1000

1250

這是從日本野生蝙蝠取得的冠狀病毒 Spkie 蛋白 S 基因的序列.

https://www.ncbi.nlm.nih.gov/nucleotide/LC469301.1?report=genbank&log$=nucltop&blast_rank=5&RID=2VJ0F2KE014

其餘也有研究 Spike 蛋白的 S 基因序列但是都侷限在 1100 ~ 1400 左右.
可能原因有:
1. 此區塊與致病相關, 所以有較大數量的定序成品.
2. 左方的區塊可能被認為與致病不相關?
3. 左方區塊出現僅在此次捕捉的野生蝙蝠樣本出現, 就未曾出現.

只是比較多數蝙蝠基因體序列和武漢海鮮市場樣本,
發現武漢海鮮市場樣本多了 22000 ~ 23400 這一段完整的序列.
排除此段為定序難度高區域. 但是武漢的樣本多了這麼一段,
是大自然演化的結果或是人為操控剪接基因造成的???

讓我們繼續看下去.

現在首重在找出病源, 讓檢驗方法簡易且快速. 畢竟潛伏期就能傳染實在
讓發燒篩檢的成果打了折扣. 更重要的是要在最短時間生產出解方及疫苗.
要不然已經發病的患者不能等很久的.

參考資料:
1. NCBI https://www.ncbi.nlm.nih.gov/
https://blast.ncbi.nlm.nih.gov/Blast.cgi
2. 各種動物與人類冠狀病毒之比較 https://www.coa.gov.tw/ws.php?id=5092

慶賀福衛七號成功發射

2019-06-25T21:06:00.000+08:00

終於在今天下午兩點半搭載 SpaceX 獵鷹重型火箭成功升空.

Ref:
福爾摩沙衛星七號

線上學習資源

2019-03-14T03:29:00.001+08:00

除了 Google 大神, 水管神器, 手機 app 外, 還有哪些線上的學習資源?

以下列出國內外值得參考的資源, 然而這只是冰山一角, 如果有找到更多資源將更新清單.

國外

https://zh-tw.coursera.org/

https://zh.khanacademy.org/

https://ocw.mit.edu/index.htm

https://www.berkeley.edu/academics/online-learning

http://online.stanford.edu/courses

http://online.caltech.edu/

國內

http://ocw.nctu.edu.tw/

http://ocw.aca.ntu.edu.tw/

http://ocw.nthu.edu.tw/

http://ocw.ntust.edu.tw/

http://ctld.video.nccu.edu.tw/

https://ocw.nsysu.edu.tw/

http://ocw.lib.ntnu.edu.tw/

http://portallib.nou.edu.tw/np.asp?mp=1&ctnode=734

https://edu.nchc.org.tw/course/index.asp

在 FreeBSD 及 CentOS 下如何將 timestamp 轉回一般時間格式輸出

2018-12-31T03:47:00.000+08:00

FreeBSD
$ date -jf "%s" "1541563268" +"%Y-%m-%d %H:%M:%S"
2018-11-07 12:01:08

CentOS
$ date -d @1541563268 +"%Y-%m-%d %H:%M:%S"
2018-11-07 12:01:08

加速 SSH 重複登入

2018-12-31T03:44:00.000+08:00

這裡採用的是 ControlMaster 功能, 可設定持續時間.

$ mkdir -p ~/.ssh/cm_socket

$ vi ~/.ssh/config
Host *
ControlMaster auto
ControlPath ~/.ssh/cm_socket/%r@%h:%p
ControlPersist 5m

$ chmod 0600 ~/.ssh/config

如何在 bash 下解析 JSON 資料

2018-12-31T03:37:00.003+08:00

以下是其中的三個方案

1. 使用 python
echo "$DATA" | python -c "import json, sys; obj=json.load(sys.stdin); print(obj['name'])";

# echo '{"test":"123","test2":[{"test21":"456"}]}' | python -c "import json, sys; obj=json.load(sys.stdin); print(obj['test'])"
123

# echo '{"test":"123","test2":[{"test21":"456"}]}' | python -c "import json, sys; obj=json.load(sys.stdin); print(obj['test2'])"
[{'test21': '456'}]

2. 使用 awk sed tr
echo "$DATA" | sed "s/[{}]//g" | tr '[]' ' ' | sed 's/^ //' | awk -v k="text" '{n=split($0,a,","); for (i=1; i<=n; i++) print a[i]}'

# echo '{"test":"123","test2":[{"test21":"456"}]}' | sed "s/[{}]//g" | tr '[]' ' ' | sed 's/^ //' | awk -v k="text" '{n=split($0,a,","); for (i=1; i<=n; i++) print a[i]}'
"test":"123"

"test2": "test21":"456"

3. 使用 jq
# echo '{"test":"123","test2":[{"test21":"456"}]}' | jq -r '.test'

123

Ref:
https://stackoverflow.com/questions/1955505/parsing-json-with-unix-tools

ESXi 好用工具介紹 ghettoVCB

2018-12-31T02:44:00.002+08:00

如果不是好野人家企業/公司, 沒有 VCenter 還有儲存裝置可以爽用 live migration.
可是 guest VM 又不能關機匯出 ova, 又必須搬/複製到另一台 ESXi VM host時, 這個超級好用工具就能幫上忙.
程式
https://github.com/lamw/ghettoVCB

目前支援到 ESXi 6.x

匯出VM 說明文件
https://communities.vmware.com/docs/DOC-8760

匯入VM說明文件
https://communities.vmware.com/docs/DOC-10595

這個軟體利用 snapshot 匯出 VM, 不過用過幾次都只能完整空間匯出, 所以不適用超大硬碟空間使用率的 guest VM. 另外匯入時也無法指定新 guest VM 名稱, 所以會檢查是否有名稱衝突問題.

至於設定檔及測試範例將在下一篇說明.

在 R 進行 K-Means clustering 分析

2018-12-31T01:44:00.001+08:00

之前說了好久的 K-Means clustering 分析終於趁過年放假公佈指令.
使用 R 的好處是將這些複雜的數學計算簡化成指令, 而只要專注於資料分析及選擇正確的分析方法. 參考資料網站的詳盡程度值得讚許, 也值得各位好好仔細學習.

###
### Load data and remove 1st and 2nd column
###
data <- DATA_SOURCE_NAME[-1]
data <- data[-1]
View(data)

###
### Normalization
###
scale(data, center = TRUE, scale = TRUE)
data <- scale(data, center = TRUE, scale = TRUE)
View(data)
write.table(data, file="DATA_Z-Score.csv", sep=",")

###
### K = 2
###
km <- kmeans(data, centers = 2, nstart = 10)
require(factoextra)
fviz_cluster(km, data = data, geom = c("point", "text"), ellipse.type = "norm")
(WSS <- km$tot.withinss) + (BSS <- km$betweenss) + (TSS <- BSS + WSS) + (ratio <- WSS / TSS)

> (WSS <- km$tot.withinss)
[1] 56253.93
> + (BSS <- km$betweenss)
[1] 22738.07
> + (TSS <- BSS + WSS)
[1] 78992
> + (ratio <- WSS / TSS)
[1] 0.7121472

outdata <- table(DATA_SOURCE_NAME$Label, km$cluster)
write.table(outdata, file="DATA_Z-Score-2.csv", sep=",")

###
### K = 3
###
km <- kmeans(data, centers = 3, nstart = 10)
require(factoextra)
fviz_cluster(km, data = data, geom = c("point", "text"), ellipse.type = "norm")
(WSS <- km$tot.withinss) + (BSS <- km$betweenss) + (TSS <- BSS + WSS) + (ratio <- WSS / TSS)

> (WSS <- km$tot.withinss)
[1] 40904.54
> + (BSS <- km$betweenss)
[1] 38087.46
> + (TSS <- BSS + WSS)
[1] 78992
> + (ratio <- WSS / TSS)
[1] 0.5178315

outdata <- table(DATA_SOURCE_NAME$Label, km$cluster)
write.table(outdata, file="DATA_Z-Score-3.csv", sep=",")

Ref:
R系列筆記

用 RTL-SDR 聽 FM 是一種生活態度

2018-05-20T02:31:00.000+08:00

請按照手冊 ( https://github.com/cjcliffe/CubicSDR/wiki/CubicSDR-Manual )
支援模組不是一定要安裝. 安裝過程很順利, 沒有什麼需要注意的地方.

啟動後, 一開始建議還是先聽 FM. 順便練習操作. FM 90.9 訊號強雜訊少拿來測試收聽.

這台筆電 x220 是第二代 i7, 平常 CPU 涼涼的. SDR 一上果真負載就上去惹.

以下是測試不同的取樣率. 從 3.2M ~ 1.5 M

當然不是只有 CubicSDR 可以玩.

有名的 SDR# 也要玩玩.

再加碼 Gqrx

同場加映 SDR touch, 也可以將 SDR 接上手機.

接下來再將 RTL-SDR 硬體接到 Raspberry Pi zero w 上.

用 cowsay 讓終端機充滿智慧

2018-04-28T22:16:00.002+08:00

0. 準備工作
apt-get install fortune cowsay cconv

1. 程式碼 Cowsay.sh
#!/usr/bin/env bash

PATH=$PATH

SLEEP=6

declare -A CS

MAXEM=0
for e in `ls /usr/share/cowsay/cows/*.cow | sed 's/\.cow//' | awk 'BEGIN{FS="/"};{print $NF}'`
do
CS[$MAXEM]="$e"
MAXEM=$((MAXEM+1))
done

while [ 1 ];
do
clear
S=$(( RANDOM % 52 ))
S=$((S+SLEEP))
F="$S"
FACE=""
if [ $F -gt $MAXEM ]; then
F=$(( F % MAXEM ))
FACE=${CS[$F]}
else
FACE=${CS[$F]}
fi
date +"%Y/%m/%d %H:%M:%S"
/usr/games/fortune | cconv -f UTF8-CN -t UTF8-TW | sed -r "s/\x1B\[[0-9;]*[mK]//g" | /usr/games/cowsay -f $FACE
sleep $S
done

2. 執行

chmod a+x Cowsay.sh

./Cowsay.sh

或

bash Cowsay.sh

阿宅桌面時鐘 ASCII 版

2018-04-28T18:34:00.000+08:00

請先安裝 toilet

# apt-get install toilet

然後執行

watch -n 1 "date +\"%Y-%m-%d %H:%M:%S\" | toilet"

Ubuntu 12 升級 16 意外直達 18 感想

2018-04-28T17:14:00.001+08:00

話說之前將一台迷你筆電從 12 經過 14 升級 16 一切順利.
就來將自己的一號機筆電從好多年的 12 升級 16. 這台唯一的升級難度是有使用加密使用者目錄, 如果不小心就會毀掉使用者目錄, 這也是之前猶豫不升級版本的主因.

首先使用外接磁碟備份重要資料.

接著就使用 do-release-upgrade 從 12 升級 14. 一切順利登入而且正確輸入密碼解開使用者目錄. 一鼓作氣繼續升級到 16.

沒想到災難開始, 一路開始抱怨一堆套件不能安裝. 硬著頭皮繼續下去, 到最後還出現完成升級但是無法安裝一堆套件. 直接結束後重新開機就直接 kernel panic.

這時發揮堅持的精神, 放棄新安裝的核心改用舊版開機, 很好, 可以看到終端機登入畫面.
登入後發現無法自動連接網路, 這難不了我, 使用 ifconfig 大法手動來.
網路終於通了, 繼續堅持再執行 do-release-upgrade 還是一樣慘兮兮. 甚至想到之前將雲端VM從 14 升級 16 只改了 apt source 的方法, 然後 apt-get update; apt-get upgrade 後重新開機還是一樣.
這下傻了, 不會要重新安裝系統吧?!

還好此時靈光乍現, 不給升級就改用 update-manager -d. 可是現在是終端機界面哪來的 GUI WM. 死馬當活馬醫, 使用 startx 上場, 雖然 menu bar 通通失蹤, 可是有桌面啊! 立馬按下右鍵開個 GUI 下的終端機執行 update-manager -d. 看到有新版可以更新, 太讚了. 直上 18.04 LTS.
一切順利完成. 重新開機後看到登入畫面一整個感動. 而且大部分安裝的套件都沒消失, 只有 VirtualBox 等已在二號機安裝完成的套件不見蹤影. 更重要的是加密使用者目錄沒消失.

就這樣消耗兩個晚上, 最後想起來之前順利完成是使用更新管理員.
請愛用 update-manager -d

安裝簡易的電報送訊息機器人 Telegram bot

2018-04-28T16:38:00.000+08:00

0. 安裝 telegram 設定帳號 UACCT

1. 加入 @BotFather
BotFather is the one bot to rule them all. Use it to create new bot accounts and manage your existing bots.

About Telegram bots:
https://core.telegram.org/bots
Bot API manual:
https://core.telegram.org/bots/api

Contact @BotSupport if you have questions about the Bot API.

UACCT:
/start

BotFather:
I can help you create and manage Telegram bots. If you're new to the Bot API, please see the manual.

You can control me by sending these commands:

/newbot - create a new bot
/mybots - edit your bots [beta]
/mygames - edit your games [beta]
...

2. 新增 bot
UACCT:
/newbot

BotFather:
Alright, a new bot. How are we going to call it? Please choose a name for your bot.

UACCT:
p****y

BotFather:
Good. Now let's choose a username for your bot. It must end in `bot`. Like this, for example: TetrisBot or tetris_bot.

UACCT:
botusername_bot

BotFather:
Done! Congratulations on your new bot. You will find it at t.me/pipboy88_bot. You can now add a description, about section and profile picture for your bot, see /help for a list of commands. By the way, when you've finished creating your cool bot, ping our Bot Support if you want a better username for it. Just make sure the bot is fully operational before you do this.

Use this token to access the HTTP API:
5*******2:A*********************************w

For a description of the Bot API, see this page: https://core.telegram.org/bots/api

3. 測試 API
3.1. 查詢我是誰
https://api.telegram.org/bot5*******2:A*********************************w/getMe
回應
{"ok":true,"result":{"id":5*******2,"is_bot":true,"first_name":"p****y","username":"botusername_bot"}}

3.2. 加入 bot 聊天並取得聊天室編號
https://api.telegram.org/bot5*******2:A*********************************w/getUpdates
{
"ok": true,
"result": [
{
"update_id": 5*******0,
"message": {
"message_id": 41,
"from": {
"id": CHAT_ID,
"is_bot": false,
"first_name": "UACCT_DESCRIPTION",
"username": "UACCT",
"language_code": "zh-TW"
},
"chat": {
"id": CHAT_ID,
"first_name": "UACCT_DESCRIPTION",
"username": "UACCT",
"type": "private"
},
"date": 1524858545,
"text": "hbbvoebbvebwber"
}
}
]
}

3.3. 送出第一則訊息
https://api.telegram.org/bot5*******2:A*********************************w/sendMessage?chat_id=CHAT_ID&text=Hello+World

3.4. 送訊息 script
3.4.1. 先安裝 packages
apt-get install jq cconv fortune fortune-zh

3.4.2. 送訊息程式 tgsendmsg.sh
#!/usr/bin/env bash

PATH=$PATH

TS=`date +"%s.%N"`
LOGPATH="/PATH/to/tglog"
LOG="$LOGPATH/LogFilename.log"

BOTTK="5*******2:A*********************************w"
CHATID="CHAT_ID"

mkdir -p $LOGPATH
touch $LOG
chown -R 0755 $LOGPATH

if [ -n "$1" ]; then
MSG="$1"
shift
else
echo "Usage: $0 \"Message\""
exit 1
fi

TM=`curl --progress-bar --data-urlencode "chat_id=$CHATID" --data-urlencode "text=$MSG" "https://api.telegram.org/bot$BOTTK/sendMessage"`
echo "$TM" | jq
echo "$TS $TM" >> $LOG

3.4.3. 呼叫送出訊息 MyMSG.sh
#!/usr/bin/env bash

PATH=$PATH

Z="Asia/Taipei"

HR=`TZ=":$Z" date +"%H"`
HR=`echo "$HR" | sed 's/^0//'`
echo $HR

if [ $HR -eq 6 ]; then
/root/tgsendmsg.sh "Good Morning 早安"
FTZH=`/usr/games/fortune-zh | cconv -f UTF8-CN -t UTF8-TW`
MSG=""
for d in $FTZH
do
MSG="$MSG $d"
done
MSG=`echo "$MSG" | sed -r "s/\x1B\[[0-9;]*[mK]//g"`
/root/tgsendmsg.sh "$MSG"
fi

if [ $HR -eq 12 ]; then
/root/tgsendmsg.sh "Good Afternoon 午安"
FT=`/usr/games/fortune | cconv -f UTF8-CN -t UTF8-TW`
FT=`echo "$FT" | sed -r "s/\x1B\[[0-9;]*[mK]//g"`
/root/tgsendmsg.sh "$FT"
fi

if [ $HR -eq 18 ]; then
/root/tgsendmsg.sh "Good Night 晚安"
FT=`/usr/games/fortune | cconv -f UTF8-CN -t UTF8-TW`
FT=`echo "$FT" | sed -r "s/\x1B\[[0-9;]*[mK]//g"`
/root/tgsendmsg.sh "$FT"
fi

接下來就發揮想像力把能串接的掛上去, 也能多開幾隻 bot 送不同類型的訊息.

IBM X200s 改裝 Intel 5300 無線網卡

2017-12-04T00:02:00.001+08:00

無線網路卡買的是 Intel Wifi link 5300

由於有鎖網卡, 請選擇支援自己筆電型號的網卡

直接將原無線網卡取代. 使用旁邊的卡槽無法正常找到網路卡.

在 /boot/loader.conf 加上下列設定在開機時載入核心模組

if_iwn_load="YES"

在 /etc/rc.conf 加入下列設定啟動無線網卡

wlans_iwn0="wlan0"

ifconfig_wlan0="WPA DHCP"

FreeBSD 11.1 local_unbound 設定

2017-12-03T23:50:00.001+08:00

為何想要用 local_unbound? 主要是為了 DNSSEC 檢驗能從本機開始檢查,
既然各軟體要外掛實在是有難度. 所以就安裝本機快取並使用已經啟動
DNSSEC 檢查的 cache DNS.

以下就是簡單的啟動步驟:
設定檔 /etc/rc.conf
local_unbound_enable="YES"

local_unbound 設定檔目錄 /var/unbound

root@bsd11x200s:/var/unbound # ls -la

total 36

drwxr-xr-x 3 unbound unbound 8 Dec 3 23:08 .

drwxr-xr-x 26 root wheel 26 Dec 3 21:27 ..

drwxr-xr-x 2 unbound unbound 3 Dec 3 23:07 conf.d

-rw-r--r-- 1 root unbound 193 Oct 11 09:54 control.conf

-rw-r--r-- 1 root unbound 104 Dec 3 22:56 forward.conf

-rw-r--r-- 1 root unbound 189 Oct 11 09:54 lan-zones.conf

-rw-r--r-- 1 unbound unbound 1252 Dec 3 23:08 root.key

-rw-r--r-- 1 root unbound 389 Oct 11 09:54 unbound.conf

設定轉送查詢的 cache DNS

root@bsd11x200s:/var/unbound # cat forward.conf

# Generated by resolvconf

forward-zone:

name: "."

forward-addr: 8.8.8.8

forward-addr: 192.168.xxx.xxx

設定一些 unbound 參數

root@bsd11x200s:/var/unbound # cat conf.d/options.conf

server:

num-threads: 3

interface: 0.0.0.0

access-control: 127.0.0.0/8 allow

harden-glue: yes

harden-dnssec-stripped: yes

harden-below-nxdomain: yes

harden-referral-path: yes

啟動服務

root@bsd11x200s:/var/unbound # service local_unbound start

root@bsd11x200s:/var/unbound # cat /etc/resolv.conf

nameserver 127.0.0.1

options edns0

測試

(1) host

root@bsd11x200s:/var/unbound # host www.google.com 127.0.0.1

Using domain server:

Name: 127.0.0.1

Address: 127.0.0.1#53

Aliases:

www.google.com has address 216.58.200.36

www.google.com has IPv6 address 2404:6800:4008:801::2004

(2) nslookup

root@bsd11x200s:/var/unbound # nslookup www.google.com 127.0.0.1

Server: 127.0.0.1

Address: 127.0.0.1#53

Non-authoritative answer:

Name: www.google.com

Address: 172.217.160.100

Name: www.google.com

Address: 2404:6800:4008:801::2004

(3) Dig 測試 DNSSEC

root@bsd11x200s:/var/unbound # dig +dnssec @127.0.0.1 www.icann.org A

; <<>> DiG 9.11.2 <<>> +dnssec @127.0.0.1 www.icann.org A

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65414

;; flags: qr rd ra ad; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags: do; udp: 4096

;; QUESTION SECTION:

;www.icann.org. IN A

;; ANSWER SECTION:

www.icann.org. 3566 IN CNAME www.vip.icann.org.

www.icann.org. 3566 IN RRSIG CNAME 7 3 3600 20171214150526 20171123111933 7500 icann.org. i5KCfOv/+c/xIaRxmQrqTItEtlGkTe9RWoh2gKh5Rh/a431n2CLLNiZ2 8xpuDXoqb2KQlAz4JBhyydFb2ilPCJIPXFbiQbUksuDV6zHdYu+PzlUC hbxRkBhRD2CIPOc227igVbp3io4oTqlzaja4P0gq268yoVEOPb2/2sSs DzFDV80=

www.vip.icann.org. 29 IN A 192.0.32.7

www.vip.icann.org. 29 IN RRSIG A 7 4 30 20171208095813 20171201095813 6887 vip.icann.org. k4FaKFgAcblg0yRPMyP1TvNcXmgI9d1GXM4YQ9jelGeCro2I+OQW+BFg OKQgmjcnh3M7NiZBW2vQQF000iKWS938B/YeiODQuun+kv9ANaiCEipD /0FFkjecpgwuMCCy2ommmRsWSlv4484Sdw7KRW8S28SZj8jonCqzIDct rVQ=

www.vip.icann.org. 29 IN RRSIG A 7 4 30 20171208095813 20171201095813 4532 vip.icann.org. FoSTut3HaWz1SEHtxReWh7IuOHOv4kCAEIuz1zPQPQVvNDU6WHenVF4h YSJOSLgyLwZ9P1MsH8PGPJEpCJr6jOR1Gl7QF24UezSj5PXnoinPLyjG Zm8/3DcM6UcrZhwmm9wRTSOuGv+LAmiU9Ab0WUfKEKR/vMnj4qn5HR+Y QOI=

;; Query time: 315 msec

;; SERVER: 127.0.0.1#53(127.0.0.1)

;; WHEN: Sun Dec 03 23:24:36 CST 2017

;; MSG SIZE rcvd: 598

至於想要了解什麼是 DNSSEC 請先看

DNSSEC – What Is It and Why Is It Important?

https://www.icann.org/resources/pages/dnssec-qaa-2014-01-29-en

以下是 TLD 支援 DNSSEC 的現況

TLD DNSSEC Report

http://stats.research.icann.org/dns/tld_report/

參考資料

1. How To Set Up the Unbound Caching DNS Resolver on FreeBSD 10.1 or 10.2

https://www.digitalocean.com/community/tutorials/how-to-set-up-the-unbound-caching-dns-resolver-on-freebsd-10-1

2. unbound.conf - Unbound configuration file.
https://www.unbound.net/documentation/unbound.conf.html

用 R 分析 log

2017-08-27T22:06:00.003+08:00

有時間再來慢慢講用 R 分析 log 的學習過程. 以下是分析經過 Z-Score normalization 的結果.

在 VirtualBox 使用 crochet 製作 Pine64 可用的 FreeBSD 12.0-CURRENT 影像檔

2017-08-27T21:58:00.002+08:00

安裝 VM 請注意硬碟記憶體給大一點, 可以製作大一點的影像檔.

硬碟建議使用 32 GB 記憶體 4GB.

安裝VM完成後請參考 https://github.com/freebsd/crochet 安裝

請編輯 board/Pine64/setup.sh 調整 IMAGE_SIZE 到 3000 以上避免問題

製作出開機影像檔後, 請使用 dd if=IMG of=/dev/SDCARD_DEVICE bs=10240 寫入記憶卡

開機後請安裝 gpart 參考 https://www.freebsd.org/doc/handbook/disks-growing.html

使用 gpart 調整 mmcsd0 後再使用 service growfs onestart 調整大小.

root@pine64:~ # df -h

Filesystem Size Used Avail Capacity Mounted on

/dev/mmcsd0s2a 29G 2.7G 24G 10% /

devfs 1.0K 1.0K 0B 100% /dev

/dev/mmcsd0s1 64M 128K 64M 0% /boot/efi

/dev/md0 29M 24K 26M 0% /tmp

/dev/md1 14M 64K 13M 0% /var/log

/dev/md2 11M 8.0K 10M 0% /var/tmp

[非教學文] 在 android 手機上 linux deploy 執行 Linux

2016-12-12T23:05:00.000+08:00

前題: 一隻已經 root 過的閒置手機及較大的儲存空間.

硬體: Ramos mos1(買到已經完成 root 及安裝 xposed)

軟體: linux deploy + piggy helper

其實安裝設定都不難, 網路上文章看看就能完成.

一開始玩得蠻開心的. 但是為了寶可夢, 開始尋找能暫時關閉 root 的軟體, 找到了 root switch. 結果關掉 root 時忘記勾選還原狀態, 直接重啟動. 杯具就發生了. root 消失了. 更慘的是寶可夢還是不能玩.

於是開始踏上尋找 root 的旅程, 一直想要直接 app 一鍵 root, 但這隻有點冷門, 找了半天找上 kingo root, 還是無法直接用 app root. 只好動用 windows 版 adb root. 總算將 root 找回來. 如果有使用冷門手機想要 root 可以參考一下這個一鍵 root 軟體. 確定可以 root ramos mos1 及紅米.

目前已經解決 linux deploy SSH 連線及 VNC 連線問題. 接下來要尋找如何製作自己的 container, 目標看能不能安裝 FreeBSD 上去??? 另外也安裝了 kalitop10 可以學習使用 kali 套件.

參考資料:

1. http://nitroxenon.com/android-linux

2. https://www.kali.org/tutorials/kali-linux-android-linux-deploy/

3. https://github.com/meefik/linuxdeploy

GMail IPv6 收信開始檢查正反解及 SPF

2016-02-17T19:54:00.000+08:00

股狗啊! 真是搞不懂你. 為啥前天靜悄悄的將 GMail IPv6 的正反解檢查還有 SPF 開起來. 被用戶通知怎麼郵件轉送都會收不到. 只好先跳回用 IPv4 送信. 又要再加一個偵測項目了.

首登百岳及首露

2015-11-18T21:39:00.000+08:00

人生第一座百岳獻給合歡北峰, 而且將第一次露營獻給小溪營地.

第一天登場的就是落日餘暉

來張超廣角度的風景

永遠記得小溪營地美麗星空伴隨冷冽寒風, 但是隔天清晨日出溫暖明亮.

小溪營地上北峰

首登百岳紀念照, 不好意思佔據版面, 只好讓北峰獨照.

風起雲湧, 正是觀賞時.

回首來時路, 但願能再次重逢.

８/１~２(六日)~砂卡礑步道>七星潭>花蓮賞鯨>白楊步道健走

2015-08-04T20:39:00.000+08:00

砂卡礑步道>七星潭>花蓮賞鯨>白楊步道健走

CVE-2015-5477 Named DoS

2015-08-04T20:21:00.001+08:00

最近這個代誌很大條. 負責 DNS 伺服器的管理員們趕快更新吧!

這是 100% 可以擊倒的, 只要權威主機被多掛幾台, 就會有一堆網站受影響.

手邊也拿到攻擊的程式, 接下來研究看看.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5477

用台灣的本土文化交流就是這麼歡樂 - 台灣三太子

2014-10-05T02:30:00.001+08:00

誰說文化交流一定要用那些繼承過來文謅謅的中國文化, 用台灣的本土文化交流就是這麼歡樂.

以下內容轉錄自 YouTube, 版權為創作者所有.

這樣操作電腦才叫做酷. Control Your Virtual World -- Mind Blow #87

2014-09-30T21:28:00.001+08:00

Bash CVE-2014-6271 和 CVE-2014-7169 漏洞暫時解法

2014-09-26T22:29:00.003+08:00

今天收到長官指示要看這一篇

Bash Shell 漏洞威脅不小於 Heartbleed！Unix-Like 作業系統請儘速更新

才剛升級完成, 也做出第一版的升級原始碼給抓不到 RPM 的機器. 就又收到同事的晴天霹靂.

Bash Shellshock Command Injection Vulnerability (CVE-2014-6271 and CVE-2014-7169)

真是雙重打擊效(笑)果好?!

目前現況: EL6 可以直接升級, 但是只解決 6271. FreeBSD 9 及 10 使用 ports 升級也是一樣. 只有 Ubuntu 的更新版本可以直接修掉 6271 及 7169. 小弟自己從 GNU 下載並且已經上好 patch . 接著再從 Ubuntu 中挖出 patch 檔. 成果就放在雲端硬碟中, 歡迎大家取用.

目前測試過的平台 EL6 x86_64, EL5 x86_64. FreeBSD 尚未測試. (要不是剛好要去當工作人員, 應該可以更早做出來)

檔案在此 https://drive.google.com/folderview?id=0B1TOrKgNeD45N0VxQWZ1c1JrU0U&usp=sharing

PS: 由於這是應急沒有經過官方完整測試的版本, 請勿上到重要的環境. 後果請自負.
PS2: 解法是由高手找出來的, 不要問我喔！甘溫.

服用方法很簡單
1. 解開壓縮檔
2. 到目錄下 ./configure
3. make
4. make install
5. 程式會將 bash 安裝到 /usr/local/bin
6. 測試沒問題請想辦法蓋掉 /bin/bash
收工

祝大家有個忙碌的週末. ^^;;;