-
Posts
7,428 -
Joined
-
Last visited
-
Days Won
19
~Brian~ last won the day on May 17 2023
~Brian~ had the most liked content!
About ~Brian~
Previous Fields
-
Diapers
Incontinent
-
I Am a...
Boy
-
Age Play Age
Not at this time
Profile Information
-
Gender
Male
-
Location
Vermont, USA
-
Real Age
51
Contact Methods
-
Website URL
https://buddy-baker.us
Recent Profile Visitors
44,848 profile views
~Brian~'s Achievements
-
GPG/APT-KEY CONVERSION/MIGRATION MARCH 13, 2024 @23:58 EDT GPG Keys for Myself: Had to make those, and then upload them to GitHub: One Secret Key, One public Key, using <root@> Used information on the github site to make these keys, and I will have to check these to see if there is anything else I need to do there. I will be monitoring it also. GPG Public Keys for BBUS: I will work to get those uploaded sometime this week, so that if it is needed, I have it there. Public and Secret keys were made and public keys just need to be able to match, so I will check that later today or tomorrow MIGRATION OF APT-KEY TO GPG: This seems to be completed successfully. Used a script I downloaded from Github to make the changes, as apt-key was One, Giving me errors about apt-key being depreciated, and using /etc/apt/trusted.gpg.d/ instead. Two: It would give me warnings when apt-get update was commanded. Seems to be corrected, and now, I have to solve a problem that happens when I do an 'apt-get update && apt-get upgrade', where some packages are 'held back' and it asks me to delete some: Gonna leave them there for now Script: I downloaded a script I call gpg-migration.zip - It takes the old apt-key format, and migrates it over to the gpg format. It is called migrate-apt-keys.sh - when done, it takes all of the keys it finds, converts them from apt-key format to gpg format, using the /etc/apt/trusted.gpg, and the /etc/apt/sources.list.d/ directories listed below: brian@cardinal:/etc/apt/trusted.gpg.d$ ls -l total 88 -rw-r--r-- 1 root root 8700 Mar 18 2023 debian-archive-bookworm-automatic.gpg -rw-r--r-- 1 root root 8709 Mar 18 2023 debian-archive-bookworm-security-automatic.gpg -rw-r--r-- 1 root root 280 Mar 18 2023 debian-archive-bookworm-stable.gpg -rw-r--r-- 1 root root 8700 Feb 25 2021 debian-archive-bullseye-automatic.gpg -rw-r--r-- 1 root root 8709 Feb 25 2021 debian-archive-bullseye-security-automatic.gpg -rw-r--r-- 1 root root 2453 Feb 25 2021 debian-archive-bullseye-stable.gpg -rw-r--r-- 1 root root 8132 Feb 25 2021 debian-archive-buster-automatic.gpg -rw-r--r-- 1 root root 8141 Feb 25 2021 debian-archive-buster-security-automatic.gpg -rw-r--r-- 1 root root 2332 Feb 25 2021 debian-archive-buster-stable.gpg -rw-r--r-- 1 root root 2292 Jan 31 23:54 php.gpg -rw-r--r-- 1 root root 1769 Jan 2 06:48 php.gpg~ -rw-r--r-- 1 root root 2836 Nov 15 12:45 varnishcache_varnish60lts.gpg brian@cardinal:/etc/apt/trusted.gpg.d$ and the /etc/apt/sources.list.d/ directory: brian@cardinal:/etc/apt/sources.list.d$ ls -l total 16 -rw-r--r-- 1 root root 746 Mar 13 23:22 mysql.list -rw-r--r-- 1 root root 106 Mar 13 23:23 php.list -rw-r--r-- 1 root root 313 Mar 13 23:23 varnishcache_varnish60lts.list -rw-r--r-- 1 root root 135 Nov 15 08:40 webmin.list brian@cardinal:/etc/apt/sources.list.d$ Looking at the list files here they look like this: ### THIS FILE IS AUTOMATICALLY CONFIGURED ### # You may comment out entries below, but any other modifications may be lost. # Use command 'dpkg-reconfigure mysql-apt-config' as root for modifications. deb [ signed-by=/usr/share/keyrings/mysql-archive-keyring.gpg] http://repo.mysql.com/apt/debian/ bullseye mysql-apt-config deb [ signed-by=/usr/share/keyrings/mysql-archive-keyring.gpg] http://repo.mysql.com/apt/debian/ bullseye mysql-8.0 deb [ signed-by=/usr/share/keyrings/mysql-archive-keyring.gpg] http://repo.mysql.com/apt/debian/ bullseye mysql-tools #deb http://repo.mysql.com/apt/debian/ bullseye mysql-tools-preview deb-src [ signed-by=/usr/share/keyrings/mysql-archive-keyring.gpg] http://repo.mysql.com/apt/debian/ bullseye mysql-8.0 Each file in the sources.list.d/ directory appears to be correct after the gpg conversion. the /usr/share/keyrings directory also seems to be correct as well - Now to see if there is anything I need to do after that. For those interested in the apt-key-migration script, I will place a link where you can download it from the BBUS Network of sites: I am not sure where I want to place it yet, but I will decide soon. (Note that it will create a bunch of files that have apt.key after them, and you HAVE to remove those after the conversion or apt-get update will error and throw warnings). That's all for now, long day for me today Thanks for all the comments and suggestions: I have had to make this apt-key to gpg upgrade now, because apt-key will NOT work in Bookworm or any other distro after it. As Always, comments/suggestions are welcomed Brian
-
Mountain (Jay Peak, Vermont)
-
~Brian~ started following I've Had It!
-
Baker (Name of the Sign Company My grampa owned and ran. In St. Johnsbury Center Vermont) I am PROUD of being a Baker as well
-
@DailyDi I wish you and you mom the best, and I will be praying for you BOTH Best Wishes and HUGS to Both of you Brian
-
UPDATE: (3/4/2024 @14:40 EST DOMAIN NEWS BBUS DOT INFO: This site has been Configured, Installed, IP has been pointed to Cardinal, and SSL certificates have been obtained for all 10 of the domains in my network: It took me a while to get it working, as there are 2 sites that have 301's that redirect people to the .us/blog section, and to .com/Main, so that they don't have to TYPE anything in the address bar. Apparently, there was a DUPE of the instructions when I started, so bbus.info was going to bbdc/Main, and I had to track that down and fix that - Now, BBUS Dot Info runs in its own directory, and is responding nicely. Now, all I have to do is decide what I want to put there Brian