search

doanit / android-notifier

Automatically exported from code.google.com/p/android-notifier
0 stars 0 forks source link

Notifications not decrypted #233

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
IMPORTANT: PLEASE search the existing issues (including closed ones) for
something similar before filing a new one.

What steps will reproduce the problem?
1.Enable encryption on the phone and set passphrase
2.Enable decryption on desktop and set passphrase
3.Send ping

What is the expected output? What do you see instead?
Receive ping. No ping

What version of the product are you using? On what operating system?
0.2.8 - Phone
0.5.1 - Desktop

Please provide the log output if possible (from the alogcat app on android,
Show Log menu on the multiplatform client, or Console on native mac app):

Please provide any additional information below.
Ping messages received when encryption not enabled.
Using Samsung Galaxy S on 2.1 and Windows 7 PC

Original issue reported on code.google.com by tormod.m...@gmail.com on 13 Oct 2010 at 7:03

GoogleCodeExporter commented 9 years ago 
Log files?

Original comment by lehph...@gmail.com on 13 Oct 2010 at 7:08

GoogleCodeExporter commented 9 years ago 
Phone log attached

Original comment by tormod.m...@gmail.com on 13 Oct 2010 at 7:24

Attachments:

GoogleCodeExporter commented 9 years ago 
Desktop log attached

Original comment by tormod.m...@gmail.com on 13 Oct 2010 at 7:25

Attachments:

GoogleCodeExporter commented 9 years ago 
You are using version 0.4 of the desktop app, encryption is supported only in 
version 0.5 or better. Please upgrade and don't forget to stop the desktop app 
before uninstalling or installing a new version.

Original comment by lehph...@gmail.com on 13 Oct 2010 at 7:31

GoogleCodeExporter commented 9 years ago 
seems version 0.5.1 still has this problem

Original comment by timmer...@gmail.com on 25 Oct 2010 at 9:28

GoogleCodeExporter commented 9 years ago 
@timmer.rj Make sure the About dialog of the desktop app says "Android Notifier 
Desktop 0.5.1", if it is 0.5.1 then please attach your log file in this issue.

Original comment by lehph...@gmail.com on 25 Oct 2010 at 12:15

GoogleCodeExporter commented 9 years ago 
I also see this problem using Windows 7 and Samsung Captivate. I'm using 
android-notifier-desktop version 0.5.1 on the computer, and 0.2.8 on the 
Android phone.

I've verified that notifications work without encryption, but when setting 
encryption the computer doesn't respond to notifications. 

In the log file on the computer, a line like the following every time I try to 
send a notification with encryption on:
2010-10-26 04:37:52,174 DEBUG [EncryptedNotificationParser] - Got notification 
not encrypted but set to decrypt, ignoring

Original comment by Josef.Sc...@gmail.com on 26 Oct 2010 at 8:59

GoogleCodeExporter commented 9 years ago 
That message means the desktop app could not decrypt the notification and is 
guessing that it's not encrypted. Could you try a different passphrase?

Original comment by lehph...@gmail.com on 26 Oct 2010 at 12:38

GoogleCodeExporter commented 9 years ago 
I did try several different passphrases with different lengths, all letters, 
mix of letters and numbers, etc.

I just got it to work. I had the android app set to use TCP only, but after 
enabling UDP and TCP protocols, notifications with passphrases work. Any idea 
why this might happen?

Original comment by Josef.Sc...@gmail.com on 26 Oct 2010 at 6:28

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Taking over lehphyro's issues.

Original comment by rdamazio@gmail.com on 11 Jan 2011 at 4:31

GoogleCodeExporter commented 9 years ago 
Confirmation that enabling UDP seems to make encrypted notifications work. If I 
only have TCP enabled, nothing shows in the logs on my desktop.

I can see that it arrives both by TCP and UDP in Wireshark with identical data.

Original comment by mkell...@gmail.com on 2 Mar 2011 at 2:11

GoogleCodeExporter commented 9 years ago 
The UDP work around is an issue, since I'm port forwarding to a public IP 
address via ssh tunnelling.  Anyone got a notion on this?

I'm using all latest versions.

Original comment by kaithar....@gmail.com on 25 Jul 2013 at 2:44