Vonode node v1.4.2

Vonode node v1.4.2 for 64-bit x86 (amd64) and 64-bit ARM (arm64) Linux (systemd package or Docker Compose).

What's new

Wi-Fi Calling identity: you now choose the User-Agent and the IMEI.

User-Agent. Each SIM has a User-Agent setting (app: card policy; web: card policy page). The default is an honest
Vonode/<version>, for example Vonode/1.4.2, which tells your carrier that the line uses Vonode. You can instead pick a
phone profile from the list or enter your own User-Agent (printable ASCII, up to 128 characters). Up to v1.4.1 the node sent
a fixed phone User-Agent taken from its carrier settings (for example an iPhone or a realme RMX3366 string) whenever you had
not picked a profile; it no longer does. SIMs where you had picked a profile keep it. If Wi-Fi Calling stops registering,
your carrier may accept only certain phones. You can choose a phone profile, which makes the node identify itself to your
carrier as that phone model; check that your carrier's terms allow it. The profile that Vonode's carrier settings used by
default is shown for reference after the SIM has started Wi-Fi Calling once since the node started.

IMEI. Some carriers allow Wi-Fi Calling only on phone models they approve; on those carriers Wi-Fi Calling may not work on
a node. A profile no longer changes the IMEI: up to v1.4.1, picking a profile also replaced the modem's IMEI in Wi-Fi Calling
signalling with one derived from the phone model. Wi-Fi Calling now uses the modem's real IMEI by default. You may instead
enter the IMEI of a phone you own and have permanently retired, after accepting a statement in the app; the node checks the
number's format and that no modem or other line of this node uses it, never generates an IMEI, and stops Wi-Fi Calling on
that SIM if, after registering, the network shows that another device took over this number's registration with that IMEI.
It cannot detect the IMEI being used with a different SIM, so make sure the retired phone stays out of use. The node sends
this IMEI only to that SIM's carrier, never to Vonode. A user-provided IMEI is not offered for SIMs whose home network is in
mainland China or India. A SIM whose User-Agent or IMEI changes registers with IMS once more with the new identity (a new SIP
instance ID when the IMEI changes); a registration the old node could not remove at shutdown expires on its own. The
device_identity.enabled setting in carrier override files is ignored (a warning is logged once).

Verification codes always get through. A text that looks like a one-time code (sign-in, verification or payment code
in 17 languages) is never put in the Filtered folder and is always pushed to the app, even when its sender is on an
always-filter rule, the spam filter would hide it, or Do Not Disturb is on; Telegram and other notification channels forward
it too. The node only decides that a message contains a code; it never stores the code separately. A manual "spam" correction
still works.

Health alerts (subscription or Lifetime). The app can alert you when the node goes offline (it stops renewing with the
Vonode relay for 15, 30, 60 or 120 minutes, 30 by default, chosen in the app) and again when it is back. The node itself
alerts you when Wi-Fi Calling on a line has been down for 10 minutes, or a modem or card reader has been gone or a SIM missing
for 3 minutes: one alert per problem and one when it recovers, only the root cause, and nothing during modem restarts, eSIM
switches or node restarts. Alerts do not count towards the SMS push quota. Node alerts are
encrypted for your phone, so the relay cannot read them, and the notification sent through Apple carries no node name or ID.

Number keep-alive. For each SIM the node records the last activity that usually keeps a prepaid number alive (a text
sent, an answered outgoing call from the app, a successful keep-alive automation step, a USSD request, or a top-up you log in
the app) and shows how many days are left. Calls and texts to free numbers (such as 0800 or 1-800), emergency numbers,
helplines and short service numbers do not count, and neither does a number the node cannot read with certainty. Built-in
rules cover 32 UK, EU and U.S. prepaid carriers; only giffgaff's 180 days is confirmed, the others are estimates from public
sources and count at most 120 days. For 9 carriers the public sources were too weak, and on the O2 UK network only SIMs that
identify as O2 get O2's rule, so for those the app asks you to set your own period; when a rule named differently from your
SIM's carrier is used, the app says which one. With a subscription or Lifetime purchase you get a reminder in the app 30, 14 and 3 days before. The node never acts on its own.
After the upgrade it fills in the last sent text from its message history; call history is not stored, so earlier calls are
not counted.

Wi-Fi Calling diagnostics and carrier coverage.

• The app shows for each line why Wi-Fi Calling is not working: the state, a plain-language reason, the step that failed and
  when the node retries.
• When a carrier keeps rejecting a SIM, the node backs off (15 minutes, 1 hour, 6 hours, then no automatic retries) instead of
  retrying every 2 minutes; turning Wi-Fi Calling off and on, reconnecting, or changing the SIM starts again.
• For carriers without an exact Vonode profile the node tries a few conservative alternatives (the two-digit network name for
  the carrier's server, compatibility encryption proposals, TCP for registration), never after an authentication failure,
  limits failed authentication attempts per SIM, and remembers what worked for that network for 30 days.
• Fixed: the automatic address-family and TCP-to-UDP fallbacks again apply to the 36 networks that carrier settings
  revision 3 had folded into existing carrier profiles.
• Wi-Fi Calling isn't available for SIM cards whose home network is in mainland China or India. On a modem, calls and texts
  over the mobile network keep working as before; the node no longer turns the radio off for Wi-Fi Calling on these SIMs, and
  the app explains why Wi-Fi Calling is off.

Spam protection.

• Incoming calls: always-allow and always-block lists now take any international number or a number in your SIM's national
  format (up to 500 each); calls from withheld numbers can be rejected (off by default); the app can reject a ringing call
  from a number on your iPhone's block list. Blocked calls are recorded as blocked in the call history.
  Over Wi-Fi Calling a blocked caller hears no ringing: the node screens the call before it rings and declines it,
  so the carrier does not treat it as "busy". Calls rejected because of your iPhone's block list are declined the same
  way. A decline is final for the whole line: if your number is also active on another phone (for example a phone
  with VoLTE on), that phone stops ringing too. Rejecting a call yourself in the app is still reported as "busy".
  National-format rules also work on USB card-reader lines.
• SMS: sender rules (up to 500) match national and international forms of the same number for the receiving line's country,
  accept more alphanumeric sender names, and the Filtered folder is recorded when a message arrives. On the free tier you
  can manage sender rules and correct filtering for the pinned line.
• Without a subscription, the chosen number can now also receive its SMS over Wi-Fi Calling (modem lines). On the free
  plan Wi-Fi Calling only receives SMS: the node registers for SMS only where the carrier accepts it and declines
  incoming calls as "temporarily unavailable" (callers reach voicemail, or your other phones keep ringing); sending,
  calls, notifications and other numbers still need a subscription. Card-reader lines stay subscriber-only.
• With an active subscription or Lifetime purchase the node also downloads the U.S. FTC's public Do-Not-Call complaint data
  (in addition to the FCC data) directly from the agency's website, keeping only keyed digests on your host.

Calls and messages.

• In-call keypad (DTMF) from the app, sent as RFC 4733 telephone events; if a call cannot send keypad tones the app is told
  so, and hanging up is never delayed by keypad tones.
• An incoming call the caller cancels while it rings is recorded as missed, not rejected.
• SMS times are stored in UTC, so conversations from different time zones sort correctly (existing messages are migrated;
  unreadable timestamps are skipped instead of stopping startup).

Card-reader lines (experimental, subscription or Lifetime only, off by default). A USB smart-card reader (CCID) can
serve a SIM as a modem-less, Wi-Fi-Calling-only line for calls and SMS (card_reader.enabled). Reader lines report no IMEI
by default, always use the honest Vonode User-Agent, are not offered for SIMs whose home network is in mainland China or
India (a reader line has only Wi-Fi Calling, which these SIMs don't get), and stay marked experimental until long-run testing is complete. The app's Retry on a reader line's Wi-Fi Calling
status reconnects it and lifts the carrier back-off; the status says when the reader is unplugged or has no SIM card. Turning
Wi-Fi Calling off on a reader line through the node API lasts until it is turned on again, the card is replaced or the node
restarts.

eSIM management for multi-profile eUICC cards in a card reader (subscription or Lifetime only; the app screens arrive in app 1.4.3). When the card in a
reader line is a rewritable multi-profile eUICC (for example 5ber, XeSIM, eSTK.me or 9eSIM cards), the app's SIM & eSIM
screens manage it like a modem eSIM: list profiles, enable, disable, rename and delete them, download a profile from an
activation code, and send pending notifications. All eSIM logic runs on the node. After enabling or disabling a profile the
node power-cycles the card, re-reads its identity and applies the region rule; enabling a profile whose card issuer is in
mainland China or India is refused before anything is written. Downloads on a reader line send the SM-DP+ the IMEI you
registered for that line as the device information; without one the download is refused (the node never generates an
IMEI). Writing to a card cannot be undone; cards from different vendors behave differently and only the GSMA-standard
interface is used. card_reader.esim_management: false turns the feature off. The IMEI statement is now version
2026-10-19.1 (it adds the SM-DP+ destination); a user-owned IMEI accepted under an earlier version must be accepted again.

Setup and self-check.

• vonode doctor checks the clock, Raspberry Pi power, ModemManager, modems and card readers, SIMs, the Vonode relay and
  subscription lease, fake-IP DNS (from a proxy or VPN on the router), whether UDP leaves through a proxy, and for each
  Wi-Fi Calling line whether the carrier's server name resolves and the server answers. Every problem comes with a
  plain-language cause and fix. The app's Network Check runs the same check. To compare the UDP and HTTPS exits, the node
  asks Cloudflare's public STUN server and the Vonode relay which address they see; the relay does not store it. For a line
  that is not registered, the node sends the carrier's server one harmless IKE_SA_INIT (no identity) at most every 10 minutes.
• One-line Docker Compose install: curl -fsSL https://vonode.cc/install/compose.sh | sudo sh (amd64 and arm64; add
  -s -- --dry-run to only download and verify). From v1.4.2 it verifies the signed compose file and pins the image by digest.
  Packages now carry a signature over the whole package (SHA256SUMS.sig), and the systemd installer refuses unsigned or
  older packages.

Other.

• Fixed a crash of the node service: v1.4.0 and v1.4.1 could stop with a segmentation fault during memory clean-up under
  load (for example while spam-protection data was being loaded) and be restarted by systemd or Docker, which dropped Wi-Fi
  Calling registrations and any call in progress.
• Modems whose radio must stay off are switched to low-power mode as soon as the node starts talking to them.
• Logs no longer contain full IMEIs; call and SMS actions are logged without numbers, digits or message text.
• Linux arm64 (for example Raspberry Pi 4, 64-bit OS) ships alongside amd64.
• The third-party notices now also list the embedded AOSP Carrier ID database (Apache-2.0), the swagger-ui assets, the eSIM
  root CI certificates and the research dataset that part of the VoWiFi carrier configuration hints is derived from.
• eSIM chip details now show the chip's own SAS accreditation number instead of a manufacturer guessed from the EID, and
  certificate issuers are named from their published certificates; issuers without a public certificate show their key ID.
• Known limitation: eSIM downloads from an SM-DP+ whose TLS chain ends at the Entrust eSIM CA, MC4 OT ROOT CI v1, China Mobile
  or China Unicom eSIM roots, or the expired SubMan V4.2 CI now fail; the node trusts only roots with a first-party published copy.
• Known limitation for Vonode app 1.4.1: the app's sender-rule editor keeps up to 100 rules per list and silently drops
  sender names with characters it does not know (for example non-Latin letters or & ' !), so saving sender rules from it
  can remove rules it did not show. Update to app 1.4.2 before editing sender rules that were added from the conversation
  menu or another phone.

中文说明

Wi-Fi 通话身份：User-Agent 与 IMEI 由你决定。

User-Agent。 每张 SIM 都有 User-Agent 设置（App：卡策略；Web：卡策略页）。默认是如实的 Vonode/<版本>，例如 Vonode/1.4.2，
运营商会因此知道本线路使用 Vonode；也可以从列表选手机画像，或自填 User-Agent（可打印 ASCII，最多 128 个字符）。v1.4.1 及更早版本在你
没选画像时，会发运营商设置里写死的手机 User-Agent（例如 iPhone 或 realme RMX3366）；现在不再这样。已选过画像的 SIM 保持原选择。
如果 Wi-Fi 通话注册不上，可能是运营商只接受某些手机。你可以选择手机画像，节点会以该机型向运营商标识自己；请先确认运营商条款允许。
Vonode 运营商设置原先默认使用的画像会在该 SIM 本次开机后首次启动 Wi-Fi 通话后显示，仅供参考。

IMEI。 部分运营商只允许其认可的手机型号使用 Wi-Fi 通话，在这些运营商上节点可能无法使用 Wi-Fi 通话。画像不再改变 IMEI：v1.4.1 及
更早版本中，选画像还会用按机型派生的 IMEI 替换 Wi-Fi 通话信令里的模组 IMEI。现在默认使用模组的真实 IMEI。你也可以在 App 里接受声明后，
填写一台你拥有、已永久停用的手机的 IMEI；节点会检查号码格式、确认本节点没有模组或其他线路在用它，绝不生成 IMEI；如果注册后网络显示
本号码的注册被使用同一 IMEI 的另一台设备取代，节点会停止该 SIM 的 Wi-Fi 通话。节点无法发现该 IMEI 被另一张 SIM 使用，请确保那台手机
不再使用。节点只把这个 IMEI 发给该 SIM 的运营商，从不发给 Vonode。归属网络在中国大陆或印度的 SIM 不提供用户提供的 IMEI。User-Agent 或
IMEI 改变的 SIM 会以新身份重新向 IMS 注册一次（IMEI 改变时 SIP 实例 ID 随之改变）；旧节点停机时未能注销的注册会自行过期。运营商覆盖文件里的
device_identity.enabled 已被忽略（只记录一次告警）。

验证码始终送达。 看起来像一次性验证码的短信（17 种语言的登录、验证或支付验证码）绝不放进“已过滤”，并且始终推送到 App——
即使发件人在“始终过滤”规则里、垃圾短信过滤会隐藏它或开启了勿扰；Telegram 等通知渠道也照常转发。节点只判断短信是否含验证码，
从不单独保存验证码。手动标为“垃圾”仍然有效。

健康告警（订阅或终身版）。 节点离线时（连续 15、30、60 或 120 分钟没有向 Vonode 中继续期，默认 30 分钟，在 App 里选择）App 会
收到提醒，恢复后再提醒一次。需要 App 1.4.2：节点所有者的手机默认开启，其他成员在 App 设置里自行打开；更早的 App 收不到健康告警。节点自己会在某条线路的 Wi-Fi 通话中断 10 分钟，或模组、读卡器丢失、SIM 不在位 3 分钟时提醒：每个问题
一条、恢复一条，只报根因；模组重启、eSIM 切换和节点重启期间不提醒。告警不占短信推送配额。节点告警按你的手机
加密，中继无法读取；经 Apple 发送的通知不带节点名称或 ID。

号码保号。 节点为每张 SIM 记录最近一次通常能保住预付费号码的活动（发出短信、从 App 拨出并接通的电话、成功的保号自动化步骤、
USSD 请求，或你在 App 里登记的充值），并显示还剩多少天。拨打或发送到免费号码（例如 0800、1-800）、紧急号码、求助热线和服务短号的
通话与短信不计入，节点无法确定的号码也不计入。内置 32 家英国、欧盟和美国预付费运营商的规则；只有 giffgaff 的 180 天经过确认，其余是
依据公开资料的估计，最多按 120 天计算。其中 9 家的公开资料不足，O2 英国网络上也只有自报为 O2 的卡才套用 O2 的规则，这些情况下
App 会请你自己设定周期；套用的规则名称与 SIM 运营商不同时，App 会注明按哪家的规则估算。已订阅或已购买终身版时，App 会在到期前 30、14、3 天收到
提醒。节点从不自动执行任何操作。升级后会从短信记录里补上最近一次发出的短信；节点不保存通话记录，此前的通话不计入。

Wi-Fi 通话诊断与运营商覆盖。

• App 为每条线路显示 Wi-Fi 通话不可用的原因：当前状态、白话原因、失败的步骤以及下次重试时间。
• 运营商持续拒绝某张 SIM 时，节点逐步放缓重试（15 分钟、1 小时、6 小时，之后不再自动重试），不再每 2 分钟重试一次；关闭再打开
  Wi-Fi 通话、重新连接或换卡后重新开始。
• 对没有 Vonode 精确画像的运营商，节点会尝试少数保守的替代方案（运营商服务器的两位网络号名称、兼容的加密报价、注册改用 TCP），
  鉴权失败后绝不再试，限制每张 SIM 的鉴权失败次数，并把对该网络有效的方案记住 30 天。
• 修复：运营商配置修订 3 并入既有画像的 36 个网络重新获得自动地址族与 TCP→UDP 回落。
• 归属网络在中国大陆或印度的 SIM 卡不提供 Wi-Fi 通话。插在模组里时，经移动网络的通话与短信照常可用；节点不再为这些 SIM 的
  Wi-Fi 通话关闭射频，App 会说明 Wi-Fi 通话为何关闭。

骚扰拦截。

• 来电：始终允许/始终拦截列表支持任意国际号码或本 SIM 所在国的国内格式（各最多 500 个）；可拒接隐藏号码来电（默认关闭）；App 可拒接
  iPhone 阻止列表里的号码的来电。被拦截的来电在通话记录里标为已拦截。经 Wi-Fi 通话时被拦截的主叫听不到振铃：节点在响铃前
  筛选并拒接，运营商不会把它当作“忙线”。因 iPhone 阻止列表拒接的来电同样处理。这种拒接对整条线路生效：你的号码若还在另一部手机上
  使用（例如开着 VoLTE 的手机），那部手机也会停止振铃。在 App 里手动拒接仍按“忙线”处理。国内格式规则同样适用于 USB 读卡器线路。
• 短信：发件人规则（最多 500 条）按接收线路所在国把同一号码的国内与国际格式视为相同，支持更多字母发件人名称，“已过滤”在短信到达时
  记录。免费档可以为固定号码管理发件人规则并纠正过滤结果。
• 未订阅时，选定的号码现在也可以经 Wi-Fi 通话接收短信（模组线路）。免费方案里 Wi-Fi 通话只收短信：运营商接受时节点只为短信注册，来电
  一律按“暂时无法接通”拒接（主叫转到语音信箱，或你的其他手机继续振铃）；发短信、通话、通知和其他号码仍需订阅。读卡器线路仍只给订阅用户。
• 已订阅或已购买终身版的节点除 FCC 数据外，还会直接从美国联邦贸易委员会（FTC）网站下载其公开的骚扰来电投诉数据，只在你的主机上保存带密钥摘要。

通话与短信。

• App 通话中按键（DTMF），以 RFC 4733 电话事件发送；不能发送按键时会告知 App，挂断不会因按键而延迟。
• 主叫在响铃中取消的来电记为未接，而不是拒接。
• 短信时间按 UTC 存储，不同时区的会话排序正确（已有短信会迁移；无法解析的时间跳过，不再导致启动失败）。

读卡器线路（实验性，仅订阅或终身版，默认关闭）。 USB 智能卡读卡器（CCID）里的 SIM 可作为无模组、仅 Wi-Fi 通话的线路收发通话与短信
（card_reader.enabled）。读卡器线路默认不报 IMEI，始终使用如实的 Vonode User-Agent；归属网络在中国大陆或印度的 SIM 不提供（读卡器线路只有 Wi-Fi 通话，
而这些 SIM 不提供 Wi-Fi 通话）；在长跑测试
完成前保持“实验性”标注。App 中读卡器线路 Wi-Fi 通话状态卡上的“重试”会重新连接并解除运营商拒绝后的放缓；读卡器被拔下或其中没有
SIM 卡时，状态会说明原因。经节点 API 关闭读卡器线路的 Wi-Fi 通话后，直到重新打开、换卡或节点重启前保持关闭。

读卡器中多号 eUICC 卡的 eSIM 管理（仅订阅或终身版；App 界面随 App 1.4.3 推出）。 读卡器线路里的卡是可擦写的多号 eUICC（例如 5ber、XeSIM、eSTK.me、9eSIM 卡）时，
App 的“SIM 卡与 eSIM”页像管理模组 eSIM 一样管理它：列出 profile，启用、停用、改名、删除，用激活码下载 profile，发送待发通知。所有 eSIM
逻辑都在节点上运行。启用或停用后节点给卡断电重新上电、重读身份并执行地域规则；发卡方在中国大陆或印度的 profile 在写卡前即拒绝启用。
读卡器线路下载时，节点把你为该线路登记的 IMEI 作为设备信息发给 SM-DP+；没有登记则拒绝下载（节点从不生成 IMEI）。写卡不可撤销；
不同厂商的卡行为不同，节点只使用 GSMA 标准接口。card_reader.esim_management: false 可关闭此功能。IMEI 声明升为
2026-10-19.1（增加发给 SM-DP+ 的去向），按旧版本接受的用户 IMEI 需要重新接受。

安装与自检。

• vonode doctor 检查时钟、树莓派供电、ModemManager、模组和读卡器、SIM 卡、Vonode 中继与订阅租约、fake-ip DNS（来自
  路由器上的代理或 VPN）、UDP 是否经过代理，以及每条 Wi-Fi 通话线路的运营商服务器域名能否解析、服务器是否应答；
  每个问题都给出白话原因和处理办法。App 的“网络体检”执行同一套检查。为比较 UDP 与 HTTPS 出口，节点会询问 Cloudflare 的公共
  STUN 服务器和 Vonode 中继看到的地址，中继不保存它。对尚未注册的线路，节点最多每 10 分钟向运营商服务器发送一个无害的
  IKE_SA_INIT（不含任何身份）。
• Docker Compose 一行安装：curl -fsSL https://vonode.cc/install/compose.sh | sudo sh（amd64 与 arm64；加 -s -- --dry-run
  只下载和校验）。自 v1.4.2 起校验已签名的 compose 文件，并按摘要固定镜像。发布包新增整包签名 SHA256SUMS.sig，systemd 安装程序
  拒绝未签名或更旧的安装包。

其他。

• 修复节点服务崩溃：v1.4.0 与 v1.4.1 在负载下回收内存时（例如载入骚扰拦截数据期间）可能因段错误退出，由 systemd 或 Docker 重启，期间 Wi-Fi 通话注册与正在进行的通话会中断。

• 需要保持射频关闭的模组在节点开始与其通信时立即进入低功耗模式。

• 日志不再包含完整 IMEI；通话与短信动作的日志不含号码、按键或短信正文。

• 与 amd64 同时提供 Linux arm64（例如 64 位系统的树莓派 4）。

• 第三方声明补列内嵌的 AOSP 运营商 ID 数据库（Apache-2.0）、swagger-ui 资源、eSIM 根 CI 证书，以及 VoWiFi 运营商配置提示部分派生自的研究数据集。

• eSIM 芯片信息改为显示芯片自报的 SAS 认证号，不再按 EID 推测厂商；证书签发机构名称取自其公开证书，没有公开证书的显示 key ID。

• 已知限制：TLS 链终于 Entrust eSIM CA、MC4 OT ROOT CI v1、中国移动或中国联通 eSIM 根、或已过期 SubMan V4.2 CI 的 SM-DP+ 将无法下载 eSIM；节点只信任有第一方公开副本的根。

• 已知限制（App 1.4.1）：App 1.4.1 的发件人规则编辑器每张列表最多 100 条，并会悄悄丢掉含它不认识的字符（例如非拉丁字母或 & ' !）的发件人名称，因此在其中保存发件人规则可能删掉它没有显示的规则。编辑从会话菜单或其他手机添加的发件人规则前，请先更新到 App 1.4.2。

• Install: download the package for your machine (uname -m: x86_64 = amd64, aarch64 = arm64), check it against its .sha256, then follow https://vonode.cc/install/

  • amd64: vonode_v1.4.2_linux_amd64_commercial.tar.gz (vonode_v1.4.2_linux_amd64_commercial.tar.gz.sha256); update file vonode_v1.4.2_linux_amd64_commercial with vonode_v1.4.2_linux_amd64_commercial.sig; GPL/LGPL source vonode_v1.4.2_linux_amd64_commercial.sources.tar; SBOM vonode_v1.4.2_linux_amd64_commercial.spdx.json.
  • arm64: vonode_v1.4.2_linux_arm64_commercial.tar.gz (vonode_v1.4.2_linux_arm64_commercial.tar.gz.sha256); update file vonode_v1.4.2_linux_arm64_commercial with vonode_v1.4.2_linux_arm64_commercial.sig; GPL/LGPL source vonode_v1.4.2_linux_arm64_commercial.sources.tar; SBOM vonode_v1.4.2_linux_arm64_commercial.spdx.json.

• Nodes already installed offer this update in the Vonode app (More > Software update); latest-commercial.json lists the signed update file of every architecture.

• The GPL/LGPL components (strongSwan, glibc, GMP) are linked per architecture, so each architecture has its own corresponding source archive.

• Docker image: vonode/vonode@sha256:a6656981dbc4575bb363dff994858f80d116e43e044f770ee69570232b6bc8e8. The package's docker/setup.sh uses it by default; the standalone docker-compose.yml asset is pinned to it.

• Corresponding source of the GPL/LGPL/MPL Alpine Linux packages in the Docker image: vonode-1.4.2-docker-alpine-sources.tar.

Vonode is proprietary software of VONODE LLC. This repository holds release files only, no source code.