apt repo: allow insecure repos

[kyrofa]

• Have you followed the guidelines for contributing?
• Have you signed the CLA?
• If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on bug reports?
• If this is a new feature. Have you discussed the design on the forum?
• Have you successfully run ./runtests.sh static?
• Have you successfully run ./runtests.sh unit?

---

In Xenial this was the default behavior, which explains why Snapcraft works. However, in Zesty this behavior changed, causing breakage when using external repositories (e.g. ROS). Instead of relying on defaults, ensure the behavior is consistent across releases.

This is not a long-term fix. We should add a way to ack repository keys.

[kalikiana]

This makes complete sense to me, considering we need consistent behavior, and this matches behavior on LTS.

Maybe log bug report to follow up on how to add keys in the future?

[kyrofa]

Maybe log bug report to follow up on how to add keys in the future?

Yeah we need to have a discussion about it. Here's a forum post.

[elopio]

Thank you!

[sergiusens]

sorry to say that I am in needs fixing mode, but I would expect the default to be the sane one instead of the allow anything in one.

[kyrofa]

@sergiusens this is causing autopkgtests to fail on zesty and artful today. We need to design a key-handling solution to use the sane default. How would you like to deal with the autopkgtests?

[kyrofa]

Alright we're going to skip instead.