Re: Log file *detailed* content description
On 12/13/23 08:24, Dave Close wrote: I asked: For example, given the message, Accepted publickey for ... from ... port ... ssh2: RSA SHA256:QSyKp5SJ8gJFcYtbtb9SQ1axtqSg7fEoQBiZf3kPXgU what is the meaning of the RSA value listed? Is it a "fingerprint"? How can I compare it to the various keys on my system? Roberto Ragusa answered: ssh-keygen -lf ~/.ssh/id_rsa.pub This comes up easily on Google. I wasn't asking for the value related to my public key. I'm not likely to see whatever the related value for that key might be in an "Accepted publickey" message on my own system. My question was, when someone connects to my system, which key in my authorized_keys file were they using? That seems to have been a more difficult question. But see my next message. Since the command above wants the public key, you just have to provide it with the lines in your authorized_keys. e.g. while read a; do echo "$a"|ssh-keygen -lf -;done <~/.ssh/authorized_keys Regards. -- Roberto Ragusamail at robertoragusa.it -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 6.6.x kernels do not boot successfully
Sent from ProtonMail, encrypted email based in Switzerland. Sent with Proton Mail secure email. On Tuesday, December 12th, 2023 at 8:01 PM, Toni Andjelkovic via users wrote: > Same problem here on an Acer Aspire 5 notebook. > > Kernel 6.6.4-200.fc39 hangs on booting, the last screen line shows the > libvirtqemud service being started [OK], then the machine hangs. > > Everything works fine with kernel version 6.5.12-300.fc39.x86_64. > > -- > Mit freundlichen Grüßen > Toni Andjelkovic > http://toni.sdf-eu.org/ > mailto:t...@sdf-eu.org > -- In looking for related situations I found one that could be related in some way. The computer I have has an nvme drive. I did not want to boot windows on it which is default so I added another drive and I installed Fedora on it. It worked beautifully since Fedora 36 and I have updated successfully on it till I hit this newer kernels 6.6.X ones. This person encounters a problem dual booting [1] There is ACPI/AHCI etc. lsblk -o NAME,FSTYPE,SIZE,LABEL,FSSIZE,FSUSE%,MOUNTPOINTS,uuid The nvme drive is not seen from output here olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsblk -o NAME,FSTYPE,SIZE,LABEL,FSSIZE,FSUSE%,MOUNTPOINTS,uuid NAME FSTYPE SIZE LABEL FSSIZE FSUSE% MOUNTPOINTS UUID sda 447.1G ├─sda1 │vfat 600M 598.8M 3% /boot/efi 7DA1-D957 ├─sda2 │ext4 1G 973.4M24% /boot 206a24f4-e24d-4bb0-9b85-fa9f706cd263 └─sda3 btrfs 445.5G fedora_localhost-live 445.5G22% /home 8ff57a6b-2a55-4e9d-870d-855d68d35bee / sdb vfat28.9G USB321FD 28.8G62% /run/media/olivares/USB321FD 75C7-0C5C sr0 1024M zram0 7.3G [SWAP] olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo fdisk -l Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors Disk model: KINGSTON SA400S3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: D7396A11-5AEF-4B52-943C-D4DE7F9AB4A7 Device Start End Sectors Size Type /dev/sda1 2048 1230847 1228800 600M EFI System /dev/sda2 1230848 3327999 2097152 1G Linux filesystem /dev/sda3 3328000 937701375 934373376 445.5G Linux filesystem Disk /dev/sdb: 28.85 GiB, 30979129856 bytes, 60506113 sectors Disk model: USB 3.2.1 FD Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x69737369 Device Boot StartEndSectors Size Id Type /dev/sdb1 1869771365 2038460886 168689522 80.4G 69 unknown /dev/sdb2 1701519481 3571400945 1869881465 891.6G 73 unknown /dev/sdb3 2573 2573 0 0B 74 unknown /dev/sdb4 2885681152 2885733566 52415 25.6M 0 Empty Partition table entries are not in disk order. Disk /dev/zram0: 7.32 GiB, 786432 bytes, 192 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes In the BIOS(which is not the BIOS anymore), there are some settings that I tried but with no success. The machine has windows but I never booted it. I do not want to boot it. The fast boot could be an issue with this but I would need to try some things. Please suggest some things I can try. I dont mind trying some things. But I do need to use the computer, and upon trying and not being able to boot the newer kernels I just remove the new kernel and keep the reliable 6.5.12 kernel. Thank you in advance, Antonio [1] https://discussion.fedoraproject.org/t/yep-another-windows-dual-boot-problem/98509 -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 6.6.x kernels do not boot successfully
Sent from ProtonMail, encrypted email based in Switzerland. Sent with Proton Mail secure email. On Wednesday, December 13th, 2023 at 8:34 AM, olivares33561 via users wrote: > > > Sent from ProtonMail, encrypted email based in Switzerland. > > Sent with Proton Mail secure email. > > > On Tuesday, December 12th, 2023 at 8:01 PM, Toni Andjelkovic via users > users@lists.fedoraproject.org wrote: > > > > > Same problem here on an Acer Aspire 5 notebook. > > > > Kernel 6.6.4-200.fc39 hangs on booting, the last screen line shows the > > libvirtqemud service being started [OK], then the machine hangs. > > > > Everything works fine with kernel version 6.5.12-300.fc39.x86_64. > > > > -- > > Mit freundlichen Grüßen > > Toni Andjelkovic > > http://toni.sdf-eu.org/ > > mailto:t...@sdf-eu.org > > -- > > > In looking for related situations I found one that could be related in some > way. The computer I have has an nvme drive. I did not want to boot windows on > it which is default so I added another drive and I installed Fedora on it. It > worked beautifully since Fedora 36 and I have updated successfully on it till > I hit this newer kernels 6.6.X ones. This person encounters a problem dual > booting [1] > There is ACPI/AHCI etc. > > lsblk -o NAME,FSTYPE,SIZE,LABEL,FSSIZE,FSUSE%,MOUNTPOINTS,uuid > The nvme drive is not seen from output here > > olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsblk -o > NAME,FSTYPE,SIZE,LABEL,FSSIZE,FSUSE%,MOUNTPOINTS,uuid > NAME FSTYPE SIZE LABEL FSSIZE FSUSE% MOUNTPOINTS UUID > sda 447.1G > ├─sda1 > │ vfat 600M 598.8M 3% /boot/efi 7DA1-D957 > ├─sda2 > │ ext4 1G 973.4M 24% /boot 206a24f4-e24d-4bb0-9b85-fa9f706cd263 > └─sda3 > btrfs 445.5G fedora_localhost-live 445.5G 22% /home > 8ff57a6b-2a55-4e9d-870d-855d68d35bee > / > sdb vfat 28.9G USB321FD 28.8G 62% /run/media/olivares/USB321FD > 75C7-0C5C > sr0 1024M > zram0 > 7.3G [SWAP] > olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ > > olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo fdisk -l > Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors > Disk model: KINGSTON SA400S3 > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: gpt > Disk identifier: D7396A11-5AEF-4B52-943C-D4DE7F9AB4A7 > > Device Start End Sectors Size Type > /dev/sda1 2048 1230847 1228800 600M EFI System > /dev/sda2 1230848 3327999 2097152 1G Linux filesystem > /dev/sda3 3328000 937701375 934373376 445.5G Linux filesystem > > > Disk /dev/sdb: 28.85 GiB, 30979129856 bytes, 60506113 sectors > Disk model: USB 3.2.1 FD > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0x69737369 > > Device Boot Start End Sectors Size Id Type > /dev/sdb1 1869771365 2038460886 168689522 80.4G 69 unknown > /dev/sdb2 1701519481 3571400945 1869881465 891.6G 73 unknown > /dev/sdb3 2573 2573 0 0B 74 unknown > /dev/sdb4 2885681152 2885733566 52415 25.6M 0 Empty > > Partition table entries are not in disk order. > > > Disk /dev/zram0: 7.32 GiB, 786432 bytes, 192 sectors > Units: sectors of 1 * 4096 = 4096 bytes > Sector size (logical/physical): 4096 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > In the BIOS(which is not the BIOS anymore), there are some settings that I > tried but with no success. The machine has windows but I never booted it. I > do not want to boot it. The fast boot could be an issue with this but I would > need to try some things. > Please suggest some things I can try. I dont mind trying some things. But I > do need to use the computer, and upon trying and not being able to boot the > newer kernels I just remove the new kernel and keep the reliable 6.5.12 > kernel. > > Thank you in advance, > > > > Antonio > > > [1] > https://discussion.fedoraproject.org/t/yep-another-windows-dual-boot-problem/98509 > > -- I checked BIOS settings it was set to RAID, set it to ACHI and now I can see a little bit more when starting 6.6.4 fedora kernel [ OK ] Started plymouth-start.service - Show Plymouth Boot Screen. [ OK ] Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target paths.target - Path Units. [ OK ] Reached basics.target - Basisc System. [ 2.089697 ] nvme nvme0: 12/0/0 default/read/poll queues [ 2.092182 ] nvme0n1: p1 p2 p3 p4 p5 p6 [ 2.093443 ] r8169 :03:00.0 enp3s0: renamed from eth0 . Starting dracut-pre-pivot.service - dracut pre-pivot and cleanup hook... I selected the 6.64 kernel and removed rhgb quiet. Screen stays there kernel does not boot. Saw these pages for reference: https://bugzilla.redhat.com/show_bug.cgi?id=1328229 https://fedoraproject.org/wiki/How_to_debug_Dracut_problems will try to de
Re: 6.6.x kernels do not boot successfully
> > I checked BIOS settings it was set to RAID, set it to ACHI and now I can see > a little bit I guess reinstalling the problematic kernel might help sudo dnf reinstall kernel-... I guess your previous Bios setting to RAID might have had (correct english ?) some influences to your current none booting initramfs, what is generated during kernel installs ... -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
ssh access sshKey/password
Hi. I know.. list is really only for fedora! But I was hoping I might find someone who could point me in a direction to figure out what's going on. This is a digitalocean/ubuntu issue for setting up/testing SSH access. Since this is a test, I'm more than willing to grant root access to figure this out. I've created snapshots to recreate the droplet/instance. thanks == I have a test digitalocean droplet. It was setup for ssh access. It more or less works. I have a few test users that I can ssh into with no issue. I also created a test user with no ssh key, to test ssh with password. ssh testu@1.2.3.4 generates the "password" prompt to login, as expected. I've tested this with a copy of "centos", as well as another ubuntu 20.04 system. Both tests seem to work as expected. I decided to do a copy of the initial DO droplet -- 161.35.5.174 and to create another copy of this with the same dir/files/processes. steps: turn off "161.35.5.174" Create a "snapshot" of the "161.35.5.174" Use the "snapshot" to create another droplet with a diff IP. "161.35.5.x" turn on 161.35.5.174 and use 161.35.5.x so I now should have 2 valid droplets, with SSH access... Now, at this point, I thought/assumed/hoped the user could simply access the new droplet via SSH the same as the initial droplet. I was sadly mistaken! Or I have a subtle/massive user err. my test users root sroot crawl_user *testu Each of these have ssh keys/dirs on/in the droplets (except fo testu, which is a simple user acct) When I'm on the test centos, and I ssh into the 161.35.5.174, everything works.. ssh -v sroot@161.35.5.174 works as expected... So, it appears the "161.35.5.174" initial droplet works as expected, which implies the "ssh" server/daemon is working, and that the /etc/ssh/sshd_config is configured/set The idea is to allow for "root" access -- for the test My goal for the overall test, is to allow ssh access into the 161.35.5.174 droplet via sshKey, as well as password. and to do the same for the copied/created droplet *** THIS ISN'T WORKING!!! when I'm on the centos and I test ssh -vvv sroot@165.227.198.59 to allow sshKey, as well as "password" access via ssh the results are: sroot@ubuntu-s-1vcpu-2gb-nyc1-01:~$ ssh -vvv testu@165.227.198.59 OpenSSH_9.3p1 Ubuntu-1ubuntu3, OpenSSL 3.0.10 1 Aug 2023 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_canonicalize: hostname 165.227.198.59 is address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/sroot/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/sroot/.ssh/known_hosts2' debug3: ssh_connect_direct: entering debug1: Connecting to 165.227.198.59 [165.227.198.59] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/sroot/.ssh/id_rsa type -1 debug1: identity file /home/sroot/.ssh/id_rsa-cert type -1 debug1: identity file /home/sroot/.ssh/id_ecdsa type -1 debug1: identity file /home/sroot/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/sroot/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/sroot/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/sroot/.ssh/id_ed25519 type -1 debug1: identity file /home/sroot/.ssh/id_ed25519-cert type -1 debug1: identity file /home/sroot/.ssh/id_ed25519_sk type -1 debug1: identity file /home/sroot/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/sroot/.ssh/id_xmss type -1 debug1: identity file /home/sroot/.ssh/id_xmss-cert type -1 debug1: identity file /home/sroot/.ssh/id_dsa type -1 debug1: identity file /home/sroot/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_9.3p1 Ubuntu-1ubuntu3 debug1: Remote protocol version 2.0, remote software version OpenSSH_9.3p1 Ubuntu-1ubuntu3 debug1: compat_banner: match: OpenSSH_9.3p1 Ubuntu-1ubuntu3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 165.227.198.59:22 as 'testu' debug3: record_hostkey: found key type ED25519 in file /home/sroot/.ssh/known_hosts:2 debug3: load_hostkeys_file: loaded 1 keys from 165.227.198.59 debug1: load_hostkeys: fopen /home/sroot/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-...@openssh.com, using HostkeyAlgorithms verbatim debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: sntrup761x25519-sha...@openssh.com,curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-n
Re: Mozilla VPN
On Fri, Dec 8, 2023, 16:12 murph nj wrote: > I've decided to try a new VPN provider, and figured I'd give Mozilla's > offering a go. > > They have a client for Ubuntu, but nothing for Fedora. > > I tried installing using the instuctions from this website: > > > https://blog.radwell.codes/2021/12/install-mozilla-vpn-rpm-from-binary-on-fedora/ > > Seemed like a solid way to go about it from the Mozilla github pages, > but the end result installs but only gives a blank window when run > from the GUI. There is a command line interface, but none of what I > tried worked, although I'm still making attempts. Sorry to hear it doesn't work. If all fails, I've used VPN Unlimited from Ukrainians at Keepsolid and it has worked flawlessly, on Ubuntu and Debian. It has the bonus that a percentage of the proceeds goes to the Ukraine military to defend themselves against the Russian invasion. Plus, it's lifetime plan is truly lifetime. I paid six years ago and got myself a new lifetime license this year just to have around in case of need of additional slots. Linux client (deb only sorry) https://www.vpnunlimited.com/downloads/linux Not sure about how the deb to rpm conversion with alien would work /// Use this link for a discount P0QIFI2yhLGnVAsdyf5P To apply the gifted promo code: 1. Log in to the KeepSolid User Office. 2. Press the Manage button on the VPN Unlimited card. 3. Go to the Pricing menu. 4. Choose the desired subscription plan. 5. Copy the promo code. 6. Press Bonus and paste the gifted code. /// Just my $0.02 FC -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: libvirt / qemu / kvm bridged network
On 12/12/23 20:03, Sbob wrote: Hi; I'm running Fedora 39, I have installed qemu / libvirt / kvm I have found many guides on setting up bridged networking but none have worked. Can someone point me to a proper guide? Thanks in advance Setting up bridged networking is nowhere near as simple as it was in older versions of Linux. I've just about given up doing it from the command line. I install cockpit, start the cockpit.socket service, connect to cockpit on port 9090, go to Networking, add a bridge, tell the bridge which interface to add, and it Just Works(TM). Thomas -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 6.6.x kernels do not boot successfully
On Wed, Dec 13, 2023 at 04:48:16PM -, old sixpack13 wrote: > I guess reinstalling the problematic kernel might help > sudo dnf reinstall kernel-... I forgot to mention that I had already tried this with "dnf remove" and "dnf install", but to no effect. The kernel 6.6.4-200 is broken in some way, and I'm eagerly awaiting the next update. -- Mit freundlichen Grüßen Toni Andjelkovic http://toni.sdf-eu.org/ mailto:t...@sdf-eu.org -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
