ubuntu14.04x64在thinkpad-T540px04

发配通用

1，This version of Android Studio is incompatible with the Gradle Plugin used. Try disabling Instant Run (or updating either the IDE or the Gradle plugin to the latest version)
改，File-->Setting-->Build..-->Instant Run-->那几个勾全取消掉
然后删掉Build内容
就好了。。。。

2，intellij之andord stuido默认签名
太久不玩忘得差不多了。。。。

senrsl@senrsl-T540p:~$ keytool -v -list -keystore '/home/senrsl/.android/debug.keystore'

输入密钥库口令:

***************** WARNING WARNING WARNING *****************

* 存储在您的密钥库中的信息的完整性 *

* 尚未经过验证! 为了验证其完整性, *

* 必须提供密钥库口令。                  *

***************** WARNING WARNING WARNING *****************

密钥库类型: JKS

密钥库提供方: SUN

您的密钥库包含 1 个条目

别名: androiddebugkey

创建日期: 2015-9-14

条目类型: PrivateKeyEntry

证书链长度: 1

证书[1]:

所有者: CN=Android Debug, O=Android, C=US

发布者: CN=Android Debug, O=Android, C=US

序列号: 2d3e029e

有效期开始日期: Mon Sep 14 19:52:12 CST 2015, 截止日期: Wed Sep 06 19:52:12 CST 2045

证书指纹:

    MD5: 11:DB:DA:20:17:DB:4B:12:41:01:7D:F9:92:AC:E1:1F

    SHA1: 62:6A:07:23:CD:62:DE:D5:63:A9:4E:90:B6:88:A4:47:E7:9A:7D:70

    SHA256: 79:83:72:E4:BF:3D:66:8C:46:59:67:FB:2F:BB:74:E2:38:28:22:35:88:F3:A5:4D:34:12:79:23:0D:ED:74:D6

    签名算法名称: SHA256withRSA

    版本: 3

扩展:

#1: ObjectId: 2.5.29.14 Criticality=false

SubjectKeyIdentifier [

KeyIdentifier [

0000: 73 EF 5E 64 35 E2 B9 30   E4 9E 61 72 51 E5 7F 5C s.^d5..0..arQ..\

0010: D3 C0 94 E5                                        ....

]

]

*******************************************

*******************************************

senrsl@senrsl-T540p:~$

3，ubuntu连接openvpn
先安装客户端，然后调用配置连接

senrsl@senrsl-T540p:~$ sudo apt-get install openvpn

senrsl@senrsl-T540p:~$ cd doc/intrant/

senrsl@senrsl-T540p:~/doc/intrant$ l

ca.crt name.crt name.key name.ovpn

senrsl@senrsl-T540p:~/doc/intrant$ sudo openvpn name.ovpn

然后就连接上了。。。。

4，看起来不错的文本编辑器sublime
今天看到别人用，下下来看起来不错的样子
www.sublimetext.com/3
linux后面有tar包。。。。

5，intellij/android studio关联源码
路径File-->Other setting-->Default Project structrue
打开是这样子的

然后点Sourcepath,选择物理目录

OK就好了

6，引入第三方system sdk
sgm给了一套自己编的系统。。。。
尝试使用Intellij引入，可以在上面↑那里加入SDK，如果删除掉其他几个只用sgm custom sdk的话会影响到其他项目，因为IdeaProject的配置就一套，存放于当前用户根目录~/.IntelliJIdea2016.2目录；
使用eclipse，新建workspace后变更android SDK path到sgm custom sdk，不会影响其他workspace的配置，因为他的配置存放于自己的workspace；
垃圾 android studio。。。。。
然而sgm custom sdk给的sdk是win版的，linux表示草拟打野。。。。

7，git push出现ssh_exchange_identification: read: Connection reset by peer；fatal: Could not read from remote repository.
往bitbucket上推推不上去了。。。。

senrsl@senrsl-T540p:~/share/svn/handover$ git push origin master

ssh_exchange_identification: read: Connection reset by peer

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

senrsl@senrsl-T540p:~/share/svn/handover$ ssh -T git@bitbucket.org

ssh_exchange_identification: read: Connection reset by peer

senrsl@senrsl-T540p:~/share/svn/handover$ ssh -T git@github.com

Warning: Permanently added the RSA host key for IP address '192.30.255.113' to the list of known hosts.

Hi senRsl! You've successfully authenticated, but GitHub does not provide shell access.

senrsl@senrsl-T540p:~/share/svn/handover$

看起来像是网络不好啊。。。。
第二天周六2017年06月17日14:19:59回家弄

senrsl@senrsl-T540p:~$ ssh -T git@github.com

Warning: Permanently added the RSA host key for IP address '192.30.255.112' to the list of known hosts.

Hi senRsl! You've successfully authenticated, but GitHub does not provide shell access.

senrsl@senrsl-T540p:~$ ssh -T git@bitbucket.org

logged in as dcjz.

You can use git or hg to connect to Bitbucket. Shell access is disabled.

senrsl@senrsl-T540p:~$

很轻松的就连上了。。。。

8，Error:Gradle: Execution failed for task ':app:processDebugResources'.
莫名其妙报错
Error:Gradle: Execution failed for task ':app:processDebugResources'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/home/senrsl/android/android-sdk-linux/build-tools/25.0.2/aapt'' finished with non-zero exit value 1
找了半天竟然是assets文件夹下不能放中文文件。。。。

senrsl@senrsl-T540p:~/android/IdeaProjects/SlideDemo/app/src/main/assets$ tree

.

└── demo_0619

└── 0首页-天气.gif

1 directory, 1 file

senrsl@senrsl-T540p:~/android/IdeaProjects/SlideDemo/app/src/main/assets$

改成英文就好了。。。。

9，抗抑郁药
成分

氟西汀    Fluoxetine

帕罗西汀    Paroxetine

舍曲林    Sertraline

氟伏沙明    Fluvoxamine

西酞普兰    Citalopram

艾司西酞普兰    Escitalopram

托莫西汀    Atomoxetine

瑞波西汀    Reboxetine

文拉法辛    Venlafaxine

度洛西汀    Duloxetine

米那普仑    Milnacipran

米氮平    Mirtazapine

曲唑酮    Trazodone

马普替林    Maprotiline

米安色林    Mianserin

去甲替林    Nortriptyline

阿米替林    Amitriptyline

氯米帕明    Clomipramine

地昔帕明    Desipramine

多塞平    Doxepin

丙米嗪    Imipramine

噻萘普汀钠    Tianeptine

阿莫沙平    Amoxapine

吗氯贝胺    Moclobemide

罗拉    Lorazepam

黛力新    Deanxit

喹硫平    Quetiapine

安非他酮    Bupropion

不换行
氟西汀，帕罗西汀，舍曲林，氟伏沙明，西酞普兰，艾司西酞普兰，托莫西汀，瑞波西汀，文拉法辛，度洛西汀，米那普仑，米氮平，曲唑酮，马普替林，米安色林，去甲替林，阿米替林，氯米帕明，地昔帕明，多塞平，丙米嗪，噻萘普汀钠，阿莫沙平，吗氯贝胺，罗拉，黛力新，喹硫平，安非他酮
英文
Fluoxetine，Paroxetine，Sertraline，Fluvoxamine，Citalopram，Escitalopram，Atomoxetine，Reboxetine，Venlafaxine，Duloxetine，Milnacipran，Mirtazapine，Trazodone，Maprotiline，Mianserin，Nortriptyline，Amitriptyline，Clomipramine，
Desipramine，Doxepin，Imipramine，Tianeptine，Amoxapine，Moclobemide，Lorazepam，Deanxit，Quetiapine，Bupropion

10，斯里兰卡过境签
澳门每天都有灰机
www.eta.gov.lk/slvisa/visainfo/fees.jsp#
过境签免费
第一步，申请签证类型

    Tourist ETA    旅游签证
     Apply for an Individual 个人
     Apply for a Group 团队
     Apply for a Third Party 第三方

    Business Purpose ETA 商务签证
     Apply for an Individual
     Apply for a Group
     Apply for a Third Party

    Transit ETA 过境签证
     Apply for an Individual
     Apply for a Group
     Apply for a Third Party

步骤：

ETA application process....
1.Submit Application    Fill all mandatory fields and submit your ETA application
2.Review Information    Review your application and confirm
3.Payment Options    Select desired payment option
4.ETA Confirmation    Print your ETA confirmation

填完，最后
Department of Immigration & Emigration Acknowledgement of ETA application

Date: 30/08/2017 13:06:04 (In Sri Lankan Standard time)

Dear MR NAME ZHAO

Your ETA application to visit Sri Lanka has been received.

Your reference number is: xxxxxxx

Charged Amount: USD 0

You will receive a response for your application within 24 hours.

You may make inquiries only after 24 hours of submission of your ETA application.

THIS ETA ACKNOWLEDGEMENT NOTICE IS ONLY SERVED TO YOU FOR THE PURPOSE OF MAKING THE ETA PROCESSING FEE. ALSO YOU MAY AWARE THAT THIS IS NOT AN APPROVAL NOTICE. YOU SHOULD NOT ARRIVE IN SRI LANKA WITHOUT RECEIVING THE ETA APPROVAL NOTICE.

For inquiries
Telephone :0094 71 9967888
Fax :0094112674631
E-mail :eta@immigration.gov.lk

This is a computer generated notice and carries no signature or seal.

Department of Immigration and Emigration,
Sri Lanka

然后，打开邮箱，竟然已经生成好了。。。。
神速啊。。。。
Department of Immigration & Emigration Acknowledgement of ETA application
DEPARTMENT OF IMMIGRATION & EMIGRATION SRI LANKA.
ETA APPROVAL NOTICE.

We are pleased to inform you that your application for ETA has been approved.

ETA Number: xxxxxxxxx
Name: MR. xxxxx ZHAO
Passport Number: xxxxx
Nationality: CHINA (CHN)
Date Of Birth (DD/MM/YYYY): xx/01/xxxx

Validity of ETA (DD/MM/YYYY): Valid 2 days ONLY. (Use before 26/02/2018)

Purpose of Travel: Transit - Transiting through Sri Lanka
(You are NOT permitted to use this ETA for any other purpose. )

This ETA allows ONLY you to transiting through Sri Lanka and you will not be permitted to enter Sri Lanka. Please produce your passport together with return air ticket and proof of sufficient funds to the Immigration officer at the port of entry to Sri Lanka.

(Please visit www.eta.gov.lk for more information.)

This is a computer generated notice and carries no signature or seal.

GENERATED BY DEPARTMENT OF IMMIGRATION & EMIGRATION SRI LANKA

但愿能解决澳门入境问题！！！
2017年09月26日17:48:45
从香港到澳门,出香港用通行证,入澳门用护照,上面那张纸压根就没用到....

11，ubuntu iso image md5 & sha1
在这里releases.ubuntu.com/16.04/
然后下面有对应文件,比如md5sum的

0d9fe8e1ea408a5895cbbe3431989295 *ubuntu-16.04.3-desktop-amd64.iso  75a7782576b1cf6fde2aa242df9e4c05 *ubuntu-16.04.3-desktop-i386.iso  10fcd20619dce11fe094e960c85ba4a9 *ubuntu-16.04.3-server-amd64.img  10fcd20619dce11fe094e960c85ba4a9 *ubuntu-16.04.3-server-amd64.iso  8428cead4ee139873da19248590e354f *ubuntu-16.04.3-server-i386.img  8428cead4ee139873da19248590e354f *ubuntu-16.04.3-server-i386.iso

12,ultraISO烧录系统到U盘
昨天一直烧进去win7x64结果无法启动,今天重新烧的时候便捷启动里增加写入MBR引导之USB-HDD+,写入方式依旧是USB-HDD+ v2,就好了....
烧win7x64的时候iso文件可以在ultraISO打开iso文件后加东西,比方说网卡驱动啊,多系统引导啊,winrar啊,系统破解啊....名字也可以改成WIN7X64,这样烧完后的U盘名字就是WIN7X64....

然后ubuntu16.04报failed to load ldlinux.c32,网上查了下,我之前用的ultraISO版本是UltraISO.v.9.6.2.3059.exe,然后下了个 UltraISO_9.7.0.3476 单文件高级版.exe,重新加主引导MBR烧录,再次重启就好了....

看来以后要用U盘做系统盘得买新U盘了,我这珍藏多年的生锈4G优盘有点吃力啊....

插更2017年11月21日11:29:18买了16G的U盘
双11从工行拿积分换的16G的U盘到了,可以烧个win10玩
然后,用diskGenius把磁盘从MBR改成GPT,磁盘就崩了,好吧,重装.....
回TAG28....

13,nss_util.cc(632)] NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required

提示升级chrome有一阵了,升级一下
结果无法启动

senrsl@senrsl-T540p:~/下载$ google-chrome

[5823:5858:0928/155445.381950:FATAL:nss_util.cc(632)] NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.

已放弃 (核心已转储)

senrsl@senrsl-T540p:~/下载$ google-chrome-stable

启动不了了,查了下新版的是在ubuntu16.04上运行,我的依然在14.04系统....
尝试

senrsl@senrsl-T540p:~/下载$ sudo apt-get install libnss3

正在读取软件包列表... 完成

正在分析软件包的依赖关系树

正在读取状态信息... 完成

将会安装下列额外的软件包：

libnspr4 libnss3-nssdb

下列软件包将被升级：

libnspr4 libnss3 libnss3-nssdb

升级了 3 个软件包，新安装了 0 个软件包，要卸载 0 个软件包，有 544 个软件包未被升级。

需要下载 1,242 kB 的软件包。

解压缩后会消耗掉 20.5 kB 的额外空间。

您希望继续执行吗？ [Y/n] Y

【警告】：下列软件包不能通过验证！

libnspr4 libnss3-nssdb libnss3

不经验证就安装这些软件包吗？ [y/N] y

....

senrsl@senrsl-T540p:~/下载$ google-chrome

senrsl@senrsl-T540p:~/下载$

启动起来了,然后没一分钟就崩了....
然后再次启动,暂时没崩

新版的主题好像变了,,,,,好丑.....
然后跑主题商店,换了几个主题之后,再切回经典主题,就好受点了.....

恩,暂时仍没崩,但看着一直报错
senrsl@senrsl-T540p:~$ google-chrome-stable
[11323:11360:0928/160631.098650:ERROR:service_manager.cc(156)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser
couldn't lock 16384 bytes of memory (secret_session): 无法分配内存
[11323:11323:0928/160817.224503:ERROR:CONSOLE(192)] "Uncaught TypeError: Cannot read property '0' of null", source: chrome://settings/crisper.js (192)
[11323:11360:0928/162204.156694:ERROR:service_manager.cc(156)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser

......

14,google的隐私权更新了
this user-agent is not permited to make an OAuth authorization request to google as it is classified as an embedded user-agent(also known as a web-view).Per our policy,only browsers are permitted to make authorization requests to google.we offer several libraries and samples for native apps to perform authorization requests int the browers.
SSL handshake timed out
然后推荐让这个方式 Modernizing OAuth interactions in Native Apps for Better Usability and Security(developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html)
然后给了三种方式让选择

Google Sign-In for Android and iOS, our recommended SDK for sign-in and OAuth with Google Accounts.

AppAuth for Android, iOS, and OS X, an open source OAuth client library that can be used with Google and other OAuth providers. We also offer GTMAppAuth (for iOS and OS X), a library which enables AppAuth support for the Google APIs Client Library for Objective-C, and the GTM Session Fetcher projects.

Google Sign-in and OAuth Examples for Windows, examples

噢,不对,这是两种....
一种是调用google自己的程序鉴定,就像新浪微博做本地sso鉴权,本地需要安个他的app,然后他这个还需要在self app里增加play service,另一种是openid的方式,也是要本地加个sdk....
妈蛋,我之前就400k的app,这么一搞,体积直接增大十几倍.......

我错了,上面提供的两种方式都要安google play service才能用......

逼着让安全家桶,作死

把google auth的地址抓出来,直接放浏览器里试了下,可以在浏览器上从登陆跑到登陆后调用页面.
可以考虑走这个方式进行修改.

从程序中,打开新的浏览器,给他地址,然后鉴权完成后,再通过调用调回app,回传鉴权结果....
明天搞2017年10月09日19:00:44
测试,
通过android打开默认浏览器可以的.
通过浏览器点击连接调回应用也是可以的....
成功的只是在页面点击.....像这种

<html>
<body>
<a href="posthot://dc.android/openwith?code=abc123">open it</a>
</body>
</html>

然后监测接收到了

10-10 09:36:59.817: W/TEST(3465): 外部网页返回:abc123---------action:android.intent.action.VIEW

这样动态参数就没法挂了....

上面测试,从app调起默认浏览器鉴权,然后鉴权成功后从浏览器调回app,都可以....
然后去模拟请求

400. That's an error.

Error: invalid_request

Custom scheme URIs are not allowed for 'WEB' client type.

地址上之前&redirect_uri=http://xxxxxxx
然后改成了&redirect_uri=dc.android.xxxx
从网页上报上面那个错误
从平板上的错误描述变成了

Uri must consist of printable ASCII characters

虽然报的位置都是redirect_uri,但描述竟然有区别
描述一致,上面那个是因为url有空格.....
看来....
是时候出大招了....
跳转到之前的oauth20.html页面,然后这个页面上挂可以跳转回来的链接,此时.
copy current url,when page jump to Activity, paste it.
Activity analsys url and saved.
我屮,这思路真棒!!!
幸好是自己拿着玩,要是发布出去的应用这么搞非得被打死.....

上面方案测试可行,就是太low

然后新浪api的也出问题
sso鉴权调不起来,热榜获取不到....
热榜问题:
比对了半天url.....
然后发现,当前最新的weibo app是7.9.4,我去年折腾的时候应用的版本是6.7.2,这两个获取热榜的格式不同,所以我去新版微博里抓了地址套上后格式不同.
当然,上面那句不是重点
我发现版本不同,热榜协议不同之后,找了6.7.0的版本,登陆后,发现格式跟之前应用的相同了,然后,
回顾了热榜报的错:

{"errmsg":"由于你近期修改过密码，或开启了登录保护，为保障你的帐号安全，请重新登录。","errno":-100,"errtype":"DEFAULT_ERROR","isblock":false}

他说的很对,直到此时,才想起来,前两天刚开始改google问题的时候,发现weibo登陆不上去,密码忘了,然后重置了一下密码.....
然后重新抓了获取热榜的url,发现鉴权的参数是gsid,把新抓的gsid值放到应用里,直接跑就可以嘞.....

改密码前请三思啊.....

GFW大规模施法,今天去墙外的难度比昨天难了好多好多啊....

特么的 bitbucket也给墙了.....

15,Bestbuy跟Walmart一直砍单
大蒜买几个129刀跟149刀的iPhone SE当老人机,折腾几天,砍单砍到怀疑人生
今天看到一句
Bestbuy要求非美国境内的信用卡统一填写此账单地址:

10780 Kempwood Dr.
Houston, TX 77043

然后这次换招行全币卡下一单
三分钟了,还没砍....

16,刷hiboy老毛子固件蓝灯问题
新版的固件路由器不管什么状态都只会红灯了,查了下

哈哈,多大仇

增加方法,加脚本
高级设置-->自定义设置-->脚本,
在路由器启动后执行脚本加:

#关闭红灯

mtk_gpio -d 8 1

#关闭蓝灯

mtk_gpio -d 10 0

#开启黄灯

mtk_gpio -d 11 1

logger "在路由器启动后开启黄灯"

在WAN上行/下行启动后执行加:

#关闭红灯

mtk_gpio -d 8 1

#关闭黄灯

mtk_gpio -d 11 0

#开启蓝灯

mtk_gpio -d 10 1

logger "在WAN 上行/下行启动后开启蓝灯"

或者这个是WAN上行下行脚本的进阶版:

#!/bin/sh

### Custom user script
### Called after internal WAN up/down action
### $1 - WAN action (up/down)
### $2 - WAN interface name (e.g. eth3 or ppp0)
### $3 - WAN IPv4 address
logger "运行后 WAN 状态:" "WAN 状态:【$1】, WAN 接口:【$2】, WAN IP:【$3】"

if [ $1 == "up" ] ; then
    mtk_gpio -d 8 1
    mtk_gpio -d 10 1
    logger "在WAN 上行/下行启动up后关闭红灯开启蓝灯,睡眠30s执行定时脚本"
    sleep 30
    /etc/storage/crontabs_script.sh up &
else
    mtk_gpio -d 8 0
    mtk_gpio -d 10 1
    logger "在WAN 上行/下行启动down后开启红灯开启蓝灯"
fi

测试
Oct 13 14:48:39 dc: 运行后 WAN 状态: WAN 状态:【up】, WAN 接口:【eth2.2】, WAN IP:【192.168.6.1】
Oct 13 14:48:39 dc: 在WAN 上行/下行启动up后关闭红灯开启蓝灯,睡眠30s执行定时脚本
Oct 13 14:49:13 bwmon[1629]: MINOTELTE-SENRSL_XM join your network: IP: 192.168.0.118, MAC: a0:86:c6:fe:f0:2d!
Oct 13 14:49:13 bwmon[1629]: UNKNOW join your network: IP: 192.168.6.254, MAC: 14:14:4b:75:74:43!
Oct 13 14:49:14 dc: 在路由器启动后开启黄灯
Oct 13 14:49:14 【自定义脚本0】: 脚本完成

竟然先输出网络启动的日志后输出启动完成的日志

17,主页被duba网站锁定
今天突然发现,辅机打开浏览器就是duba的网址,而且右下角会自动弹广告,桌面多了几个tmall之类的浏览器链接.....
我辅机之上,只安了一个驱动精灵啊......
本来是先卸载了驱动精灵的,发现浏览器无法恢复,又重新安了下,发现安装的时候,勾都去掉依然会锁定浏览器到duba
安装后在设置里有一个IE的设置,各种解除锁定就可以在IE里改了.....
折腾完果断卸载驱动精灵....
一个搞驱动的也开始耍流氓.....

18,阿里云的IoT
修改配置为自己的key,然后编译demo报错

senrsl@senrsl-T540p:~/test/iot/iotkit-embedded/output/release/bin$ ./mqtt-example loop

[inf] iotx_device_info_init(40): device_info created successfully!

[dbg] iotx_device_info_set(50): start to set device info!

[dbg] iotx_device_info_set(64): device_info set successfully!

[dbg] _calc_hmac_signature(57): | source: clientIdsIgkkh5lOkT.Device01deviceNameDevice01productKeysIgkkh5lOkTtimestamp2524608000000 (89)

[dbg] _calc_hmac_signature(58): | secret: 5bsFvmgSXVmyGhNPBhk4h2DC1xipbhLA (32)

[dbg] _calc_hmac_signature(61): | method: hmacsha1

[dbg] _calc_hmac_signature(74): | signature: 8d85ddd9da0e10aae4c23ab68d0f4f1137fdc877 (40)

[dbg] guider_print_dev_guider_info(220): ....................................................

[dbg] guider_print_dev_guider_info(221):           ProductKey : sIgkkh5lOkT

[dbg] guider_print_dev_guider_info(222):           DeviceName : Device01

[dbg] guider_print_dev_guider_info(223):             DeviceID : sIgkkh5lOkT.Device01

[dbg] guider_print_dev_guider_info(224):         DeviceSecret : 5bsFvmgSXVmyGhNPBhk4h2DC1xipbhLA

[dbg] guider_print_dev_guider_info(225): ....................................................

[dbg] guider_print_dev_guider_info(226):        PartnerID Buf :

[dbg] guider_print_dev_guider_info(227):           Guider URL :

[dbg] guider_print_dev_guider_info(229):       Guider SecMode : 2 (TLS + Direct)

[dbg] guider_print_dev_guider_info(231):     Guider Timestamp : 2524608000000

[dbg] guider_print_dev_guider_info(232): ....................................................

[dbg] guider_print_dev_guider_info(233):          Guider Sign : 8d85ddd9da0e10aae4c23ab68d0f4f1137fdc877

[dbg] guider_print_dev_guider_info(238): ....................................................

[dbg] guider_print_conn_info(198): -----------------------------------------

[dbg] guider_print_conn_info(199):             Host : sIgkkh5lOkT.iot-as-mqtt.cn-shanghai.aliyuncs.com

[dbg] guider_print_conn_info(200):             Port : 1883

[dbg] guider_print_conn_info(201):         UserName : Device01&sIgkkh5lOkT

[dbg] guider_print_conn_info(202):         PassWord : 8d85ddd9da0e10aae4c23ab68d0f4f1137fdc877

[dbg] guider_print_conn_info(203):         ClientID : sIgkkh5lOkT.Device01|securemode=2,timestamp=2524608000000,signmethod=hmacsha1,gw=0|

[dbg] guider_print_conn_info(205):       TLS PubKey : 0x461770 ('-----BEGIN CERTI ...')

[dbg] guider_print_conn_info(208): -----------------------------------------

[inf] iotx_mc_init(1630): MQTT init success!

[inf] _ssl_client_init(164): Loading the CA root certificate ...

cert. version     : 3

serial number     : 04:00:00:00:00:01:15:4B:5A:C3:94

issuer name       : C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA

subject name      : C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA

issued on        : 1998-09-01 12:00:00

expires on        : 2028-01-28 12:00:00

signed using      : RSA with SHA1

RSA key size      : 2048 bits

basic constraints : CA=true

key usage         : Key Cert Sign, CRL Sign

[inf] _ssl_parse_crt(132): crt content:451

[inf] _ssl_client_init(172): ok (0 skipped)

[inf] _TLSConnectNetwork(253): Connecting to /sIgkkh5lOkT.iot-as-mqtt.cn-shanghai.aliyuncs.com/1883...

[inf] _TLSConnectNetwork(258): ok

[inf] _TLSConnectNetwork(263):   . Setting up the SSL/TLS structure...

[inf] _TLSConnectNetwork(273): ok

[inf] _TLSConnectNetwork(308): Performing the SSL/TLS handshake...

[inf] _TLSConnectNetwork(316): ok

[inf] _TLSConnectNetwork(320):   . Verifying peer X.509 certificate..

[inf] _real_confirm(81): certificate verification result: 0x00

[dbg] iotx_mc_connect(1940): start MQTT connection with parameters: clientid=sIgkkh5lOkT.Device01|securemode=2,timestamp=2524608000000,signmethod=hmacsha1,gw=0|, username=Device01&sIgkkh5lOkT, password=8d85ddd9da0e10aae4c23ab68d0f4f1137fdc877

[err] iotx_mc_wait_CONNACK(1187): recvConnackProc error,result = -35

[inf] _network_ssl_disconnect(413): ssl_disconnect

[err] iotx_mc_connect(1952): wait connect ACK timeout, or receive a ACK indicating error!

[inf] iotx_mc_release(2099): mqtt release!

mqtt_client|198 :: MQTT construct failed

---------------------------------------------------

. bytes_total_allocated:    696

. bytes_total_freed:        696

. bytes_total_in_use:       0

. bytes_max_allocated:      552

. bytes_max_in_use:         696

. iterations_allocated:     4

. iterations_freed:         4

. iterations_in_use:        0

. iterations_max_in_use:    4

---------------------------------------------------

main|437 :: out of sample!

senrsl@senrsl-T540p:~/test/iot/iotkit-embedded/output/release/bin$

看配置key的源码:

#if defined(MQTT_ID2_AUTH) && defined(TEST_ID2_DAILY)

    #define PRODUCT_KEY             "OvNmiEYRDSY"

    #define DEVICE_NAME             "sh_online_sample_mqtt"

    #define DEVICE_SECRET           "v9mqGzepKEphLhXmAoiaUIR2HZ7XwTky"

#elif defined(MQTT_ID2_AUTH)

    #define PRODUCT_KEY             "micKUvuzOps"

    #define DEVICE_NAME             "00AAAAAABBBBBB4B645F5800"

    #define DEVICE_SECRET           "v9mqGzepKEphLhXmAoiaUIR2HZ7XwTky"

#else

    #define PRODUCT_KEY             "5KsxxwNYH3t"

    #define DEVICE_NAME             "Device03"

    #define DEVICE_SECRET           "v8ypFF6NG0jkjwGl4zT7vEUKb6c9lwCx"

Pages

東川印記

ubuntu14.04x64在thinkpad-T540px04

2017年12月21日星期四

没有评论 :

发表评论