From NoCos30 at hotmail.com  Sun Jan  1 19:54:25 2017
From: NoCos30 at hotmail.com (Nocs ...)
Date: Sun, 1 Jan 2017 19:54:25 +0000
Subject: [Tox Support] Merry Christmas And Happy New Year Broz ^.^
In-Reply-To: <CAD=k+Gt6ybtrUQmRYQVhSgGN4w2Yq+DuAuJffb8E02Sss0ccgQ@mail.gmail.com>
References: <HE1PR02MB1290F7B3B5862B94913B64E9B26A0@HE1PR02MB1290.eurprd02.prod.outlook.com>,
 <CAD=k+Gt6ybtrUQmRYQVhSgGN4w2Yq+DuAuJffb8E02Sss0ccgQ@mail.gmail.com>
Message-ID: <HE1PR02MB1290EF92729760F2B64513F7B26C0@HE1PR02MB1290.eurprd02.prod.outlook.com>

Got it nurupo ^.^ thanks and happy new year.


About the secretKey i was asking if it has something to do with the uTox Profile Password which says that "?Tox will automatically start encrypting with this password.There is no way to recover lost passwords."

I guess this is an encryption that is being used by uTox only when it saves the data according the the password the user enters and its not anywhere in the toxcore functions so its ok.

________________________________
From: Support <support-bounces at lists.tox.chat> on behalf of nurupo <nurupocontributions at gmail.com>
Sent: Saturday, December 31, 2016 3:17:07 AM
Cc: support at lists.tox.chat
Subject: Re: [Tox Support] Merry Christmas And Happy New Year Broz ^.^

There are no "secretID" and "publicID", there are secret key and public key, which together is your permanent asymmetric cryptography keypair that toxcore uses. This keypair is your Tox identity, if anyone gains access to the secret key, they can claim your Tox identity, so you should never share your secret key. You should study public-key cryptography if you want to understand public and secret keys in more detail.

Tox Id is pretty much public key and nospam combined, with the third component being checksum bytes, which can be generated given the first two, so it's redundant to store Tox Id along with public key and nospam. It might make sense to do given your use case though.

>If i create the savedata.tox and i keep my toxID, secretID, publicID and NoSpamID as string and i delete the savedata.tox
>am i able to create a savedata.tox with the id`s i have again so i dont need to recreate a new toxID and otherId`s ?

I don't understand what savedata.tox file has to do with anything. I assume it contains the savedata bytes toxcore provides? Are you extracting the Tox Id, public key, secret key and nospam out of it? If so, you shouldn't be doing that, as the format of the savedata bytes is unspecified. You should use these functions to get your public key, secret key and nospam https://github.com/TokTok/c-toxcore/blob/a096c71db867ac83fc3e01e0fbe98573d20f9286/toxcore/tox.h#L1015-L1035. There is also a function to get your Tox Id, which is called address in toxcore https://github.com/TokTok/c-toxcore/blob/a096c71db867ac83fc3e01e0fbe98573d20f9286/toxcore/tox.h#L995-L1004,

If all you want is to keep your Tox identity, all you need to store is your secret key. You can additionally store nospam to keep your previous Tox Id valid for friend requests. Toxcore allows you to create a Tox instance using just your secret key https://github.com/TokTok/c-toxcore/blob/a096c71db867ac83fc3e01e0fbe98573d20f9286/toxcore/tox.h#L405-L422, and you would need to set the saved nospam on the created Tox instance https://github.com/TokTok/c-toxcore/blob/a096c71db867ac83fc3e01e0fbe98573d20f9286/toxcore/tox.h#L1006-L1013.

On Fri, Dec 30, 2016 at 1:59 PM, Nocs ... <NoCos30 at hotmail.com<mailto:NoCos30 at hotmail.com>> wrote:
Hello broz, merry christmas and happy holidays i have some problems with my internet lately so i send you from email the question i have.

If i create the savedata.tox and i keep my toxID, secretID, publicID and NoSpamID as string and i delete the savedata.tox
am i able to create a savedata.tox with the id`s i have again so i dont need to recreate a new toxID and otherId`s ?

Also is there a link to read about the secretID what it does ?
Is it the one to use on passwords and encrypts the data with it where should i look for that ?

Thanks for your reply in advance

_______________________________________________
Support mailing list
Support at lists.tox.chat
https://lists.tox.chat/listinfo/support


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170101/91bf4bf2/attachment.htm>

From nakasun_berry at hotmail.com  Tue Jan  3 06:55:41 2017
From: nakasun_berry at hotmail.com (N Ayumi)
Date: Tue, 3 Jan 2017 06:55:41 +0000
Subject: [Tox Support] Questions about Antox app
Message-ID: <SG2PR06MB0725DF42EA6D9804CF22136E836E0@SG2PR06MB0725.apcprd06.prod.outlook.com>

Hi there,

I just downloaded Antox yesterday and it's working well so far.
I have some questions about its function.
Some websites say that it has "read receipt" but how can I tell if the messages are read?
Also, are we able to see when is the last login of my contacts?

I'd appreciate it if I could receive your reply.
Thanks :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170103/b7fbffb0/attachment.htm>

From ahib.sip at mailnull.com  Tue Jan  3 11:32:08 2017
From: ahib.sip at mailnull.com (AHIB)
Date: Tue, 03 Jan 2017 13:32:08 +0200
Subject: [Tox Support] Antox not booting up on Cyanogenmod
Message-ID: <1483443128.4138581.835773337.35A2536D@webmail.messagingengine.com>

Hi,

I'm reporting a small Antox bug under CyanogenMod 13. Despite Antox being set to boot on startup, with permission from Privacy Guard, and with Privacy Guard's "Bootup List" actually logging it had started at the current boot among other startup apps, Antox doesn't run in the background until I open it manually.

If PG's log is accurate it would mean that Antox does boot up but immediately shuts down before the ROM's interface is ready.

The problem may exist in Android as well since other apps boot normally under CyanogenMod but I can't verify.

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
                          love email again



From fuumind at openmailbox.org  Wed Jan  4 18:50:29 2017
From: fuumind at openmailbox.org (fuumind)
Date: Wed, 04 Jan 2017 19:50:29 +0100
Subject: [Tox Support] Why no bootstrap nodes serving on port 443/80?
In-Reply-To: <fc18318d-ef6f-b026-55ac-7b18f990154c@dvor.me>
References: <1482400588.9237.9.camel@openmailbox.org>
 <203ccbf2-2d87-515b-d5cf-61e2e562ce26@slevermann.de>
 <1482404395.9237.14.camel@openmailbox.org>
 <8fcff4aa-f2ec-326e-e581-fb3aefb850db@dvor.me>
 <1482408371.9237.18.camel@openmailbox.org>
 <fc18318d-ef6f-b026-55ac-7b18f990154c@dvor.me>
Message-ID: <1483555829.3219.4.camel@openmailbox.org>

Hi again!

I visited the library today for the first time after the holidays and
tried to hook up to tox. I still do not get any connection. Checking
the list of bootsrap nodes I can see two listening on port 443. They
are both listed as online but in yellow, not green. What does this
mean? Is there something I need to do in order for my client to connect
using port 443 instead of any 'default' one? Are there any logs I
should be taking a closer look at?

/fuumind

tor 2016-12-22 klockan 16:02 +0100 skrev Dmytro Vorobiov:
> Hello fuumind,
> 
> I've started a bootstrap node on 443 port, it should be added to
> nodes
> list soon.
> 
> ????Dmytro
> 
> On 22/12/16 13:06, fuumind wrote:
> > 
> > Hi Dmytro!
> > 
> > Thanks for the links to the wiki! ~700GiB is a bit out of my league
> > so
> > I guess I'll have to pass on this atm.
> > 
> > /fuumind
> > 
> > tor 2016-12-22 klockan 12:32 +0100 skrev Dmytro Vorobiov:
> > > 
> > > Hello fuumind,
> > > 
> > > According to wiki it takes ~700GiB of total traffic (1/2
> > > incoming,
> > > 1/2
> > > outgoing) per month. See wiki for more info:
> > > 
> > > https://wiki.tox.chat/users/nodes
> > > https://wiki.tox.chat/users/runningnodes
> > > 
> > > ????Dmytro
> > > 
> > > On 22/12/16 11:59, fuumind wrote:
> > > > 
> > > > 
> > > > Thanks Simon!
> > > > 
> > > > How much bandwidth does running a bootstrap node consume per
> > > > month?
> > > > Does it take a lot of work to maintain one? If the parameters
> > > > are
> > > > managable I might try setting up a node as well.
> > > > 
> > > > /fuumind
> > > > 
> > > > tor 2016-12-22 klockan 11:34 +0100 skrev Simon Levermann:
> > > > > 
> > > > > 
> > > > > Hello fuumind,
> > > > > 
> > > > > one possible reason is that a lot of bootstrap nodes are
> > > > > hosted
> > > > > on
> > > > > machines that are not exclusively tox bootstrap nodes. And a
> > > > > very
> > > > > common
> > > > > thing to have on a VPS/root server is a web server, and that
> > > > > usually
> > > > > takes up ports 80/443.
> > > > > 
> > > > > That being said, maybe I'll get around to setting up a 443
> > > > > node
> > > > > on my
> > > > > server (it has a second IP anyhow). But definitely not before
> > > > > the
> > > > > end
> > > > > of
> > > > > the year, it is vacation time for me after today.
> > > > > 
> > > > > Cheers
> > > > > 
> > > > > Simon
> > > > > 
> > > > > 
> > > > > On 22.12.2016 10:56, fuumind wrote:
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Hi all!
> > > > > > 
> > > > > > Is there a special reason why no bootstrap nodes are on
> > > > > > port
> > > > > > 443/80?
> > > > > > Like is it more difficult / dangerous? Reason I'm asking is
> > > > > > I
> > > > > > currently
> > > > > > am unable to use tox at my library because their firewall
> > > > > > only
> > > > > > allows
> > > > > > 80/443 outgoing and there are no available nodes serving on
> > > > > > those
> > > > > > ports.
> > > > > > 
> > > > > > Thanks!
> > > > > > fuumind
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Support mailing list
> > > > > > Support at lists.tox.chat
> > > > > > https://lists.tox.chat/listinfo/support
> > > > > _______________________________________________
> > > > > Support mailing list
> > > > > Support at lists.tox.chat
> > > > > https://lists.tox.chat/listinfo/support
> > > > _______________________________________________
> > > > Support mailing list
> > > > Support at lists.tox.chat
> > > > https://lists.tox.chat/listinfo/support
> > > > 
> > > _______________________________________________
> > > Support mailing list
> > > Support at lists.tox.chat
> > > https://lists.tox.chat/listinfo/support
> > _______________________________________________
> > Support mailing list
> > Support at lists.tox.chat
> > https://lists.tox.chat/listinfo/support
> > 
> _______________________________________________
> Support mailing list
> Support at lists.tox.chat
> https://lists.tox.chat/listinfo/support


From zetok at openmailbox.org  Wed Jan  4 18:56:04 2017
From: zetok at openmailbox.org (Zetok Zalbavar)
Date: Wed, 4 Jan 2017 18:56:04 +0000
Subject: [Tox Support] Questions about Antox app
In-Reply-To: <SG2PR06MB0725DF42EA6D9804CF22136E836E0@SG2PR06MB0725.apcprd06.prod.outlook.com>
References: <SG2PR06MB0725DF42EA6D9804CF22136E836E0@SG2PR06MB0725.apcprd06.prod.outlook.com>
Message-ID: <74908587-4c73-ad5a-6cd7-dbb685480d47@openmailbox.org>

On 03.01.2017 06:55, N Ayumi wrote:
> Hi there,
> 
> I just downloaded Antox yesterday and it's working well so far.
> I have some questions about its function.
> Some websites say that it has "read receipt" but how can I tell if the messages are read?

Antox only indicates whether given message was delivered.

> Also, are we able to see when is the last login of my contacts?
> 
> I'd appreciate it if I could receive your reply.
> Thanks :-)

If it's not possible to see that already, you should open an issue about
it on Antox github repository: https://github.com/Antox/Antox/issues/new

-- 

Kind regards,
Zetok Zalbavar
----
tox:29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.tox.chat/pipermail/support/attachments/20170104/877ea9b9/attachment.sig>

From zetok at openmailbox.org  Wed Jan  4 18:58:17 2017
From: zetok at openmailbox.org (Zetok Zalbavar)
Date: Wed, 4 Jan 2017 18:58:17 +0000
Subject: [Tox Support] Antox not booting up on Cyanogenmod
In-Reply-To: <1483443128.4138581.835773337.35A2536D@webmail.messagingengine.com>
References: <1483443128.4138581.835773337.35A2536D@webmail.messagingengine.com>
Message-ID: <954cac01-5730-f7cc-1534-c7b54272cef9@openmailbox.org>

On 03.01.2017 11:32, AHIB wrote:
> Hi,
> 
> I'm reporting a small Antox bug under CyanogenMod 13. Despite Antox being set to boot on startup, with permission from Privacy Guard, and with Privacy Guard's "Bootup List" actually logging it had started at the current boot among other startup apps, Antox doesn't run in the background until I open it manually.
> 
> If PG's log is accurate it would mean that Antox does boot up but immediately shuts down before the ROM's interface is ready.
> 
> The problem may exist in Android as well since other apps boot normally under CyanogenMod but I can't verify.
> 

It would be good to open an issue about it on Antox repo if there isn't
one already: https://github.com/Antox/Antox/issues/new
-- 

Kind regards,
Zetok Zalbavar
----
tox:29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.tox.chat/pipermail/support/attachments/20170104/fff54b10/attachment.sig>

From d at dvor.me  Wed Jan  4 19:20:45 2017
From: d at dvor.me (Dmytro Vorobiov)
Date: Wed, 4 Jan 2017 20:20:45 +0100
Subject: [Tox Support] Why no bootstrap nodes serving on port 443/80?
In-Reply-To: <1483555829.3219.4.camel@openmailbox.org>
References: <1482400588.9237.9.camel@openmailbox.org>
 <203ccbf2-2d87-515b-d5cf-61e2e562ce26@slevermann.de>
 <1482404395.9237.14.camel@openmailbox.org>
 <8fcff4aa-f2ec-326e-e581-fb3aefb850db@dvor.me>
 <1482408371.9237.18.camel@openmailbox.org>
 <fc18318d-ef6f-b026-55ac-7b18f990154c@dvor.me>
 <1483555829.3219.4.camel@openmailbox.org>
Message-ID: <05a8d4e0-b555-4235-0ba4-9e1a02ec6baa@dvor.me>

Hello fuumind,

What tox client are you using? Nodes are updated on the website, but
client might have outdated ones.

You can try to update it to latest version.

    Dmytro

On 04/01/17 19:50, fuumind wrote:
> Hi again!
> 
> I visited the library today for the first time after the holidays and
> tried to hook up to tox. I still do not get any connection. Checking
> the list of bootsrap nodes I can see two listening on port 443. They
> are both listed as online but in yellow, not green. What does this
> mean? Is there something I need to do in order for my client to connect
> using port 443 instead of any 'default' one? Are there any logs I
> should be taking a closer look at?
> 
> /fuumind
> 
> tor 2016-12-22 klockan 16:02 +0100 skrev Dmytro Vorobiov:
>> Hello fuumind,
>>
>> I've started a bootstrap node on 443 port, it should be added to
>> nodes
>> list soon.
>>
>>     Dmytro
>>
>> On 22/12/16 13:06, fuumind wrote:
>>>
>>> Hi Dmytro!
>>>
>>> Thanks for the links to the wiki! ~700GiB is a bit out of my league
>>> so
>>> I guess I'll have to pass on this atm.
>>>
>>> /fuumind
>>>
>>> tor 2016-12-22 klockan 12:32 +0100 skrev Dmytro Vorobiov:
>>>>
>>>> Hello fuumind,
>>>>
>>>> According to wiki it takes ~700GiB of total traffic (1/2
>>>> incoming,
>>>> 1/2
>>>> outgoing) per month. See wiki for more info:
>>>>
>>>> https://wiki.tox.chat/users/nodes
>>>> https://wiki.tox.chat/users/runningnodes
>>>>
>>>>     Dmytro
>>>>
>>>> On 22/12/16 11:59, fuumind wrote:
>>>>>
>>>>>
>>>>> Thanks Simon!
>>>>>
>>>>> How much bandwidth does running a bootstrap node consume per
>>>>> month?
>>>>> Does it take a lot of work to maintain one? If the parameters
>>>>> are
>>>>> managable I might try setting up a node as well.
>>>>>
>>>>> /fuumind
>>>>>
>>>>> tor 2016-12-22 klockan 11:34 +0100 skrev Simon Levermann:
>>>>>>
>>>>>>
>>>>>> Hello fuumind,
>>>>>>
>>>>>> one possible reason is that a lot of bootstrap nodes are
>>>>>> hosted
>>>>>> on
>>>>>> machines that are not exclusively tox bootstrap nodes. And a
>>>>>> very
>>>>>> common
>>>>>> thing to have on a VPS/root server is a web server, and that
>>>>>> usually
>>>>>> takes up ports 80/443.
>>>>>>
>>>>>> That being said, maybe I'll get around to setting up a 443
>>>>>> node
>>>>>> on my
>>>>>> server (it has a second IP anyhow). But definitely not before
>>>>>> the
>>>>>> end
>>>>>> of
>>>>>> the year, it is vacation time for me after today.
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> Simon
>>>>>>
>>>>>>
>>>>>> On 22.12.2016 10:56, fuumind wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi all!
>>>>>>>
>>>>>>> Is there a special reason why no bootstrap nodes are on
>>>>>>> port
>>>>>>> 443/80?
>>>>>>> Like is it more difficult / dangerous? Reason I'm asking is
>>>>>>> I
>>>>>>> currently
>>>>>>> am unable to use tox at my library because their firewall
>>>>>>> only
>>>>>>> allows
>>>>>>> 80/443 outgoing and there are no available nodes serving on
>>>>>>> those
>>>>>>> ports.
>>>>>>>
>>>>>>> Thanks!
>>>>>>> fuumind
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Support mailing list
>>>>>>> Support at lists.tox.chat
>>>>>>> https://lists.tox.chat/listinfo/support
>>>>>> _______________________________________________
>>>>>> Support mailing list
>>>>>> Support at lists.tox.chat
>>>>>> https://lists.tox.chat/listinfo/support
>>>>> _______________________________________________
>>>>> Support mailing list
>>>>> Support at lists.tox.chat
>>>>> https://lists.tox.chat/listinfo/support
>>>>>
>>>> _______________________________________________
>>>> Support mailing list
>>>> Support at lists.tox.chat
>>>> https://lists.tox.chat/listinfo/support
>>> _______________________________________________
>>> Support mailing list
>>> Support at lists.tox.chat
>>> https://lists.tox.chat/listinfo/support
>>>
>> _______________________________________________
>> Support mailing list
>> Support at lists.tox.chat
>> https://lists.tox.chat/listinfo/support
> _______________________________________________
> Support mailing list
> Support at lists.tox.chat
> https://lists.tox.chat/listinfo/support
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: OpenPGP digital signature
URL: <http://lists.tox.chat/pipermail/support/attachments/20170104/a5b3588a/attachment.sig>

From nurupocontributions at gmail.com  Wed Jan  4 19:33:57 2017
From: nurupocontributions at gmail.com (nurupo)
Date: Wed, 4 Jan 2017 14:33:57 -0500
Subject: [Tox Support] Merry Christmas And Happy New Year Broz ^.^
In-Reply-To: <HE1PR02MB1290EF92729760F2B64513F7B26C0@HE1PR02MB1290.eurprd02.prod.outlook.com>
References: <HE1PR02MB1290F7B3B5862B94913B64E9B26A0@HE1PR02MB1290.eurprd02.prod.outlook.com>
 <CAD=k+Gt6ybtrUQmRYQVhSgGN4w2Yq+DuAuJffb8E02Sss0ccgQ@mail.gmail.com>
 <HE1PR02MB1290EF92729760F2B64513F7B26C0@HE1PR02MB1290.eurprd02.prod.outlook.com>
Message-ID: <CAD=k+GvhcTYGFupDLtVkq7rfEooicdEyczy_zocvLVxxOzBHfA@mail.gmail.com>

Clients generally use the libtoxencryptsave for the savedata encryption.

On Sun, Jan 1, 2017 at 2:54 PM, Nocs ... <NoCos30 at hotmail.com> wrote:

> Got it nurupo ^.^ thanks and happy new year.
>
>
> About the secretKey i was asking if it has something to do with the uTox
> Profile Password which says that "?Tox will automatically start encrypting
> with this password.There is no way to recover lost passwords."
>
> I guess this is an encryption that is being used by uTox only when it
> saves the data according the the password the user enters and its not
> anywhere in the toxcore functions so its ok.
> ------------------------------
> *From:* Support <support-bounces at lists.tox.chat> on behalf of nurupo <
> nurupocontributions at gmail.com>
> *Sent:* Saturday, December 31, 2016 3:17:07 AM
> *Cc:* support at lists.tox.chat
> *Subject:* Re: [Tox Support] Merry Christmas And Happy New Year Broz ^.^
>
> There are no "secretID" and "publicID", there are secret key and public
> key, which together is your permanent asymmetric cryptography keypair that
> toxcore uses. This keypair is your Tox identity, if anyone gains access to
> the secret key, they can claim your Tox identity, so you should never share
> your secret key. You should study public-key cryptography if you want to
> understand public and secret keys in more detail.
>
> Tox Id is pretty much public key and nospam combined, with the third
> component being checksum bytes, which can be generated given the first two,
> so it's redundant to store Tox Id along with public key and nospam. It
> might make sense to do given your use case though.
>
> >If i create the savedata.tox and i keep my toxID, secretID, publicID and
> NoSpamID as string and i delete the savedata.tox
> >am i able to create a savedata.tox with the id`s i have again so i dont
> need to recreate a new toxID and otherId`s ?
>
> I don't understand what savedata.tox file has to do with anything. I
> assume it contains the savedata bytes toxcore provides? Are you extracting
> the Tox Id, public key, secret key and nospam out of it? If so, you
> shouldn't be doing that, as the format of the savedata bytes is
> unspecified. You should use these functions to get your public key, secret
> key and nospam https://github.com/TokTok/c-toxcore/blob/
> a096c71db867ac83fc3e01e0fbe98573d20f9286/toxcore/tox.h#L1015-L1035. There
> is also a function to get your Tox Id, which is called address in toxcore
> https://github.com/TokTok/c-toxcore/blob/a096c71db867ac83fc3e01e0fbe985
> 73d20f9286/toxcore/tox.h#L995-L1004,
>
> If all you want is to keep your Tox identity, all you need to store is
> your secret key. You can additionally store nospam to keep your previous
> Tox Id valid for friend requests. Toxcore allows you to create a Tox
> instance using just your secret key https://github.com/TokTok/
> c-toxcore/blob/a096c71db867ac83fc3e01e0fbe985
> 73d20f9286/toxcore/tox.h#L405-L422, and you would need to set the saved
> nospam on the created Tox instance https://github.com/TokTok/c-
> toxcore/blob/a096c71db867ac83fc3e01e0fbe98573d20f9286/toxcore/tox.h#
> L1006-L1013.
>
> On Fri, Dec 30, 2016 at 1:59 PM, Nocs ... <NoCos30 at hotmail.com> wrote:
>
>> Hello broz, merry christmas and happy holidays i have some problems with
>> my internet lately so i send you from email the question i have.
>>
>> If i create the savedata.tox and i keep my toxID, secretID, publicID and
>> NoSpamID as string and i delete the savedata.tox
>> am i able to create a savedata.tox with the id`s i have again so i dont
>> need to recreate a new toxID and otherId`s ?
>>
>> Also is there a link to read about the secretID what it does ?
>> Is it the one to use on passwords and encrypts the data with it where
>> should i look for that ?
>>
>> Thanks for your reply in advance
>>
>> _______________________________________________
>> Support mailing list
>> Support at lists.tox.chat
>> https://lists.tox.chat/listinfo/support
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170104/341a5b5c/attachment.htm>

From fuumind at openmailbox.org  Thu Jan  5 07:04:49 2017
From: fuumind at openmailbox.org (fuumind)
Date: Thu, 05 Jan 2017 08:04:49 +0100
Subject: [Tox Support] Why no bootstrap nodes serving on port 443/80?
In-Reply-To: <05a8d4e0-b555-4235-0ba4-9e1a02ec6baa@dvor.me>
References: <1482400588.9237.9.camel@openmailbox.org>
 <203ccbf2-2d87-515b-d5cf-61e2e562ce26@slevermann.de>
 <1482404395.9237.14.camel@openmailbox.org>
 <8fcff4aa-f2ec-326e-e581-fb3aefb850db@dvor.me>
 <1482408371.9237.18.camel@openmailbox.org>
 <fc18318d-ef6f-b026-55ac-7b18f990154c@dvor.me>
 <1483555829.3219.4.camel@openmailbox.org>
 <05a8d4e0-b555-4235-0ba4-9e1a02ec6baa@dvor.me>
Message-ID: <1483599889.5059.12.camel@openmailbox.org>

Ok, so the list of bootstrap nodes is not updated dynamically in the
clients...?

I've tried with Ricin (from source) and utox (from pkg.tox.chat.) utox
is updated to the latest available version. I'll try installing the
latest code from github for Ricin for now to see if things start
working.

/fuumind

ons 2017-01-04 klockan 20:20 +0100 skrev Dmytro Vorobiov:
> Hello fuumind,
> 
> What tox client are you using? Nodes are updated on the website, but
> client might have outdated ones.
> 
> You can try to update it to latest version.
> 
> ????Dmytro
> 
> On 04/01/17 19:50, fuumind wrote:
> > 
> > Hi again!
> > 
> > I visited the library today for the first time after the holidays
> > and
> > tried to hook up to tox. I still do not get any connection.
> > Checking
> > the list of bootsrap nodes I can see two listening on port 443.
> > They
> > are both listed as online but in yellow, not green. What does this
> > mean? Is there something I need to do in order for my client to
> > connect
> > using port 443 instead of any 'default' one? Are there any logs I
> > should be taking a closer look at?
> > 
> > /fuumind
> > 
> > tor 2016-12-22 klockan 16:02 +0100 skrev Dmytro Vorobiov:
> > > 
> > > Hello fuumind,
> > > 
> > > I've started a bootstrap node on 443 port, it should be added to
> > > nodes
> > > list soon.
> > > 
> > > ????Dmytro
> > > 
> > > On 22/12/16 13:06, fuumind wrote:
> > > > 
> > > > 
> > > > Hi Dmytro!
> > > > 
> > > > Thanks for the links to the wiki! ~700GiB is a bit out of my
> > > > league
> > > > so
> > > > I guess I'll have to pass on this atm.
> > > > 
> > > > /fuumind
> > > > 
> > > > tor 2016-12-22 klockan 12:32 +0100 skrev Dmytro Vorobiov:
> > > > > 
> > > > > 
> > > > > Hello fuumind,
> > > > > 
> > > > > According to wiki it takes ~700GiB of total traffic (1/2
> > > > > incoming,
> > > > > 1/2
> > > > > outgoing) per month. See wiki for more info:
> > > > > 
> > > > > https://wiki.tox.chat/users/nodes
> > > > > https://wiki.tox.chat/users/runningnodes
> > > > > 
> > > > > ????Dmytro
> > > > > 
> > > > > On 22/12/16 11:59, fuumind wrote:
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Thanks Simon!
> > > > > > 
> > > > > > How much bandwidth does running a bootstrap node consume
> > > > > > per
> > > > > > month?
> > > > > > Does it take a lot of work to maintain one? If the
> > > > > > parameters
> > > > > > are
> > > > > > managable I might try setting up a node as well.
> > > > > > 
> > > > > > /fuumind
> > > > > > 
> > > > > > tor 2016-12-22 klockan 11:34 +0100 skrev Simon Levermann:
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > Hello fuumind,
> > > > > > > 
> > > > > > > one possible reason is that a lot of bootstrap nodes are
> > > > > > > hosted
> > > > > > > on
> > > > > > > machines that are not exclusively tox bootstrap nodes.
> > > > > > > And a
> > > > > > > very
> > > > > > > common
> > > > > > > thing to have on a VPS/root server is a web server, and
> > > > > > > that
> > > > > > > usually
> > > > > > > takes up ports 80/443.
> > > > > > > 
> > > > > > > That being said, maybe I'll get around to setting up a
> > > > > > > 443
> > > > > > > node
> > > > > > > on my
> > > > > > > server (it has a second IP anyhow). But definitely not
> > > > > > > before
> > > > > > > the
> > > > > > > end
> > > > > > > of
> > > > > > > the year, it is vacation time for me after today.
> > > > > > > 
> > > > > > > Cheers
> > > > > > > 
> > > > > > > Simon
> > > > > > > 
> > > > > > > 
> > > > > > > On 22.12.2016 10:56, fuumind wrote:
> > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Hi all!
> > > > > > > > 
> > > > > > > > Is there a special reason why no bootstrap nodes are on
> > > > > > > > port
> > > > > > > > 443/80?
> > > > > > > > Like is it more difficult / dangerous? Reason I'm
> > > > > > > > asking is
> > > > > > > > I
> > > > > > > > currently
> > > > > > > > am unable to use tox at my library because their
> > > > > > > > firewall
> > > > > > > > only
> > > > > > > > allows
> > > > > > > > 80/443 outgoing and there are no available nodes
> > > > > > > > serving on
> > > > > > > > those
> > > > > > > > ports.
> > > > > > > > 
> > > > > > > > Thanks!
> > > > > > > > fuumind
> > > > > > > > 
> > > > > > > > _______________________________________________
> > > > > > > > Support mailing list
> > > > > > > > Support at lists.tox.chat
> > > > > > > > https://lists.tox.chat/listinfo/support
> > > > > > > _______________________________________________
> > > > > > > Support mailing list
> > > > > > > Support at lists.tox.chat
> > > > > > > https://lists.tox.chat/listinfo/support
> > > > > > _______________________________________________
> > > > > > Support mailing list
> > > > > > Support at lists.tox.chat
> > > > > > https://lists.tox.chat/listinfo/support
> > > > > > 
> > > > > _______________________________________________
> > > > > Support mailing list
> > > > > Support at lists.tox.chat
> > > > > https://lists.tox.chat/listinfo/support
> > > > _______________________________________________
> > > > Support mailing list
> > > > Support at lists.tox.chat
> > > > https://lists.tox.chat/listinfo/support
> > > > 
> > > _______________________________________________
> > > Support mailing list
> > > Support at lists.tox.chat
> > > https://lists.tox.chat/listinfo/support
> > _______________________________________________
> > Support mailing list
> > Support at lists.tox.chat
> > https://lists.tox.chat/listinfo/support
> > 


From lukastaschler at posteo.de  Wed Jan 11 00:10:56 2017
From: lukastaschler at posteo.de (Lukas Taschler)
Date: Wed, 11 Jan 2017 01:10:56 +0100
Subject: [Tox Support] Fwd: qtox starting error/utox not starting at all/on
	OSX 10.8.5
References: <3E370FE6-BD0D-4806-9896-EAC1D7B9F96B@posteo.de>
Message-ID: <23624693-5E01-43AC-A090-F71793BB4EF3@posteo.de>

> hey all!
> tried to install TOX chat. Its not working for me. Both .app's are in the applications-folder but when I start qtox I receive an error-message(attached in the end of email.)
> and u tox just doesn'T do anything. The symbol pops up for milli-second and then disappears.
> Thanks for helping!!
> 
> PS: I also have Linux Mint Cinnamon where I didnd't find anthing how to install it?



> 
> Process:         qtox [700]
> Path:            /Applications/qTox.app/Contents/MacOS/qtox
> Identifier:      chat.tox.qtox
> Version:         v1.5.1 (1.4.1)
> Code Type:       X86-64 (Native)
> Parent Process:  launchd [163]
> User ID:         501
> 
> Date/Time:       2017-01-11 00:52:10.343 +0100
> OS Version:      Mac OS X 10.8.5 (12F45)
> Report Version:  10
> 
> Interval Since Last Report:          5308700 sec
> Crashes Since Last Report:           104
> Per-App Crashes Since Last Report:   6
> Anonymous UUID:                      1E27B826-43BB-2169-1762-52F077B2193A
> 
> Crashed Thread:  0
> 
> Exception Type:  EXC_BREAKPOINT (SIGTRAP)
> Exception Codes: 0x0000000000000002, 0x0000000000000000
> 
> Application Specific Information:
> dyld: launch, loading dependent libraries
> 
> Dyld Error Message:
>  Library not loaded: /usr/local/Cellar/ffmpeg/3.1.2/lib/libavcodec.57.dylib
>  Referenced from: /Applications/qTox.app/Contents/Frameworks/libavformat.57.dylib
>  Reason: image not found
> 
> Binary Images:
>       0x100857000 -        0x100d8dff7 +chat.tox.qtox (v1.5.1 - 1.4.1) <11FC7725-2719-3092-BBF5-A26340D856C8> /Applications/qTox.app/Contents/MacOS/qtox
>       0x100e54000 -        0x100e7dfff +libtoxcore.0.dylib (0) <8CF3575D-83FA-3BA9-B67E-B48002F83E90> /Applications/qTox.app/Contents/Frameworks/libtoxcore.0.dylib
>       0x100e8c000 -        0x100eedff7 +libtoxav.0.dylib (0) <1F017116-168F-387F-B01C-60838CAFC156> /Applications/qTox.app/Contents/Frameworks/libtoxav.0.dylib
>       0x100eff000 -        0x100efffff +libtoxencryptsave.0.dylib (0) <711C548A-5791-3A44-9D16-CCFA98DC69AE> /Applications/qTox.app/Contents/Frameworks/libtoxencryptsave.0.dylib
>       0x100f04000 -        0x100f04fff +libtoxdns.0.dylib (0) <91BC097D-2B03-389E-A096-BC12FC8B7000> /Applications/qTox.app/Contents/Frameworks/libtoxdns.0.dylib
>       0x100f07000 -        0x100f4bfef +libsodium.13.dylib (0) <3961F626-80BB-34E8-8B6A-C07F5A70A81F> /Applications/qTox.app/Contents/Frameworks/libsodium.13.dylib
>       0x100f5d000 -        0x100f9afff +libopus.0.dylib (0) <202EE14C-AD43-34C8-8D5A-986A4E2128D0> /Applications/qTox.app/Contents/Frameworks/libopus.0.dylib
>       0x100fa4000 -        0x100fcffff  com.apple.audio.OpenAL (1.6 - 1.6) <0FBA7491-B817-39EE-8898-FF88C9485B50> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL
>       0x100fe4000 -        0x101151ff7 +libavformat.57.dylib (0) <F64B2761-5740-31B3-8462-20B73F251C02> /Applications/qTox.app/Contents/Frameworks/libavformat.57.dylib
>       0x101199000 -        0x1011a8fff +libavdevice.57.dylib (0) <F370DC99-0BE0-3325-A434-FE138F4A5A34> /Applications/qTox.app/Contents/Frameworks/libavdevice.57.dylib
>       0x1011b3000 -        0x101deffff +libavcodec.57.dylib (0) <6DDB7574-DE20-3100-92E7-22AFD2DB4A49> /Applications/qTox.app/Contents/Frameworks/libavcodec.57.dylib
>       0x102433000 -        0x102478fff +libavutil.55.dylib (0) <071E6732-43EF-3708-98D6-9665FDF1CA42> /Applications/qTox.app/Contents/Frameworks/libavutil.55.dylib
>       0x10249d000 -        0x102515ff7 +libswscale.4.dylib (0) <77805803-C5FE-3BAF-9E34-F995D1459DE6> /Applications/qTox.app/Contents/Frameworks/libswscale.4.dylib
>       0x102529000 -        0x102653fff  com.apple.avfoundation (2.0 - 361.40.1) <82E0EE8C-6026-33AD-8947-B20D2ED7B2E1> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
>       0x10273d000 -        0x102a9cfff  com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
>       0x102cc6000 -        0x102d11fff  com.apple.CoreMedia (1.0 - 926.106) <64467905-48DC-37F9-9F32-186768CF2640> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
>       0x102d3b000 -        0x102d3bfff  com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
>       0x102d41000 -        0x102d47fff +libqrencode.3.dylib (0) <952B29C4-6660-3D9E-953D-3E26900AAAE7> /Applications/qTox.app/Contents/Frameworks/libqrencode.3.dylib
>       0x102d4f000 -        0x102dd4ff7 +libsqlcipher.0.dylib (0) <DF64C362-EC9F-3EF4-9A41-59087C2C8E61> /Applications/qTox.app/Contents/Frameworks/libsqlcipher.0.dylib
>       0x102de5000 -        0x102e53ff7  com.apple.framework.IOKit (2.0.1 - 755.42.1) <A90038ED-48F2-3CC9-A042-53A3D7985844> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
>       0x102e87000 -        0x103071ff7  com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
>       0x1031d0000 -        0x10320ffff +org.qt-project.QtOpenGL (5.6 - 5.6.1) <10E93C8F-36E7-342A-B786-22A71274F468> /Applications/qTox.app/Contents/Frameworks/QtOpenGL.framework/Versions/5/QtOpenGL
>       0x103232000 -        0x10373aff7 +org.qt-project.QtWidgets (5.6 - 5.6.1) <7794C7F4-F304-3EAB-928B-A5444072F9DF> /Applications/qTox.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets
>       0x103894000 -        0x103d65ff7 +org.qt-project.QtGui (5.6 - 5.6.1) <A5B23072-8C58-31D0-9985-BFBFF18A2882> /Applications/qTox.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui
>       0x103e58000 -        0x104376fff +org.qt-project.QtCore (5.6 - 5.6.1) <E64B0A9B-A902-38B2-8CA3-155851D8222D> /Applications/qTox.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore
>       0x104423000 -        0x104429fff  com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
>       0x10443a000 -        0x104475fff +org.qt-project.QtSvg (5.6 - 5.6.1) <BCCB3E33-CD51-3575-9D3D-C74A2863BB38> /Applications/qTox.app/Contents/Frameworks/QtSvg.framework/Versions/5/QtSvg
>       0x104495000 -        0x1045a1fff +org.qt-project.QtNetwork (5.6 - 5.6.1) <0C9CD7A6-2805-3CF4-9CB9-46CDFBA7B83E> /Applications/qTox.app/Contents/Frameworks/QtNetwork.framework/Versions/5/QtNetwork
>       0x1045e1000 -        0x104616ff7 +org.qt-project.QtXml (5.6 - 5.6.1) <4FF7C0C6-DBBE-3F53-935F-A5811886A798> /Applications/qTox.app/Contents/Frameworks/QtXml.framework/Versions/5/QtXml
>       0x104628000 -        0x104654ff7 +org.qt-project.QtSql (5.6 - 5.6.1) <311D52D3-FA91-3ED3-A646-E1C09C6E7C67> /Applications/qTox.app/Contents/Frameworks/QtSql.framework/Versions/5/QtSql
>       0x104666000 -        0x104675fff  com.apple.opengl (1.8.10 - 1.8.10) <AD49CF56-B7C1-3598-8610-58532FC41345> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
>       0x104682000 -        0x104687fff  com.apple.agl (3.2.1 - AGL-3.2.1) <57EC66DD-031A-3A8E-B067-72DB72B405E7> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
>       0x104695000 -        0x1046fdff7  libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
>       0x104757000 -        0x104758ff7  libSystem.B.dylib (169.3) <5ED23C27-47AF-3C93-984A-172751CF745A> /usr/lib/libSystem.B.dylib
>       0x104761000 -        0x10487992f  libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
>       0x10489a000 -        0x10489ffff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
>       0x1048a5000 -        0x1048b3fff  libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
>       0x1048c4000 -        0x1048c9fff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
>       0x1048d8000 -        0x1048dffff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
>       0x1048e8000 -        0x1048fdff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
>       0x104918000 -        0x104919ff7  libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
>       0x104923000 -        0x104926ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
>       0x104933000 -        0x104933fff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
>       0x104939000 -        0x104941fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
>       0x10494e000 -        0x104954fff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
>       0x10495e000 -        0x104960fff  libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib
>       0x10496a000 -        0x10496bff7  libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib
>       0x104977000 -        0x104978fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
>       0x104983000 -        0x104a4fff7  libsystem_c.dylib (825.40.1) <543B05AE-CFA5-3EFE-8E58-77225411BA6B> /usr/lib/system/libsystem_c.dylib
>       0x104a98000 -        0x104aa0ff7  libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib
>       0x104aac000 -        0x104ae2fff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
>       0x104afd000 -        0x104b18ff7  libsystem_kernel.dylib (2050.48.12) <4B7993C3-F62D-3AC1-AF92-414A0D6EED5E> /usr/lib/system/libsystem_kernel.dylib
>       0x104b2e000 -        0x104b5cff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
>       0x104b6c000 -        0x104b7aff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
>       0x104b88000 -        0x104b93fff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
>       0x104ba1000 -        0x104ba2ff7  libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib
>       0x104bae000 -        0x104bb0ff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
>       0x104bb9000 -        0x104bbfff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
>       0x104bcd000 -        0x104befff7  libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
>       0x104c0d000 -        0x104c5cff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
>       0x104c6f000 -        0x104cbbff7  libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
>       0x104cd5000 -        0x104cfaff7  libc++abi.dylib (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /usr/lib/libc++abi.dylib
>       0x104d2c000 -        0x104d2dfff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
>       0x104d35000 -        0x104d98fff  com.apple.audio.CoreAudio (4.1.2 - 4.1.2) <FEAB83AB-1DE5-3813-BA48-7A7F2374CCF0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
>       0x104dbd000 -        0x104f0ffff  com.apple.audio.toolbox.AudioToolbox (1.9.2 - 1.9.2) <DC5F3D1B-036A-37DE-BC24-7636DC95EA1C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
>       0x104f99000 -        0x104f99ffd  com.apple.audio.units.AudioUnit (1.9.2 - 1.9.2) <6D314680-7409-3BC7-A807-36341411AF9A> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
>       0x104fa6000 -        0x104fa6fff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
>       0x104fb0000 -        0x105019fff  libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
>       0x105083000 -        0x105354ff7  com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security
>       0x105488000 -        0x105688fff  libicucore.A.dylib (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /usr/lib/libicucore.A.dylib
>       0x10572e000 -        0x105740ff7  libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
>       0x105748000 -        0x10575bff7  libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
>       0x105766000 -        0x105774ff7  libkxld.dylib (2050.48.12) <B8F7ED1F-CF84-3777-9183-0A1C513DF81F> /usr/lib/system/libkxld.dylib
>       0x105780000 -        0x10578fff7  libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
>       0x10579b000 -        0x105898fff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
>       0x1058b3000 -        0x1058b7fff  libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
>       0x1058bd000 -        0x1058bdfff  libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
>       0x1058c6000 -        0x1058d3fff  libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
>       0x1058dc000 -        0x1059d9ff7  libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
>       0x105a13000 -        0x105a13fff  com.apple.vecLib (3.8 - vecLib 3.8) <6CBBFDC4-415C-3910-9558-B67176447789> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
>       0x105a1b000 -        0x105ab5fff  libvMisc.dylib (380.10) <A7F12764-A94C-36EB-88E0-F826F5AF55B4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
>       0x105ac1000 -        0x105b29fff  libvDSP.dylib (380.10) <3CA154A3-1BE5-3CF4-BE48-F0A719A963BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
>       0x105b38000 -        0x105f2ffff  libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
>       0x105f94000 -        0x10611afff  libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
>       0x10614c000 -        0x1062c1ff7  com.apple.CFNetwork (596.5 - 596.5) <22372475-6EF4-3A04-83FC-C061FE4717B3> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
>       0x106382000 -        0x106699ff7  com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
>       0x106715000 -        0x106796fff  com.apple.Metadata (10.7.0 - 707.12) <69E3EEF7-8B7B-3652-8320-B8E885370E56> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
>       0x1067ed000 -        0x106893ff7  com.apple.CoreServices.OSServices (557.6 - 557.6) <FFDDD2D8-690D-388F-A48F-4750A792D2CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
>       0x1068f4000 -        0x106981ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
>       0x1069c6000 -        0x106a25fff  com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
>       0x106a4f000 -        0x106b00fff  com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
>       0x106b59000 -        0x106b8aff7  com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
>       0x106bb4000 -        0x106c05ff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
>       0x106c35000 -        0x106c3cfff  com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
>       0x106c48000 -        0x106c55ff7  com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
>       0x106c65000 -        0x106cd2ff7  com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
>       0x106d0d000 -        0x106d11ff7  com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
>       0x106d1d000 -        0x106d1efff  liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
>       0x106d26000 -        0x106d47ff7  libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
>       0x106d56000 -        0x106d6dfff  com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
>       0x106d77000 -        0x106d8efff  com.apple.CFOpenDirectory (10.8 - 151.10) <F7AD9844-559A-366E-8192-BB4FCF9EE7A3> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
>       0x106db0000 -        0x106ddbfff  libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
>    0x7fff60457000 -     0x7fff6048b93f  dyld (210.2.3) <6900F2BA-DB48-3B78-B668-58FC0CF6BCB8> /usr/lib/dyld
> 
> Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core 2 Duo, 2.26 GHz, 8 GB, SMC 1.47f2
> Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
> Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0000, 0x000000000000000000000000000000000000
> Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0000, 0x000000000000000000000000000000000000
> AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.17)
> Bluetooth: Version 4.1.7f4 12974, 3 service, 21 devices, 3 incoming serial ports
> Network Service: Wi-Fi, AirPort, en1
> Serial ATA Device: TOSHIBA MK5065GSXF, 500,11 GB
> Serial ATA Device: MATSHITADVD-R   UJ-868
> USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 2
> USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26500000 / 2
> USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0x04600000 / 3
> USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2
> USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2
> USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06110000 / 3
> 



From moss at snap.net.nz  Wed Jan 11 01:45:36 2017
From: moss at snap.net.nz (moss at snap.net.nz)
Date: Wed, 11 Jan 2017 14:45:36 +1300
Subject: [Tox Support] qTox setup help pls
In-Reply-To: <2d13139248f67c127712c10a46348753@snap.net.nz>
References: <0b9de24dc06f0df4a2d4e4dff9b02d58@snap.net.nz>
 <93063c92fbdbc86d6e3fc6080c6ef21f@mail.tox.chat>
 <2d13139248f67c127712c10a46348753@snap.net.nz>
Message-ID: <29e7f56ad3da2b26ed006b240b054ccc@snap.net.nz>

 

Dear List Support,
I have struggled to enable my qTox to function
correctly (see below) and on the advice of nuropo have gone through the
user manual. I have also uninstalled my system and reinstalled with
v1.6.0-obs which I assume is the latest one for Linuxmint 18.

Is there
anyone who can call me on qTOX to help me through the configurations to
see whether it's possible to get it working properly, please. My ID
is
6C84A17F6F0480E05CE57E27AC2AC74EDFDD917096A367138C389F630B484B7270813704C040


I'm particularly interested to see whether the USP enabled/disabled
will help with the quality issue which was the sound intermittently
dropping out altogether during a call

Thanking you for any
help,
regards, James

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170111/59bf3d88/attachment.htm>

From NoCos30 at hotmail.com  Thu Jan 12 02:43:40 2017
From: NoCos30 at hotmail.com (Nocs ...)
Date: Thu, 12 Jan 2017 02:43:40 +0000
Subject: [Tox Support] Static Build Like Shared Build for windows X86 ?
Message-ID: <HE1PR02MB129063D3144A080A47025B92B2790@HE1PR02MB1290.eurprd02.prod.outlook.com>

Hello again,


Due to personal problems on my pc i have to send you email for the moment whenever i fix the pc problem i will come again at irc channel.

I would like to know if anyone that builds the toktok windows build can make the static build as the shared build which i mean

one only library file without the .dll all in the one library and ofcourse with less includes as the shared library build has ?


Is this possible cause i cant make the build on windows by myself and static dont compile at all though shared as is has no errors and everything works fine.

I just need the shared build for windows x86 to become static as is.


Thank you in advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170112/a81415bb/attachment.htm>

From NoCos30 at hotmail.com  Mon Jan 16 05:03:56 2017
From: NoCos30 at hotmail.com (Nocs ...)
Date: Mon, 16 Jan 2017 05:03:56 +0000
Subject: [Tox Support] Static Build Like Shared Build for windows X86 ?
In-Reply-To: <HE1PR02MB129063D3144A080A47025B92B2790@HE1PR02MB1290.eurprd02.prod.outlook.com>
References: <HE1PR02MB129063D3144A080A47025B92B2790@HE1PR02MB1290.eurprd02.prod.outlook.com>
Message-ID: <VI1PR02MB12961B6BBD55107B37928A39B27D0@VI1PR02MB1296.eurprd02.prod.outlook.com>

I cant compile with any static build.

I downloaded static release of tox_core, libsodium and it doesnt compile it has errors again :/


If i remember well there is someone that knows how to build or he hasnt got problems compiling the static build at visual studio at windows

Can anyone give a zip with an empty main.cpp project for visual studio and with the static build libs etc that works ready to compile it ?


I cant compile it at all in static only in shared with the one lib and the dll which i would like to make it static


Thank you in advance

________________________________
From: Support <support-bounces at lists.tox.chat> on behalf of Nocs ... <NoCos30 at hotmail.com>
Sent: Thursday, January 12, 2017 4:43:40 AM
To: support at lists.tox.chat
Subject: [Tox Support] Static Build Like Shared Build for windows X86 ?


Hello again,


Due to personal problems on my pc i have to send you email for the moment whenever i fix the pc problem i will come again at irc channel.

I would like to know if anyone that builds the toktok windows build can make the static build as the shared build which i mean

one only library file without the .dll all in the one library and ofcourse with less includes as the shared library build has ?


Is this possible cause i cant make the build on windows by myself and static dont compile at all though shared as is has no errors and everything works fine.

I just need the shared build for windows x86 to become static as is.


Thank you in advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170116/a7b46dbf/attachment.htm>

From tiger.railgun at hushmail.com  Mon Jan 16 21:57:36 2017
From: tiger.railgun at hushmail.com (tiger.railgun at hushmail.com)
Date: Mon, 16 Jan 2017 14:57:36 -0700
Subject: [Tox Support] BlackBerry
Message-ID: <8f7a4167b2bd5803ded528a6660bef5b@smtp.hushmail.com>

Hello, is there any plan to make Tox available for BlackBerry?  I know
some people who have BlackBerry's although I have Android.

Of all the apps I know of that have End-to-End Encryption, WhatsApp is
the only one that supports BlackBerry, and even they are dropping
support for older BlackBerry's.
https://www.whatsapp.com/faq/en/bb10/24983053      
https://www.whatsapp.com/faq/en/bb


Thank you.


-- 
Signal <https://whispersystems.org>/WhatsApp
<https://www.whatsapp.com>/Wire <https://Wire.com>/Zom <https://Zom.im>
 

Have questions about Life, the Universe and Everything? Visit
BibleUniversity.com
<http://www.bibleuniversity.com/logon.aspx?sr=0003010367> to finally
find the real answers!


"And this gospel of the kingdom shall be preached in all the world for a
witness unto all nations; and then shall the end come." Matthew 24:14

Have your neighbors seen this website yet? Gospel Learning Center Bible
School <http://www.GospelLearningCenter.com/School.aspx?sr=6725>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/support/attachments/20170116/6458b517/attachment.htm>

From daniel at rechi.at  Thu Jan 26 06:18:39 2017
From: daniel at rechi.at (Daniel Rechberger)
Date: Thu, 26 Jan 2017 07:18:39 +0100
Subject: [Tox Support] Issues with uTox 0.11.1 and 0.12.1
Message-ID: <7d326b3e-6d97-845d-e6b9-f8ba1d832f53@rechi.at>

Hey Gents,

I am a using uTox for confidential communication and I am having a bit 
of an issue.

Since updating to 0.11.1 (and now 0.12.1) I can't send any files across 
anymore. I can select the file I want to send, but it will not put it 
into the history and offer it to my communication partner.

Also, since the feature "Export Chatlog" has been introduced, I can't 
use it. It offers me to export the log - selecting a file destination. 
But the file gets locked, and stays empty. I used different directories 
to put it in (Desktop, E:, User-folder, ...) - all the same.

Kindest Regards,

Dan


From tox at cebe.cc  Thu Jan 26 08:12:39 2017
From: tox at cebe.cc (Carsten Brandt)
Date: Thu, 26 Jan 2017 09:12:39 +0100
Subject: [Tox Support] Issues with uTox 0.11.1 and 0.12.1
In-Reply-To: <7d326b3e-6d97-845d-e6b9-f8ba1d832f53@rechi.at>
References: <7d326b3e-6d97-845d-e6b9-f8ba1d832f53@rechi.at>
Message-ID: <4a11c854-8700-c1f9-23e5-2c7ff0938d8f@cebe.cc>

Hi Dan,

thanks for reporting these issues. These are mostly known and we are
working on them.

Would be great if you could check the Issue Tracker if your issue is
listed and report a new one if not: https://github.com/uTox/uTox/issues

Thanks!

best regards,
Carsten

On 26.01.2017 07:18, Daniel Rechberger wrote:
> Hey Gents,
> 
> I am a using uTox for confidential communication and I am having a bit
> of an issue.
> 
> Since updating to 0.11.1 (and now 0.12.1) I can't send any files across
> anymore. I can select the file I want to send, but it will not put it
> into the history and offer it to my communication partner.
> 
> Also, since the feature "Export Chatlog" has been introduced, I can't
> use it. It offers me to export the log - selecting a file destination.
> But the file gets locked, and stays empty. I used different directories
> to put it in (Desktop, E:, User-folder, ...) - all the same.
> 
> Kindest Regards,
> 
> Dan
> _______________________________________________
> Support mailing list
> Support at lists.tox.chat
> https://lists.tox.chat/listinfo/support

-- 
mail:  mail at cebe.cc
phone: +49 176 / 96 52 999 7
www:   http://cebe.cc/
pgp:   http://cebe.cc/cebe_pub.asc
skype: skype://cebe08
irc:   cebe @ irc.freenode.net



-- 
mail:  mail at cebe.cc
www:   http://cebe.cc/
pgp:   http://cebe.cc/cebe_pub.asc
irc:   cebe @ irc.freenode.net


From zetok at openmailbox.org  Thu Jan 26 13:29:40 2017
From: zetok at openmailbox.org (Zetok Zalbavar)
Date: Thu, 26 Jan 2017 13:29:40 +0000
Subject: [Tox Support] Issues with uTox 0.11.1 and 0.12.1
In-Reply-To: <7d326b3e-6d97-845d-e6b9-f8ba1d832f53@rechi.at>
References: <7d326b3e-6d97-845d-e6b9-f8ba1d832f53@rechi.at>
Message-ID: <d8b0e112-d93b-5ab3-f086-607cbf788ba7@openmailbox.org>

On 26.01.2017 06:18, Daniel Rechberger wrote:
> Hey Gents,
> 
> I am a using uTox for confidential communication and I am having a bit
> of an issue.
> 
> Since updating to 0.11.1 (and now 0.12.1) I can't send any files across
> anymore. I can select the file I want to send, but it will not put it
> into the history and offer it to my communication partner.
> 
> Also, since the feature "Export Chatlog" has been introduced, I can't
> use it. It offers me to export the log - selecting a file destination.
> But the file gets locked, and stays empty. I used different directories
> to put it in (Desktop, E:, User-folder, ...) - all the same.
> 
> Kindest Regards,
> 
> Dan

You could try using qTox.

-- 

Kind regards,
Zetok Zalbavar
----
tox:29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.tox.chat/pipermail/support/attachments/20170126/8ce63251/attachment.sig>

From daniel at rechi.at  Thu Jan 26 17:37:43 2017
From: daniel at rechi.at (Daniel Rechberger)
Date: Thu, 26 Jan 2017 18:37:43 +0100
Subject: [Tox Support] Issues with uTox 0.11.1 and 0.12.1
Message-ID: <09a3cdc2-f0e0-0126-4d62-68ebee4c3e52@rechi.at>

@Carsten Brandt

I'd like to report those two issues. I can't, as it requires a GitHub-Account, which I do not want ... if you could relay those two issues? I looked at the open as well as closed issues, and did not find any match.

Issue #1:
Exporting a chat history does not work. The file does get created, locked on OS level (Win 7 x64, Ultimate), but stays empty. I either need to Unlock the file in order to remove it, or close uTox.

Issue #2:
Before 0.11.1 (I think 0.9 or so) I was able to send and receive files with no problem. Now at 0.12.1 I am no longer able, and need to use different ways. Again, Windows 7 x64 (receiver is Windows 10).

Kindest regards,

Dan