===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
shairport-sync-3.3.5/CONTRIBUTING.md-12-----
shairport-sync-3.3.5/CONTRIBUTING.md:13:Issue reports are welcome, but before you report an issue, please have a look though the existing [issues](https://github.com/mikebrady/shairport-sync/issues), both open and closed, and check for hints in the [TROUBLESHOOTING](TROUBLESHOOTING.md) page. It would be great to give some details of the device and version of Linux or FreeBSD in use along with the version of Shairport Sync you are using (use `$ shairport-sync -V` to get this). Then, if possible, some diagnostic information from the log or logfile would be useful.
shairport-sync-3.3.5/CONTRIBUTING.md-14-
##############################################
shairport-sync-3.3.5/INSTALL.md-24-### Remove Old Copies
shairport-sync-3.3.5/INSTALL.md:25:Before you begin building Shairport Sync, it's best to search for and remove any existing copies of the application, called `shairport-sync`. Use the command `$ which shairport-sync` to find them. For example, if `shairport-sync` has been installed previously, this might happen:
shairport-sync-3.3.5/INSTALL.md-26-```
##############################################
shairport-sync-3.3.5/README.md-93-
shairport-sync-3.3.5/README.md:94:You should check to see if `shairport-sync` is already installed – you can use the command `$ which shairport-sync` to find where it is located, if installed. If it is installed you should delete it – you may need superuser privileges. After deleting, check again in case further copies are installed elsewhere.
shairport-sync-3.3.5/README.md-95-
##############################################
shairport-sync-3.3.5/README.md-101-
shairport-sync-3.3.5/README.md:102:Shairport Sync has a number of different "backends" that connect it to the system's audio handling infrastructure. Most recent Linux distributions that have a GUI – including Ubuntu, Debian and others – use PulseAudio to handle sound. In such cases, it is inadvisable to attempt to disable or remove PulseAudio. Thus, if your system uses PulseAudio, you should build Shairport Sync with the PulseAudio backend. You can check to see if PulseAudio is running by opening a Terminal window and entering the command `$ pactl info`. Here is an example of what you'll get if PulseAudio is installed, though the exact details may vary:
shairport-sync-3.3.5/README.md-103-```
##############################################
shairport-sync-3.3.5/README.md-254-
shairport-sync-3.3.5/README.md:255:`$ ./configure --sysconfdir=/etc --with-alsa --with-pa --with-avahi --with-ssl=openssl --with-metadata --with-soxr --with-systemd`
shairport-sync-3.3.5/README.md-256-
##############################################
shairport-sync-3.3.5/README.md-314-
shairport-sync-3.3.5/README.md:315:Shairport Sync reads settings from a configuration file at `/etc/shairport-sync.conf` (note that in FreeBSD it will be at `/usr/local/etc/shairport-sync.conf`). When you run `$sudo make install`, a sample configuration file is installed or updated at `/etc/shairport-sync.conf.sample` (`/usr/local/etc/shairport-sync.conf.sample` in FreeBSD). This contains all the setting groups and all the settings available, but they all are commented out (comments begin with `//`) so that default values are used. The file contains explanations of the settings, useful hints and suggestions. In addition, if the file doesn't already exist, a default configuration is installed, which should work in almost any system with a sound card.
shairport-sync-3.3.5/README.md-316-
##############################################
shairport-sync-3.3.5/RELEASENOTES.md-88-* A new [MQTT](https://en.wikipedia.org/wiki/MQTT) client interface, thanks to the work of [Till Zimmermann](https://github.com/tillz).
shairport-sync-3.3.5/RELEASENOTES.md:89:* Changes in logging -- now you should add `-u` to direct log entries to STDERR (typically the console) rather than the system log. For example, to get logs of verbosity 1 to appear on the console: `$ shairport-sync -v -u`.
shairport-sync-3.3.5/RELEASENOTES.md-90-* The help menu now lists all `alsa` output devices found.
##############################################
shairport-sync-3.3.5/RELEASENOTES.md-744-**Enhancements**
shairport-sync-3.3.5/RELEASENOTES.md:745:* Broaden the use of the value `$PREFIX` instead of the path `/usr/local/bin` during configuration. Thanks to [dantheperson](https://github.com/dantheperson).
shairport-sync-3.3.5/RELEASENOTES.md-746-
##############################################
shairport-sync-3.3.5/RELEASENOTES.md-751-http://www.freedesktop.org/software/systemd/man/daemon.html#Installing%20Systemd%20Service%20Files. Thanks to [dantheperson](https://github.com/dantheperson).
shairport-sync-3.3.5/RELEASENOTES.md:752:* Rather than hardwire the path `/usr/local/bin` as the path to the shairport-sync executable, the value of `$PREFIX` is now used during configuration. Thanks to [Nick Steel](https://github.com/kingosticks).
shairport-sync-3.3.5/RELEASENOTES.md-753-* Add some extra diagnostic messages if the hardware buffer in the DAC is smaller than desired.
##############################################
shairport-sync-3.3.5/RELEASENOTES.md-1170- * Compile options have changed -- see the Building and Installing section below.
shairport-sync-3.3.5/RELEASENOTES.md:1171: * The name of the program itself has changed from shairport to shairport-sync. You should remove the old version -- you can use `$which shairport` to locate it.
shairport-sync-3.3.5/RELEASENOTES.md-1172- * The name of the init script file has changed from shairport to shairport-sync. You should remove the old one.
##############################################
shairport-sync-3.3.5/TROUBLESHOOTING.md-110-
shairport-sync-3.3.5/TROUBLESHOOTING.md:111:Having compiled Shairport Sync properly using the README guide, and having completed the `make install` step, and having enabled startup on reboot using `$ sudo systemctl enable shairport-sync`, Shairport Sync will start manually upon entering `$sudo systemctl enable shairport-sync`, but it will not start automatically after a reboot.
shairport-sync-3.3.5/TROUBLESHOOTING.md-112-
##############################################
shairport-sync-3.3.5/UPDATING.md-27-```
shairport-sync-3.3.5/UPDATING.md:28:(If you wish to use the `development` branch, you should enter the command `$ git checkout development` at this point. Everything else is the same.)
shairport-sync-3.3.5/UPDATING.md-29-
##############################################
shairport-sync-3.3.5/alac.c-213- * obvious for what it's doing. never use this.
shairport-sync-3.3.5/alac.c:214: * then there are the asm ones. fill in as necessary
shairport-sync-3.3.5/alac.c-215- * and finally an unrolled and optimised c version
##############################################
shairport-sync-3.3.5/configure.ac-17-fi
shairport-sync-3.3.5/configure.ac:18:with_os=`echo ${with_os} | tr '[[:upper:]]' '[[:lower:]]' `
shairport-sync-3.3.5/configure.ac-19-
##############################################
shairport-sync-3.3.5/rtsp.c-1243- metadata_sockaddr.sin_family = AF_INET;
shairport-sync-3.3.5/rtsp.c:1244: metadata_sockaddr.sin_addr.s_addr = inet_addr(config.metadata_sockaddr);
shairport-sync-3.3.5/rtsp.c-1245- metadata_sockaddr.sin_port = htons(config.metadata_sockport);
##############################################
shairport-sync-3.3.5/tinysvcmdns.c-1200- mreq.imr_interface.s_addr = htonl(INADDR_ANY);
shairport-sync-3.3.5/tinysvcmdns.c:1201: mreq.imr_multiaddr.s_addr = inet_addr(MDNS_ADDR);
shairport-sync-3.3.5/tinysvcmdns.c-1202- if ((r = setsockopt(sd, IPPROTO_IP, IP_ADD_MEMBERSHIP, (char *)&mreq, sizeof(mreq))) < 0) {
##############################################
shairport-sync-3.3.5/tinysvcmdns.c-1228- toaddr.sin_port = htons(MDNS_PORT);
shairport-sync-3.3.5/tinysvcmdns.c:1229: toaddr.sin_addr.s_addr = inet_addr(MDNS_ADDR);
shairport-sync-3.3.5/tinysvcmdns.c-1230- }