BeeBeep no longer runs on a Mac!
You can message and share files inside your intranet without a server.
Brought to you by:
mastroddi
Menu
▾
▴
1 Attachments
#352 BeeBeep no longer runs on a Mac!
Yesterday I had a few minutes to investigating a long standing problem we were having with BeeBeep 4.0.0. Everything worked between our Windows 7 machine, our Linux machine and our Mac OS 10 machine except for one thing. Niether the Windows machine or the Linux machine could send a file to the Mac. Even if Norton and the firewall were turned off on the Mac. The Mac could send a file to the other machines with no problem.
When I went to grab the log files on the Mac we discovered that BeeBeep could no longer communicate to either machines. They could not see the Mac and the Mac could not see anyone else. We rebooted the Mac and still the same. We uninstalled BeeBeep and downloaded a new copy and installed it but it will not even run. See error dialog box. We unistalled it again and I went in and deleted anything I could find on the Mac that had beebeep in the file name. We rebooted, downloaded another copy of beebeep 4.0.0 and installed it and we get the same error message.
So now we are stuck. What can we do to get it to run on the Mac again?
Discussion
Anonymous
Hello!
1) Send files to Mac: the problem occurs when mac cannot download files from other computers. Firewall can block it, but if you have not firewall active, you can see if mac can really reach port of other computer: usually the 6476 (you can see in network options). Make a telnet with IP of other computer and port 6476 to see if connection works...
2) I have download now from Sourceforge the package for mac and it seems to work.
https://sourceforge.net/projects/beebeep/files/MacOSX/
Let me know...
Thank you!
Running an older version of Mac OS 10.10.5 V 14F2511. Do you think that matterrs?
I want to try to install this again. But first I want to delete all remnants of the beebeep program. Can you tell me the best way to that on a Mac?
You took to long :)
I deleted every reference to beebeep and turned off the firewall and Norton and reinstalled it and it now runs. I have access to the UI. However it does not conncet to our 2 other machines. I tried the telnet deal from both ports 6475 and 6476 and telnet connects.
So what is the next step?
Hello! I’m out fot work... I will back on monday :-(
I will answer as soon as possible....
Try to add user manually (settings - user - add users) and add the ip address of your friends or click on auto add from lan)
It will take about a minute to scan all network....
-- Marco from mobile
Ok I finally got this to work! What is even better is everything is working. No weird one way file transfer to the Mac. Yeah!
Here is all the things I tried in the order I tried them:
I looked at all the logs I could find. No indication that Beebeep was not working or blocked in any way.
Turned off the firewall and Norton but it still would not communicate.
I played with all the settings for beebeep on the Mac and set them all to match the settings on my Linux machine. Still no go.
I did the manual add user thing from the Mac as well as from my Linux machine. No luck there.
Turned back on Norton and the firewall.
Then I went to System Settings on the Mac. Selected Security & Privacy. Under the General tab I then changed the Allow apps downloaded from: setting from "App Store and identified developers" to “Anywhere”. I closed out the Security & Privacy deal but beebeep still did not work.
I quit and restarted beebeep and a dialog box asked me if I wanted to allow beebeep to have access to the network. I did not find out what program was doing the asking however. Probably either Norton or the Firewall.
I clicked allow and then everything worked! Even file transfer.
I put the setting back in Security & Privacy and everythig still worked.
I then googled that "Anywhere" setting and found out about Mac OS's Gatekeeper program that can block programs if they are not from the App Store or approved developers.
So just in case on the Mac I did: sudo spctl --add /Applications/BeeBEEP.app
This morning after a fresh power up BeeBeep did not automatically come up.
Had to remove the old Beebeep deal to start up at boot and set it to the new install. That fixed that.
Everything is still working!
By the way when you do a sudo spctl -v -a /Applications/BeeBEEP.app/ to verify Gatekeeper is setup right for BeeBeep I get the following response:
/Applications/BeeBEEP.app/: invalid Info.plist (plist or signature have been modified)
Don't know what that means however.
Let me know your thoughts.
WOW! You are awesome!!!! Thank you very very much!!!!! ^_^
Maybe If I sign the software with a digital signature the gatekeeper does not give problem... but signing software has a cost and it is very unuseful for an open source and free project....
Last edit: Marco Mastroddi 2017-10-23
Thank you for the compliment and you are welcome.
I agree that the digital signature cost is not in the cards right now. I think however when you get a chance you should look into the error message that spctl gave when I went to verify that BeeBeep was set up correctly in Gatekeeper. Maybe there is some simple setting that you can add to your Info.plist file that won't give that particular error. I know nothing about Mac OS but it is enough like Linux I can do some stuff.
@mastroddi, may I suggest that you codesign the Mac app using adhoc signing? It doesn't require a (paid) codesigning certificate, but still allows the app to be verified against modifications, and therefore enables us to define exceptions in gatekeeper.
I used it so I don't need to allow incoming connections after every restart of BeeBeep.
Amendment:
This is how I did it (on my Mac):
codesign --force --deep -s - /Applications/BeeBEEP.appHere a little more about adhoc codesigning:
https://apple.stackexchange.com/questions/343912/should-i-sign-open-source-code-myself
Or maybe take a look at this regarding signing woth a self-signed certificate (I did not test it):
https://stackoverflow.com/questions/1482476/code-signing-certificate
Last edit: Metin Savignano 2021-12-01
Thank you very much!