sockscap

  • Posts

    5
  • Joined

  • Last visited

sockscap's Achievements

  1. Thanks for the reply. A few more questions: 1. It sounds like the keys will not be synchronized automatically between these servers, and it relies on key owners' manual action? I'm a little worried, if I encounter the issue again, how do I know which server holds the info? For example, I initially thought keyring.debian.org should work, but actually it's not. 2. If I simply use the default sources.list like the one below, what key server is considered to be the official one? deb http://httpredir.debian.org/debian stretch main contrib non-free #deb-src http://httpredir.debian.org/debian stretch main contrib non-free deb http://httpredir.debian.org/debian stretch-updates main contrib non-free #deb-src http://httpredir.debian.org/debian stretch-updates main contrib non-free deb http://httpredir.debian.org/debian stretch-backports main contrib non-free #deb-src http://httpredir.debian.org/debian stretch-backports main contrib non-free deb http://security.debian.org/ stretch/updates main contrib non-free #deb-src http://security.debian.org/ stretch/updates main contrib non-free 3. What's the purpose of https://ftp-master.debian.org/keys.html? I'm asking because it sounds like the official source which should be the most trustful. Can I use the info from it to generate the keys missing?
  2. It's a Debian stretch server (Armbian to be specific). When I ran "apt-get update" the day before yesterday, it gave me an error: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9". I searched the Internet and finally resolved the issue by running the following commands: apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 648ACFD622F3D138 apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9 Initially I tried to use "--keyserver keyring.debian.org" but it didn't work. Therefore, I did some further research, and I read from https://wiki.debian.org/SecureApt that "The current and the retired Debian archive "signing" keys are available from https://ftp-master.debian.org/keys.html." The latter web page provides the key as ".asc" files, but I cannot find how should I do with these ".asc" files. Could someone point out the official recommended method to fix such NO_PUBKEY errors? It's a bit strange that I have to consult ubuntu keyserver to fix Debian signing key issues.
  3. For some special reason, I want to make sure bluetooth is completely disabled. I have done the following: 1. Try to run hcitool & bluetoothctl. Both commands are unavailable on the system. 2. Run "systemctl status bluetooth", it says "Unit bluetooth.service could not be found." 3. Run "service --status-all", it doesn't show bluetooth entry. I'd assume bluetooth isn't enabled, but when I run "dmesg |grep Bluetooth", it shows: [ 13.744331] Bluetooth: Core ver 2.22 [ 13.744337] Bluetooth: Starting self testing [ 13.761692] Bluetooth: ECDH test passed in 16935 usecs [ 13.764626] Bluetooth: SMP test passed in 2804 usecs [ 13.764636] Bluetooth: Finished self testing [ 13.764717] Bluetooth: HCI device and connection manager initialized [ 13.764729] Bluetooth: HCI socket layer initialized [ 13.764734] Bluetooth: L2CAP socket layer initialized [ 13.764748] Bluetooth: SCO socket layer initialized [ 13.778717] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 What's the correct method to verify whether bluetooth is enabled on the system? In addition, what's the correct method to completely disable bluetooth? Any suggestions are appreciated.