wireshark - wireshark.org protocol dissector with Osmocom additions (obsolete)

Age	Commit message (Collapse)	Author	Files	Lines
2018-10-22	No need for the debugging output.	Guy Harris	1	-1/+1
	The chmods seem to be working. Change-Id: I0f85a1428de511497597a3fd304c700ea1a1f846 Reviewed-on: https://code.wireshark.org/review/30331 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2018-10-22	Make the chmod verbose.	Guy Harris	1	-1/+1
	For some reason it's not taking away write permission; make it verbose to try to debug that. Change-Id: I180309953d36798d2da3a74959cdd934adc5a4a3 Reviewed-on: https://code.wireshark.org/review/30325 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2018-10-21	More permission fixes.	Guy Harris	1	-1/+3
	Take away group write permission for stuff under /Library/Application Support/Wireshark. For some reason, it's getting set; it's not necessary. Change-Id: I4280a635e0c171cf5ad17cb91fe20d746c2daf79 Reviewed-on: https://code.wireshark.org/review/30317 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2018-10-21	Fix ownership and permissions on /Library/Application Support/Wireshark.	Guy Harris	1	-0/+12
	Bug: 14335 Change-Id: I657b024554e1eff01544b7726a7eec74c8da8be1 Reviewed-on: https://code.wireshark.org/review/30307 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2018-10-21	Don't give launchd daemon plists execute permission.	Guy Harris	1	-5/+5
	They don't need it; read permission suffices. While we're at it, rename a variable to indicate that it's the path to the plist for ChmodBPF, not the path to the executable for ChmodBPF. Change-Id: Ib7537e26ae3f4477c4110759049a8cd7d2f09cf6 Reviewed-on: https://code.wireshark.org/review/30303 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2014-06-07	Only nuke the startup item once we've installed the launch daemon.	Guy Harris	1	-2/+2
	That way, if we crash in the middle, there's still something installed that will try to set the permissions on the BPF devices. Change-Id: Ie0c32f9eaca08bdbb359d07e47f20c664bc66411 Reviewed-on: https://code.wireshark.org/review/2023 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2014-06-07	When installing the launch daemon, get rid of the old startup item.	Guy Harris	1	-0/+2
	Only one is necessary; get rid of the startup item. Change-Id: I0bd2dabb3fc286ccd0e6634bc112e20602624c86 Reviewed-on: https://code.wireshark.org/review/2016 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2014-06-06	Switch to a launch daemon for ChmodBPF.	Guy Harris	1	-4/+6
	"Ah finally blew that varmint to Kingdom Come!" Change-Id: I4ef5f8692924772189af4158eddbc125c1c7d521 Reviewed-on: https://code.wireshark.org/review/2004 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2012-03-20	Now, isn't that swell! Leopard's dseditgroup doesn't return a failure	Guy Harris	1	-1/+1
	exit status if the group in question doesn't exist, so we can't use dseditgroup on Leopard to check whether the access_bpf group exists. Instead, as per Martin Williams' suggestion in bug 6526, use "dscl . -read /groups/{group}" instead; the suggestion came from the addgroup.sh script in https://developer.apple.com/library/mac/documentation/OpenSource/Conceptual/ShellScripting/ShellScripting.pdf svn path=/trunk/; revision=41680
2011-05-15	Fix the ChmodBPF startup item permissions. Handling this within	Gerald Combs	1	-1/+4
	PackageMaker would be a more correct fix. Replacing PackageMaker with something that fits our development and deployment model would be an even more correct fix. svn path=/trunk/; revision=37167
2011-05-12	Switch to an installer package for OS X instead of a draggable app	Gerald Combs	1	-0/+11
	bundle. There are still a few rough edges but it's an improvement over what we currently have. Fixes bug 5756. svn path=/trunk/; revision=37093