NEnewman314·Aug 8, 2022
FWIW, a number of other AirPlay 2 repos that I have been tracking:
* https://github.com/openairplay/goplay2
* https://github.com/openairplay/airplay2-receiver
In Open AirPlay 2 Receiveropenairplay
airplay2-receiver
Python2022–2022
openairplay / airplay2-receiver
airplay2-receiver
AirPlay 2 Receiver - Python implementation
3Distinct people
4Mentions
0Explicit recommenders
2.4KGitHub stars
What to know before exploring
What it is
AirPlay 2 Receiver - Python implementation
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by hour4 dated mentions
Observed mentions: 2022-08-08 09:55:51 UTC to 2022-08-08 20:58:40 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 8, 09:00 | 2022-08-08 09:00:00 UTC | 2022-08-08 10:00:00 UTC | 1 | 1 | 0 |
| Aug 8, 10:00 | 2022-08-08 10:00:00 UTC | 2022-08-08 11:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 11:00 | 2022-08-08 11:00:00 UTC | 2022-08-08 12:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 12:00 | 2022-08-08 12:00:00 UTC | 2022-08-08 13:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 13:00 | 2022-08-08 13:00:00 UTC | 2022-08-08 14:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 14:00 | 2022-08-08 14:00:00 UTC | 2022-08-08 15:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 15:00 | 2022-08-08 15:00:00 UTC | 2022-08-08 16:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 16:00 | 2022-08-08 16:00:00 UTC | 2022-08-08 17:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 17:00 | 2022-08-08 17:00:00 UTC | 2022-08-08 18:00:00 UTC | 1 | 0 | 1 |
| Aug 8, 18:00 | 2022-08-08 18:00:00 UTC | 2022-08-08 19:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 19:00 | 2022-08-08 19:00:00 UTC | 2022-08-08 20:00:00 UTC | 0 | 0 | 0 |
| Aug 8, 20:00 | 2022-08-08 20:00:00 UTC | 2022-08-08 21:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
4 sourcesThat file is intense… seems like half of it is a declaration of a list with a BUNCH of hex addresses. I don’t know anything about crypto so no idea if that’s fairly typical or not.
This file is also interesting:
https://github.com/openairplay/airplay2-receiver/blob/master...
In particular:
AIRPORT_PRIVATE_KEY = (
"-----BEGIN RSA PRIVATE KEY-----\n"
"MIIEpQIBAAKCAQEA5..."
Is that intentional? Surely it is, being a public repo, etc.
In Open AirPlay 2 ReceiverIt's worth stating that the actual crypto code itself is "moderately insane" – https://github.com/openairplay/airplay2-receiver/blob/master... contains the warning:
"""
GPLv2
Python implementation by systemcrash 2022
Original C implementation of OmgHax by (credit to original author and Foxsen)
If you want this to work, don't touch anything. It's a steaming hot
rats nest of crypto mess which works. It's quite performant.
Resist the urge to refactor. :)
Avoid +=, -=, ^= etc operators in Garble: they don't account for overflow.
"""
before going into lovely detail, containing lines (e.g. in a method appropriately called Garble) such as
buffer1[15] = ((3 * (((buffer1[72] >> (buffer4[buffer1[190] % 21] & 7)) ^ (buffer1[72] << ((7 - (buffer4[buffer1[190] % 21] - 1) & 7)))) - (3 * buffer4[buffer1[126] % 21
Read the rest
]))) ^ buffer1[15]) & 0xff
print(f'buffer1[15]:{hex(buffer1[15])}')
Really, really hats off to whoever worked this out. I have no idea where you'd start.