i was thinking like, lets say i wanted an extra layer of security between me and freebsd-update
i would login to https://cert.freebsd.org, type in a few things, check a few checkboxes, get a ssl cert from an official server, and i should be able to do something like freebsd-update --encrypted $CERT and all communications would be relatively secure. i think ssl certs can expire with a precoded time limit. but it would encrypt the communication with a cool ssl cert you can save for communication with that server. then the ssl cert can be store in a diretory or on removable media
there should always be the normal method of getting files from freebsd-update and pkg and etc, but if someone or a freebsd member wants to code this it would be awesome (it would also be cool having a cert from freebsd.org lol)
i would login to https://cert.freebsd.org, type in a few things, check a few checkboxes, get a ssl cert from an official server, and i should be able to do something like freebsd-update --encrypted $CERT and all communications would be relatively secure. i think ssl certs can expire with a precoded time limit. but it would encrypt the communication with a cool ssl cert you can save for communication with that server. then the ssl cert can be store in a diretory or on removable media
there should always be the normal method of getting files from freebsd-update and pkg and etc, but if someone or a freebsd member wants to code this it would be awesome (it would also be cool having a cert from freebsd.org lol)