Torix, I just tried your workaround, the issue still occurs. Thank you. --Keifer On Tue, Oct 27, 2020 at 1:58 PM <torix@protonmail.com> wrote:

Dear Keifer,

Just guessing here, but have you tried reverting your sources.list to http?

As for the notices and notices.1, this seems like normal linux log rotation. See if you don't have an /etc/logrotate.d/tor file that gives the structure of how the tor log is handled. Mine is set to rotate to a new file daily, so notices.log is renamed to notices.log.1, and the new log is notices.log. Notices.log.1 is zipped up to notices.2.tgz, and so on, and the last 5 days of files are kept before being deleted.

--Torix

Sent with ProtonMail <https://protonmail.com> Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, October 27, 2020 8:30 PM, Keifer Bly <keifer.bly@gmail.com> wrote:

Hi all, so for my bridge at

https://metrics.torproject.org/rs.html#details/EF36AE38C162E96E0645E1DF25EF1...

I am some reason unable to update tor and obfs4 to the newest version. Upon running sudo apt update && sudo apt install -y --only-upgrade tor

I am getting an error saying that updating from such a resprrtory can’t be done securely and is therefor disabled by default. I have the following entered in Debian file /etc/apt/sources.list:

deb https://deb.torproject.org/torproject.org focal main deb-src https://deb.torproject.org/torproject.org focal main

So am not sure why it thinks this is insecure.

Another thing I noticed, it seems that for some reason, for the tor traffic log file, it switches from writing to notices.log to notices.log.1 automatically after a while, this happened on both my bridge and my relay though I did not tell it to do this.

I wonder why the update error is happening, thank you.