Growl 1.3 in the Mac App Store

62 views
Skip to first unread message

Brian Dunnington

unread,
Oct 3, 2011, 10:04:05 PM10/3/11
to growl for windows
Just a heads-up for any body with a Mac: Growl (the original) just
released v1.3 via the Mac App Store, so be sure to check it out.

Also, for anybody who is doing any forwarding to/from a Mac, be aware
that the old UDP protocol has been completely removed from Growl/Mac.
If you are forwarding from a PC to a Mac using UDP on port 9887, it
isnt going to work anymore. You can edit your forwarding settings to
now use GNTP over port 23053 instead and you should be all set again
(and get some nice new features as well like icon forwarding, etc).

If anybody tries it out, let me know your experience.

kLy

unread,
Oct 4, 2011, 4:13:41 AM10/4/11
to growl for windows
Not working for me :(

Messages seem to get sent correctly but nothing received?

Turned on fowarding to the Windows machine. On the Windows machine I
enabled "Allow network notifications".

On the Mac, I try: growlnotify test -m test

This shows a notification on the Mac as well as this in the Log:

04/10/2011 10:05:17.725 Growl: Dispatching notification from
growlnotify: Command-Line Growl Notification
04/10/2011 10:05:17.739 mDNSResponder: -> DNSServiceResolve
Growl\032on\032XXXX._gntp._tcp.local.
04/10/2011 10:05:17.856 Growl: Notification successful




On the Windows machine with debug enabled, I receive this in the log:


Timestamp: 04/10/2011 10:05:03
Notification Origin: 195.110.29.102 [LAN - same subnet]


-----------------------------------------------------

GNTP/1.0 NOTIFY NONE


-----------------------------------------------------

GNTP/1.0 -ERROR NONE
Error-Code: 400
Error-Description: Missing key hash
Origin-Machine-Name: XXXX
Origin-Software-Name: Growl/Win
Origin-Software-Version: 2.0.7.2
Origin-Platform-Name: Microsoft Windows NT 6.1.7601 Service Pack 1
Origin-Platform-Version: 6.1.7601.65536
X-Message-Daemon: Growl/Win
X-Timestamp: 04/10/2011 10:05:03


Any help? Thx!

Brian Dunnington

unread,
Oct 4, 2011, 11:18:01 AM10/4/11
to growl-fo...@googlegroups.com
GNTP (the protocol that Growl/Mac now uses and Growl for Windows has
always used) requires that any notifications that come in from the
network (such as the ones you are forwarding) to supply a password. So
you have to set up a password in the forwarding side (Mac) and set
that same password in Growl for Windows. (the snippet of the debug log
that says 'GNTP/1.0 NOTIFY NONE' shows that no password is being sent,
and the error response from GfW (Missing key hash) indicates that it
is required).

Try that and let me know how it goes.

> --
> You received this message because you are subscribed to the Google Groups "growl for windows" group.
> To post to this group, send email to growl-fo...@googlegroups.com.
> To unsubscribe from this group, send email to growl-for-wind...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
>
>

kLy

unread,
Oct 4, 2011, 5:33:29 PM10/4/11
to growl for windows
I've tried running with and without a password. The above log is
actually from trying with a password set up as described here (http://
www.growlforwindows.com/gfw/help/forwarding.aspx) and using that same
password in the password column on the Mac for the bonjour entry that
pops up for the windows machine.

Also tried to add my Mac to the subscription on the Windows with that
same password to no effect (and removed it again afterwards). Not
really sure what that does, the notification setup guide doesn't even
mention it.

Brian Dunnington

unread,
Oct 4, 2011, 9:54:46 PM10/4/11
to growl-fo...@googlegroups.com
something is not right on the sending side then. from the info in your
log, the beginning of the packet received by GfW was: GNTP/1.0 NOTIFY
NONE

if the 'NONE' is where the password hash should go. if that is not
present (as in this case), then GfW will reject any notification from
the network. (If it were correctly passing the password hash, it
should look something like: GNTP/1.0 NOTIFY AES:blahblahblah.blahblah
SHA256:blahblahbah.blahblah)

You can try asking on the Growl/Mac discussion group here:
http://groups.google.com/group/growldiscuss/ to see if they have any
ideas.

Brian Dunnington

unread,
Oct 4, 2011, 10:22:26 PM10/4/11
to growl-fo...@googlegroups.com
> Also tried to add my Mac to the subscription on the Windows with that
> same password to no effect (and removed it again afterwards). Not
> really sure what that does, the notification setup guide doesn't even
> mention it.

Subscriptions are a separate thing from forwarding and you dont need
to (and shouldnt) configure any subscriptions to get forwarding to
work (which is also why the documentation on forwarding doesnt mention
it).

I have a Mac here, but it is still running Snow Leopard, so I will
have to upgrade it to Lion before I can install Growl 1.3. Once I do
that, I can try to reproduce your issue, but from seeing what the log
shows, it definitely sounds like the password is not being handled
correct on the sending (Mac) side.

kLy

unread,
Oct 6, 2011, 6:40:38 AM10/6/11
to growl for windows
Tried it again, setting the password on both, then restarting growl on
both Mac and Windows. Still the same thing :(

Also tried explicitly specifying the password with -P in growlnotify
but the Windows log still says NOTIFY NONE.

Another note: I'm not only testing with growlnotify. I get other
notifications all the time and none of them are showing up on the
Windows machine.

Brian Dunnington

unread,
Oct 6, 2011, 9:21:01 AM10/6/11
to growl-fo...@googlegroups.com
I played with it a bit and here is what I found:

What works:
- forwarding from Mac to PC *if* you have the same password set up
correctly on both ends. On the PC, you have to have the password set
up on the 'Security' tab, and on the Mac, you have to set the password
for each machine that you are forwarding to (click to the right of the
name (Growl on MACHINE) in the password column to enter the password -
it is NOT the same as the master password for incoming notifications).

What doesnt work:
- some images dont come through when going from Mac to PC. web-based
images (urls) seem to work fine, but local images are not forwarded
correctly
- forwarding from PC to Mac doesnt seem to work at all. With a
password set, the Mac cannot properly parse the incoming message, and
with no password set, it complains that the keyHash is missing.

Both of those appear to be bugs in the Mac implementation and the Mac
guys know about them now, so hopefully they can get them fixed. That
said, your case (forwarding from Mac to PC) does work for me when
configured properly, so hopefully we can get yours to work for you as
well.

Reply all
Reply to author
Forward
0 new messages