Javier Pedro's conclusion after trying to build a bridge from Sailfish OS
to Gear was that it wasn't possible because SAP traffic was encrypted using
Samsung's private key. Well, not possible without "doing a geohot"
anyway:
https://git.javispedro.com/cgit/sapd.git/
https://en.wikipedia.org/wiki/PlayStation_3_homebrew#Private_key_compromised
I hope that isn't what is being hit in this case, but it may be.
To my knowledge, this is the first attempt at a Tizen Wearable platform by
any company other than Samsung themselves, so nobody else would have had
the opportunity to discover this flaw until now.
Or maybe it isn't a "flaw" per-se, because SAP and other related transport
details are likely Samsung-proprietary?
Venkateswara: Is there source code for sdb, wrt-installer or pkgcmd?
Or for any obvious target-side software to support talking to these
host-side tools?
On Sun, Jan 24, 2016 at 4:21 PM, Mats Wichmann <m...@osg.samsung.com> wrote:
> On 01/24/16 23:46, Bob Summerwill wrote:
> > I really hope that this ...
> >
> > ## [validate error]: [xmlSecOpenSSLX509StoreVerify(382)] : [x509-store]
> : [X509_verify_cert] : [crypto library function failed]
> [subj=/C=KR/ST=South Korea/L=Suwon/O=Samsung Electronics Co.,
> Ltd./OU=Mobile/CN=GEAR2 DEVELOPER Public CA Class/emailAddress=
> gear2....@samsung.com <mailto:gear2....@samsung.com>;err=20;msg=unable to
> get local issuer certificate]
> >
> > ... doesn't mean that you need to HAVE Samsung's private key to be able
> to do a Tizen Wearable port? And that it means that you need to USE
> Samsung's public key?
>
> me too. perhaps something defaults to using Samsung's key if another one
> is not supplied (though that would still be quite surprising).
>
> Looking forward to hearing more details, actually!
>
>
>
--
b...@summerwill.net
_______________________________________________
General mailing list
General@lists.tizen.org
https://lists.tizen.org/listinfo/general
