Make sure GNTP works with Growl for Windows

[GoogleCodeExporter]

It seems GNTP may not be working with Growl for Windows. It's worth checking to 
see what the problem is.

Original issue reported on code.google.com by ch...@growl.info on 5 Oct 2011 at 12:59

[GoogleCodeExporter]

Moving to 1.3.2.

Original comment by ch...@growl.info on 5 Oct 2011 at 9:51

• Added labels: Milestone-1.3.2

[GoogleCodeExporter]

Just some additional info from my quick testing:

What works:
 - forwarding from Mac to PC mostly works, but some images do not come through. it looks like url-based images work fine, but local images (Simplest Notifier Evar) do not get forwarded properly. In GfW, I forward url-based images and binary images as-is (since they should work properly on the receiving end) and convert local file paths to binary resources (since the local file path most likely wont work on another machine)

What doesnt work:
 - forwarding from PC to Mac doesnt seem to work at all. With a password set, the Mac does not parse the incoming request properly at all (for registrations, it usually says the application name is 'null' and then says that is invalid), and with no password set, it complains that the keyHash is missing (which technically is correct)
 - notifications from the Firefox plugin also get the 'keyHash missing' error response, even though it is a local app that should not have to supply a password. sending the same data via telnet works, so my guess is that it is being treated as a non-local app?

I will try to play with it some more to gather more details, but that hopefully 
points you in the right direction.

Original comment by briandun...@gmail.com on 6 Oct 2011 at 1:26

[GoogleCodeExporter]

After discussing this with Brian in IRC, the issue with Windows forwarding to 
Mac is that Windows uses encryption with messages it forwards with a password.  
Growl.app 1.3 does not support encryption, and does not support completely 
lacking password either.  
Firefox has been partly fixed, it no longer spits hash string errors, however, 
it now silently fails.  It appears the socket is closing before we can get the 
bulk of the data read properly (this also appears to be the cause of the hash 
error, it didn't know what host was connected anymore).  We need to investigate 
how to handle this better.  

Moving to 1.4, if I or someone else finds time to work on these sooner, great.

Original comment by dan...@growl.info on 7 Oct 2011 at 2:05

• Changed state: Accepted
• Added labels: Milestone-1.4
• Removed labels: Milestone-1.3.2

[GoogleCodeExporter]

An update from Brian, Firefox addon fully fixed with an update to the addon, 
even without the changes already made for 1.3.1.
Growl/GNTP Firefox addon version 1.2.5, direct link till the addon's front page 
updates: 
https://addons.mozilla.org/en-US/firefox/addon/growlgntp/versions/?page=1#versio
n-1.2.5
Leaving open as there is still the outstanding issue of encryption

Original comment by dan...@growl.info on 7 Oct 2011 at 6:26

[GoogleCodeExporter]

we should split this up into separate issues and then close this one out. so 
far i know of:

 - Growl doesnt support encryption in anyway (thus forwarding from GfW doesnt work)
 - Growl doesnt always forward registration/notification icons (may only be for apps/notifications that dont provide any and you guys are using the app's default icon - not sure yet)

Original comment by briandun...@gmail.com on 7 Oct 2011 at 6:40

[GoogleCodeExporter]

btw. this is what appears in the console log, when a message is being sent from 
windows to local mac with growl 1.3.1 using a password:

03.11.11 14:49:19,710 Growl: Error occurred: Error domain GrowlNetwork, code 2 
(Der Vorgang konnte nicht abgeschlossen werden. Application-Name is a required 
header for registration).
03.11.11 14:49:19,711 Growl: Failed reading with error: Error 
Domain=GrowlNetwork Code=2 "Der Vorgang konnte nicht abgeschlossen werden. 
Application-Name is a required header for registration" UserInfo=0x7f8cfc8476f0 
{NSLocalizedFailureReason=Application-Name is a required header for 
registration}
03.11.11 14:49:19,919 Growl: Failed application registration for application 
with no name; wrote failed registration dictionary 0x7f8cfc88eb30 to 
/Users/docacola/Library/Logs/Failed Growl 
registrations/unknown-application.growlRegDict

Original comment by normanhe...@fotona.de on 3 Nov 2011 at 1:52

[GoogleCodeExporter]

I would like to use GfW in my Parallels VM send notifies to my mac Growl.  i 
have no password set, is this part fixed at least?

Original comment by karaoke....@gmail.com on 28 Nov 2011 at 12:02

[GoogleCodeExporter]

Update to the latest GfW, it should work.

Splitting up like Brian suggested.

Original comment by ch...@growl.info on 28 Nov 2011 at 12:53

• Changed state: WontFix

[GoogleCodeExporter]

I am using 2.0.8.1 for Windows, and 1.3.1 for mac.  It is definitely still NOT 
working.

Original comment by karaoke....@gmail.com on 28 Nov 2011 at 4:23

[GoogleCodeExporter]

just made the update on growl for windows 2.0.8.1 with growl 1.3.1 and it is 
still no success. tested with and without a password set.

the message in the console that appears:
28.11.11 10:40:45,565 Growl: Failed reading with error: Error 
Domain=GrowlNetwork Code=2 "Der Vorgang konnte nicht abgeschlossen werden. 
Application-Name is a required header for registration" UserInfo=0x7ff1722b4be0 
{NSLocalizedFailureReason=Application-Name is a required header for 
registration}
28.11.11 10:40:45,571 Growl: Failed application registration for application 
with no name; wrote failed registration dictionary 0x7ff17237b670 to 
/Users/docacola/Library/Logs/Failed Growl 
registrations/unknown-application.growlRegDict

Original comment by normanhe...@fotona.de on 28 Nov 2011 at 9:43

[GoogleCodeExporter]

oh, and with no password set, this appears in the log:

28.11.11 10:47:45,599 Growl: There was a missing 
<hashalgorithm>:<keyHash>.<keySalt> with encryption or remote, set error and 
return appropriately
28.11.11 10:47:45,600 Growl: Error occurred: Error domain GrowlNetwork, code 
400 (Der Vorgang konnte nicht abgeschlossen werden. Fehlender, missgebildeter 
oder ungültiger Hash-Schlüssel).
28.11.11 10:47:45,600 Growl: Failed reading with error: Error 
Domain=GrowlNetwork Code=400 "Der Vorgang konnte nicht abgeschlossen werden. 
Fehlender, missgebildeter oder ungültiger Hash-Schlüssel" 
UserInfo=0x7ff172354eb0 {NSLocalizedFailureReason=Fehlender, missgebildeter 
oder ungültiger Hash-Schlüssel}
28.11.11 10:47:45,605 Growl: Failed application registration for application 
with no name; wrote failed registration dictionary 0x7ff17226c350 to 
/Users/docacola/Library/Logs/Failed Growl 
registrations/unknown-application.growlRegDict
28.11.11 10:47:47,217 Growl: There was a missing 
<hashalgorithm>:<keyHash>.<keySalt> with encryption or remote, set error and 
return appropriately
28.11.11 10:47:47,217 Growl: Error occurred: Error domain GrowlNetwork, code 
400 (Der Vorgang konnte nicht abgeschlossen werden. Fehlender, missgebildeter 
oder ungültiger Hash-Schlüssel).
28.11.11 10:47:47,217 Growl: Failed reading with error: Error 
Domain=GrowlNetwork Code=400 "Der Vorgang konnte nicht abgeschlossen werden. 
Fehlender, missgebildeter oder ungültiger Hash-Schlüssel" 
UserInfo=0x7ff172142a40 {NSLocalizedFailureReason=Fehlender, missgebildeter 
oder ungültiger Hash-Schlüssel}

translation:
Der Vorgang konnte nicht abgeschlossen werden. Fehlender, missgebildeter oder 
ungültiger Hash-Schlüssel -> Operation could not be completed. Missing, 
malformed or invalid hash key.

Original comment by normanhe...@fotona.de on 28 Nov 2011 at 9:50

[GoogleCodeExporter]

The developer for GfW says that the latest update works with Growl by checking 
for Bonjour. If it's not working, please start a thread on our discuss list. If 
we determine it's an issue with Growl, and not already filed, then we'll file 
the ticket.

This ticket was a task ticket. Based on the feedback from Brian I've closed 
this task ticket and split out into different tickets. 

Original comment by ch...@growl.info on 28 Nov 2011 at 7:07

[GoogleCodeExporter]

i don't really get what bonjour has to do with that. the previous version of 
gfw auto-detected my mac through bonjour already, too. bonjour itself has not 
much to do with the data sent but only with discovery of networking devices, 
right?

anyway, i can't tell if the error is on side of gfw or growl and i understand 
that the passworded messages bug is a different one. all i know as a user that 
my (non-passworded) gfw messages never are displayed in growl (but produce an 
error in console as stated previously). i suspect that either gfw sends the 
data malformed or growl interprets the data received from gfw too strict 
(compared to gfw->gfw messages). i can't evaluate that as i am not a developer 
of growl :) that is up to you.
an older thread for this bug here exists already (and triggered the creation of 
this ticket in the first place), so i do not understand why i should repeat it 
in a new thread.

Original comment by normanhe...@fotona.de on 28 Nov 2011 at 7:35