Kronymous Status Updates

[Deepankar Tyagi]

[Dec 03] Not Working on all Chrome 55 update on all devices

[Dec 19] I am voluntarily retiring Kronymous on Chrome 55 ( and above ) for now. 

It is unclear when and if this can be resolved. Have reached out to Google developers also. Waiting for the response.

For those interested in technical details click here. 

The code is and has always been open sourced , if anyone wants to help out see these repos:

• https://github.com/codebuff/naclports-tor
  
• https://github.com/codebuff/kronymous
  

This thread is continuation of this reddit thread.

If you want to get notified about Kronymous, kindly become member of this group.

[Nathaniel Suchy]

I'm really sad to see your project ended like this :(

[Alex]

Would you mind maybe sharing how to do what you did with Kronymous, except on our own using the Tor bundle?

What I mean is, I'm pretty sure Kronymous was doing something that could be done by making Chrome use Tor while the Tor Browser Bundle is open, right?

I'd like to have some tutorial on how to get chrome traffic to go through the tor connection that the browser bundle opens. I'm sure there's a way to do it with custom settings in the Tor config and using that along with Proxy Switchy in Chrome to get them to talk to each other, right?

[Alex]

Basically I'm just asking how to manually do what you made Kronymous to do for us. Teach us what the trick really is. It'd really help.

[Vikas Bidhuri]

Is there any kind of permission that you need to acquire in order to launch the Tor module. I mean, the status 126 means that the command is either not executable (which isn't in this case as it used to work earlier) or there's a problem with permissions. Chrome 55 might have updated permissions, I suggest giving it a try. I'm no extension or chrome app developer, but I think this problem might just be a permission in manifest.

[Deepankar Tyagi]

On Sunday, December 25, 2016 at 9:34:53 PM UTC+5:30, Alex wrote:

Would you mind maybe sharing how to do what you did with Kronymous, except on our own using the Tor bundle?

What I mean is, I'm pretty sure Kronymous was doing something that could be done by making Chrome use Tor while the Tor Browser Bundle is open, right?

No, kronymous doesn't use Tor browser bundle.  

I'd like to have some tutorial on how to get chrome traffic to go through the tor connection that the browser bundle opens. I'm sure there's a way to do it with custom settings in the Tor config and using that along with Proxy Switchy in Chrome to get them to talk to each other, right?

Start with https://developer.chrome.com/native-client

then read this > https://deepankar.io/current_projects/details/kronymous

After that look through these repos:

• https://github.com/codebuff/naclports-tor
  
• https://github.com/codebuff/kronymous
• https://gitweb.torproject.org/tor.git
  

[Deepankar Tyagi]

On Friday, December 30, 2016 at 10:33:34 PM UTC+5:30, Vikas Bidhuri wrote:

Is there any kind of permission that you need to acquire in order to launch the Tor module. I mean, the status 126 means that the command is either not executable (which isn't in this case as it used to work earlier) or there's a problem with permissions. Chrome 55 might have updated permissions, I suggest giving it a try. I'm no extension or chrome app developer, but I think this problem might just be a permission in manifest.

No this is not the issue, sel_ldr validations are failing which means "most likely" the compiler emitted some unsupported instruction in the  bytecode which is leading to failure when pnacl-translator tries to convert it into machine code.

[Alex]

Just one last question. One to be absolutely clear on one thing.

Do you intend to continue development on Kronymous and have it ready for Chrome 55+ for any time in the foreseeable future, or are you suspending it indefinitely?

Just asking to get the big question out of the way. If you don't think it'll be up and working with a few months it's probably best for folks to start looking at other options.

[Tracy Cooper Jr]

So I ignored the warning and decided to try starting TOR and it looks like it is working. I am using Dev 58 but running Kronymous with SwitchyOmega, check.torproject.org says I am using TOR. Don't know what changed but wanted to let you know.

[Graig Ddu]

Just tried Developer Channel 58.0.3029.31 (Official Build) dev (32-bit) and Kronymous with SwitchyOmega works as before so it seems that whatever broke in 55 has been fixed,

The 57 build run in beta channel still has the original problem,

let's hope it doesn't break again before 58 reaches beta or stable channel

[Mario Marietto]

I have installed Chrome 59.0.3071.9 (official Build) dev (at 64 bit) to check if kronymous 0.2.8 is able to work with it and you can read here what's happened :
 
https://tor.stackexchange.com/questions/14595/kronymous-0-2-8-is-working-with-chrome-59-0-3071-9-official-build-dev-at-64-b

[Deepankar Tyagi]

Hi, apologies for delayed response.

On Sunday, January 8, 2017 at 4:44:33 AM UTC+5:30, Alex wrote:

Just one last question. One to be absolutely clear on one thing.

Do you intend to continue development on Kronymous and have it ready for Chrome 55+ for any time in the foreseeable future, or are you suspending it indefinitely?

At the time it looked like I would have suspend it indefinitely due to lack of time and chaotic nature of pnacl toolchains (in general pnacl platform), however lately I have started to get my work-life balance back to equilibrium so expect an update in near future.

Just asking to get the big question out of the way. If you don't think it'll be up and working with a few months it's probably best for folks to start looking at other options.

As I have mentioned in help section of app and support section on webstore page, that  windows/linux/macos users already have the alternative i.e. tor browser bundle. Main beneficiaries of this app were chromebook users thus I wanted to stick around for those users hoping that other platform users might also benefit. 

[Deepankar Tyagi]

On Tuesday, March 14, 2017 at 5:56:30 AM UTC+5:30, Tracy Cooper Jr wrote:

So I ignored the warning and decided to try starting TOR and it looks like it is working. I am using Dev 58 but running Kronymous with SwitchyOmega, check.torproject.org says I am using TOR. Don't know what changed but wanted to let you know.

Thanks for the valuable info, I was waiting for chrome 58 to become stable and can confirm that is it working .
Next step would to test if all the functionality is working, compile with updated toolchain, update tor binary, depending upon how all this goes, will release an update on webstore.

[Deepankar Tyagi]

On Wednesday, April 19, 2017 at 5:53:23 PM UTC+5:30, Mario Marietto wrote:

I have installed Chrome 59.0.3071.9 (official Build) dev (at 64 bit) to check if kronymous 0.2.8 is able to work with it and you can read here what's happened :
 
https://tor.stackexchange.com/questions/14595/kronymous-0-2-8-is-working-with-chrome-59-0-3071-9-official-build-dev-at-64-b

Saw it, I could elaborate on all the issues on stackexchange but let's leave that for another day.

"N.B. this browsing won't be anonymous and will make non-Tor connections consistently"
This is incorrect. Full answer will be lengthy, skipping for now.
For hint on this, kindly see "notes from developer" section by clicking on "are you browsing anonymously" button in the app.It also contains windows related note and other general guideline.