<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<blockquote type="cite"
cite="mid:e7e35a6d-8468-48e1-b0cc-eee401a8c055@posteo.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font size="2">Hi all and cheers for all your replies.<br>
</font></p>
<p><font size="2">I aimed to convey: I have no (longer) update
issues from the moment I recently found out that the change
introduced beginning of this month was <br>
NOT A CHANGE OF KEY<br>
rather this was <br>
AN UPDATE IN THE REPO ()we returned to a deb.only repos for
all.<br>
<br>
And what this implies is HUGE, because most non-pro-active
servers out on the netwroks, all operators gone, who lost
access to their Unattended settlements, who trusted TOR, US
ALL for respecting the FEATURE of Unattendedness have now
running server Eternally flown with MiM-Repo-weak servers.<br>
<br>
I implied to ask: DO you guys realize that <b>Unattendness is
a Feature</b> to build around and not to change while asking
everyone to upgrade / Attend.<br>
Unattended servers are abandonned, they work and their owners
could have been killed, lost interest, yet they were meant to
work for us all.<br>
</font></p>
<p><font size="2">What is the share of our network that will
upgrade from non-deb, obsoleting repos, and who is going to
Man-In-the=Middle that repos and OPA (acquire for free) ALL
those lone servers.<br>
<br>
This is a monstruous danger to the network.<br>
<br>
Carlos.<br>
<br>
<br>
</font></p>
<div class="moz-cite-prefix">On 8/14/24 9:07 PM, Toralf Förster
via tor-relays wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ecce7220-57f1-46d4-b788-6f0f5a5b1cba@gmx.de">On
8/14/24 19:44, boldsuck wrote: <br>
<blockquote type="cite">upgrades are running or not. And that I
have to reboot because of the kernel <br>
upgrade or similar. (I don't like auto reboots) <br>
</blockquote>
<br>
Ah, ok. <br>
I like it and have therefore unattended upgrade configured <br>
unconditionally for all packages [1]. <br>
<br>
Furthermore I do use needrestart to detect services and/or
kernel <br>
requiring a reboot and do it [2]. <br>
<br>
So it works all out of the box w/o manual intervention here. <br>
<br>
[1] <br>
<a class="moz-txt-link-freetext"
href="https://github.com/toralf/tor-relays/blob/main/playbooks/roles/setup_common/tasks/auto-update.yaml"
moz-do-not-send="true">https://github.com/toralf/tor-relays/blob/main/playbooks/roles/setup_common/tasks/auto-update.yaml</a>
<br>
[2] <br>
<a class="moz-txt-link-freetext"
href="https://github.com/toralf/tor-relays/blob/main/playbooks/roles/setup_common/tasks/reboot.yaml"
moz-do-not-send="true">https://github.com/toralf/tor-relays/blob/main/playbooks/roles/setup_common/tasks/reboot.yaml</a>
<br>
<br>
-- <br>
Toralf <br>
<br>
_______________________________________________ <br>
tor-relays mailing list <br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:tor-relays@lists.torproject.org"
moz-do-not-send="true">tor-relays@lists.torproject.org</a> <br>
<a class="moz-txt-link-freetext"
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays"
moz-do-not-send="true">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
<br>
</blockquote>
<pre class="moz-signature" cols="72">--
</pre>
</blockquote>
<br>
</body>
</html>