jperkin: "pkg_add: unable to verify signature: Signature key id" how do I update the key?

Smithx10: assuming illumos trunk, follow the "Standard (upgrade)" instructions at pkgsrc.smartos.org/install-on-illumos

This is inside of the base-64-lts 21.4.0 zone

never had to do that before

the key didn't change for 21.4.0

so .. not sure what's going on there

ran the upgrade

eek, no

uh oh

ok, one moment..

from within the zone I ran pkgin update i believe

Ill redeploy that image

Dont think I need it anyway

oh, if you're able to then that'll probably be easiest, make sure you get the latest version which uses pkgsrc.smartos.org

There is a new base-64-lts?

the only thing that changed for LTS releases is the URL, the signing key is exactly the same (basically until the LTS are EOL), so something else must have happened for you to now get different packages

85d0f826-0131-11ed-973d-2bfeef68011c right?

I released 20.4.1 and 21.4.1 images which have the updated URLs in place

yeh looks good

Joyent no longer in the motd lol

if you did want to retain that older image then unpacking pkgsrc.smartos.org/packages/SmartOS…tstrap-2021Q4-x86_64-upgrade.tar.gz over the top should fix it

"brought to you by MNX" :P

yeh, rip

companies don't write/maintain/package software; people do. I'm grateful for jperkin's employers past and present, but I know who's doing the pkgsrc work. :)

Well they get the add rights by Paying cash, it's a small enough price imho

At MNX we've decided to do all of the Triton/SmartOS stuff under the quazi-organization Triton.

There's not a legal framework around it, but the vendor is considered to be Triton or Triton Data Center.

MNX gets copyrights, which is clearly attributed in the source, but otherwise we didn't want to have to go through the whole mess if disentangling the company name if there happens to be change of ownership at any time in the future.

Hmmm might be a good discussion for ARM

LLDP doesn't work when the interfaces are in an aggregation right?

Any other way to get port info from ToR to get around that?

Is there LACP on them? Could you sniff it, if so?

hmmm, where were the pkgsrc trunk build logs? caddy seems to be missing from it...

(and 21Q4 has 2.4.5 when 2.6.2 is newest)

mail-index.netbsd.org/pkgsrc-bulk - us-central.manta.mnx.io/pkgsrc/publ…21119.0803/caddy-2.6.2nb1/build.log

undefined: unix.SO_REUSEPORT

caddy requirements: Go 1.18 or newer

and trunk has go-1.19.3.tgz

so... from running a nat/fw/tls termination zone, to running nat/fw zone, tunneling to lx tls termination...

I don't like tne amount of hops for data, but there's just no way to keep running stuff on native zones

and that design will break the current certificate infra in place... the yak shaving just keeps going deeper. I just wanted a tls certificate for an ip, and I'm something like 15 hours in with it...=)