ssh forced command in syslog?
by Alex
Hi,
I'm trying to use the "command=" ability with ssh and rsync to restrict the
commands that can be run with a passwordless ssh key. The problem is that I
can't figure out the exact rsync that's being executed on the remote side.
I recall in the past being able to somehow log this information to syslog,
but now I can't remember and can't find it.
Does anyone know how to do this?
I recall it being related to LogLevel and SyslogFacility, but I must be
missing something.
The rsync command I'm running on the local side is:
$ rsync -a -e 'ssh -i /path/to/private-key' /path/to/local/files
host:/path/to/dest/
The contents of my /root/.ssh/authorized_keys for the command I want to
execute is something like this:
command="/usr/bin/rsync --server --sender -logDtprze.iLs --numeric-ids .
/",no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAABAQC....
I want to upgrade this to instead use an ed25519 key and define a more
specific path.
I've also tried the SSH_ORIGINAL_COMMAND environment variable, but it
doesn't seem to be set.
Thanks,
Alex
4 months, 4 weeks
might be off topic -- using digitalocean to test
by bruce
Hi.
Does anyone have digitalocean (DO) experience creating
droplets/snapshots/cloning etc.
I'm thinking of doing tests with the platform. Wanted to ask specific questions.
The questions have more to do with actual steps to "clone" a given
"droplet" than Fedora itself.
thanks
4 months, 4 weeks
Re: GPT/MBR what does fedora use for raspberry pi 39
by olivares33561
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, December 15th, 2023 at 1:45 PM, Barry Scott <barry(a)barrys-emacs.org> wrote:
> > On 15 Dec 2023, at 18:11, olivares33561 <olivares33561(a)protonmail.com> wrote:
> >
> > Trying to clone the fedora 39 on raspberry pi 4 sdcard using clonezilla and informing the users that the machine that does not boot 6.6.X fedora kernels does boot a 6.6.5 debian kernel from usb. So it may be a bug. but cause is unknown. That is what I was trying to do.
>
>
> Given that Rpi4 works with the 6.6.6 kernel I wonder is the cloning is giving you a copy that cannot be booted?
>
> Barry
I did not clone the Fedora installation till today. I had tried to boot the kernels 6.6.X series 6.6.3/6.6.4 and now 6.6.6-200* on a sdd I had on the computer. When I noticed that clonezilla recognized the nvme devices, I decided to clone it and successfully booted with 6.5.12-200 kernel. Tried 6.6.6 on it and it did not work.
Best Regards,
Antonio
5 months
6.6.x kernels do not boot successfully
by olivares33561
Dear kind Fedora users,
When there was a kernel upgrade from 6.5.12 to 6.6.2, the 6.6.2-*fc39 kernel, the 6.6.3*, and 6.6.4*.fc39 kernel fail to boot. Machine just hangs. It used to just work great. Now the machine hangs and I have to install updates and exclude the kernels with sudo dnf upgrade --exclude=kernel* .
I have successfully run the 6.6.x Fedora kernels on a raspberry pi 4. So I know those kernels work, except on that machine. If I install the new kernels, boot hangs indefinitely with no response. I will like to find out how I can check what is going on and successfully boot a newer 6.6.x kernels. I can send information for machine. It is a Dell XPS 8950 or something like that.
Thank you in advance,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
5 months
GPT/MBR what does fedora use for raspberry pi 39
by olivares33561
Dear fellow Fedora users,
I am trying to back up/clone/save an image of a raspberry pi 4 machine running Fedora 39. It reports an error that GPT/MBR mismatch :
This disk contains mismatched GPT and MBR partion: /dev/mmcblk0
I am doubting what to do, as I have tried to clone Fedora raspberry pi installations and have not succeeded. How can I tell what type it is ?
Best Regards,
Antonio
BTW, a 6.6.x kernel did successfully boot on the machine, but the message was too large and needs moderator approval. I can attach small bits, but it reports an nvme( which is the windows install which I have not used ).
[ 72.856418] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1f.3/sound/card0/input26
[ 73.795584] nvme0n1: p1 p2 p3 p4 p5 p6
[ 74.225843] nvme0n1: p1 p2 p3 p4 p5 p6
[ 78.102348] nvme0n1: p1 p2 p3 p4 p5 p6
[ 81.977078] nvme0n1: p1 p2 p3 p4 p5 p6
[ 85.862016] nvme0n1: p1 p2 p3 p4 p5 p6
[ 93.610173] nvme0n1: p1 p2 p3 p4 p5 p6
[ 97.485178] nvme0n1: p1 p2 p3 p4 p5 p6
[ 101.363060] nvme0n1: p1 p2 p3 p4 p5 p6
[ 102.349958] mmc0: new ultra high speed SDR50 SDHC card at address 5048
[ 102.383908] mmcblk0: mmc0:5048 SD32G 28.9 GiB
[ 102.385752] mmcblk0: p1 p2
[ 105.421101] sda: sda1 sda2 sda3
[ 106.453006] nvme0n1: p1 p2 p3 p4 p5 p6
[ 106.798286] nvme0n1: p1 p2 p3 p4 p5 p6
[ 110.428732] nvme0n1: p1 p2 p3 p4 p5 p6
[ 110.831566] nvme0n1: p1 p2 p3 p4 p5 p6
[ 114.480372] nvme0n1: p1 p2 p3 p4 p5 p6
[ 114.619552] sda: sda1 sda2 sda3
[ 114.874872] nvme0n1: p1 p2 p3 p4 p5 p6
[ 116.958448] mmcblk0: p1 p2
[ 121.631645] nvme0n1: p1 p2 p3 p4 p5 p6
[ 122.374100] nvme0n1: p1 p2 p3 p4 p5 p6
[ 195.601879] sda: sda1 sda2 sda3
[ 195.984670] nvme0n1: p1 p2 p3 p4 p5 p6
[ 196.126568] mmcblk0: p1 p2
[ 197.070732] nvme0n1: p1 p2 p3 p4 p5 p6
[ 199.481898] nvme0n1: p1 p2 p3 p4 p5 p6
[ 201.930185] mmcblk0: p1 p2
[ 202.267950] nvme0n1: p1 p2 p3 p4 p5 p6
[ 202.425612] nvme0n1: p1 p2 p3 p4 p5 p6
[ 202.756384] sda: sda1 sda2 sda3
[ 241.331011] nvme0n1: p1 p2 p3 p4 p5 p6
[ 241.748101] sda: sda1 sda2 sda3
[ 242.968629] nvme0n1: p1 p2 p3 p4 p5 p6
[ 243.337205] sda: sda1 sda2 sda3
[ 246.438125] nvme0n1: p1 p2 p3 p4 p5 p6
[ 246.772420] nvme0n1: p1 p2 p3 p4 p5 p6
[ 247.139061] nvme0n1: p1 p2 p3 p4 p5 p6
[ 247.199095] nvme0n1: p1 p2 p3 p4 p5 p6
[ 247.706299] nvme0n1: p1 p2 p3 p4 p5 p6
[ 248.411458] sda: sda1 sda2 sda3
[ 300.775429] nvme0n1: p1 p2 p3 p4 p5 p6
[ 305.336285] nvme0n1: p1 p2 p3 p4 p5 p6
[ 306.141799] mmcblk0: p1 p2
[ 1171.059090] mmcblk0: p1 p2
[ 1171.228892] mmcblk0: p1 p2
[ 1173.098568] QNX4 filesystem 0.2.3 registered.
[ 1335.835452] EXT4-fs (mmcblk0p2): mounted filesystem b8316dab-786b-45e8-815c-3d4bbf198d98 r/w with ordered data mode. Quota mode: none.
user@debian:/media/mmcblk0p2/home/olivares/Downloads/kerTeX/Documents/mptmp$ uname -a
Linux debian 6.5.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.8-1 (2023-10-22) x86_64 GNU/Linux
user@debian:/media/mmcblk0p2/home/olivares/Downloads/kerTeX/Documents/mptmp$ exit
exit
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
5 months
libvirt / qemu / kvm bridged network
by Sbob
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
5 months
Mozilla VPN
by murph nj
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...
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.
This was both on a virtual machine running Fedora 39 desktop, as well
as my laptop running Kinoite (39 as well)
I can provide more information if anyone has an idea where to go with
this, just let me know.
Thanks,
--murph
5 months
ssh access sshKey/password
by bruce
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(a)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(a)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(a)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(a)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 0x04000000
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-v01(a)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-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms:
ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256(a)openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos:
chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm(a)openssh.com
debug2: ciphers stoc:
chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm(a)openssh.com
debug2: MACs ctos:
umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib(a)openssh.com,zlib
debug2: compression stoc: none,zlib(a)openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms:
sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
debug2: host key algorithms:
rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos:
chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm(a)openssh.com
debug2: ciphers stoc:
chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm(a)openssh.com
debug2: MACs ctos:
umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib(a)openssh.com
debug2: compression stoc: none,zlib(a)openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: sntrup761x25519-sha512(a)openssh.com
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305(a)openssh.com MAC:
<implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305(a)openssh.com MAC:
<implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519
SHA256:FSbkPEpUcP9WKaF8Wqzdq1HoBy9UB5Lg3G2KdvJNIiM
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
debug1: Host '165.227.198.59' is known and matches the ED25519 host key.
debug1: Found key in /home/sroot/.ssh/known_hosts:2
debug3: send packet: type 21
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug3: ssh_get_authentication_socket_path: path
'/tmp/ssh-0pg5Dmeqog/agent.41138'
debug2: get_agent_identities: ssh_agent_bind_hostkey: communication
with agent failed
debug1: get_agent_identities: ssh_fetch_identitylist: communication
with agent failed
debug1: Will attempt key: /home/sroot/.ssh/id_rsa
debug1: Will attempt key: /home/sroot/.ssh/id_ecdsa
debug1: Will attempt key: /home/sroot/.ssh/id_ecdsa_sk
debug1: Will attempt key: /home/sroot/.ssh/id_ed25519
debug1: Will attempt key: /home/sroot/.ssh/id_ed25519_sk
debug1: Will attempt key: /home/sroot/.ssh/id_xmss
debug1: Will attempt key: /home/sroot/.ssh/id_dsa
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info:
server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256(a)openssh.com,ssh-dss,ssh-rsa,rsa-sha2-256,rsa-sha2-512>
debug1: kex_input_ext_info: publickey-hostbound(a)openssh.com=<0>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/sroot/.ssh/id_rsa
debug3: no such identity: /home/sroot/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /home/sroot/.ssh/id_ecdsa
debug3: no such identity: /home/sroot/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/sroot/.ssh/id_ecdsa_sk
debug3: no such identity: /home/sroot/.ssh/id_ecdsa_sk: No such file
or directory
debug1: Trying private key: /home/sroot/.ssh/id_ed25519
debug3: no such identity: /home/sroot/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: /home/sroot/.ssh/id_ed25519_sk
debug3: no such identity: /home/sroot/.ssh/id_ed25519_sk: No such file
or directory
debug1: Trying private key: /home/sroot/.ssh/id_xmss
debug3: no such identity: /home/sroot/.ssh/id_xmss: No such file or directory
debug1: Trying private key: /home/sroot/.ssh/id_dsa
debug3: no such identity: /home/sroot/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
testu(a)165.227.198.59: Permission denied (publickey).
sroot@ubuntu-s-1vcpu-2gb-nyc1-01:~$
which doesn't implement a "password" check/process!!
in the test of the initial "testu(a)161.35.5.174"
.
.
debug1: Trying private key: /root/.ssh/id_dsa
debug3: no such identity: /root/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password <<<<<<<<<<<<<<<<<<< this happened!!
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
testu(a)161.35.5.174's password:
.
.
it appears that the
authmethod_lookup password
doesn't happen!!!!!!!
the issue is why!
so.. anyone have any clues as to what I can test/check?
or what I've screwed up!!
thanks
by the way..
If I log into the "working/initial" droplet the --161.35.5.174
and I attempt to ssh/access the "copied" droplet --165.227.198.59
I get the same errs...
testu(a)165.227.198.59: Permission denied (publickey).
5 months
Log file *detailed* content description
by Dave Close
So I spent the last 30 minutes or so trying to find a detailed
description of the content of /var/log/secure. Sure, I know the purpose
of the file and most of the messages are self-explanatory. But some
of the message content is not. I was surprised that multiple search
engines were unable to find anything beyond the obvious ("Keep
authentication logs for both successful ..."). Doesn't Fedora's
documentation anywhere describe this file in some detail?
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?
--
Dave Close, Compata, Irvine CA +1 714 434 7359
dave(a)compata.com dhclose(a)alumni.caltech.edu
"Politics have no relation to morals." -- Niccolo Machiavelli
5 months
Help converting VMWare Workstation VM to Qemu/KVM
by Sbob
All;
I have installed Quemu/KVM/libvirt and I have it working, I was able to
install a new Fedora VM using the ISO as the disk image.
Now I want to convert an existing VMWare workstation VM, here is the
file listing in the Directory for the VM I want to convert:
$ ls /data/vmware/Dev-Fedora
Dev-Fedora-0.scoreboard Dev-Fedora-s002.vmdk Dev-Fedora.vmsd
mksSandbox-2.log
Dev-Fedora-1.scoreboard Dev-Fedora-s003.vmdk Dev-Fedora.vmx
mksSandbox.log
Dev-Fedora-7.scoreboard Dev-Fedora-s004.vmdk Dev-Fedora.vmxf
vmware-0.log
Dev-Fedora-8.scoreboard Dev-Fedora-s005.vmdk Dev-Fedora.vmx.lck
vmware-1.log
Dev-Fedora-9.scoreboard Dev-Fedora-s006.vmdk mksSandbox
vmware-2.log
Dev-Fedora.nvram Dev-Fedora.scoreboard mksSandbox-0.log
vmware.log
Dev-Fedora-s001.vmdk Dev-Fedora.vmdk mksSandbox-1.log
I tried this:
1) use qemu-img convert to convert the Dev-Fedora.vmdk file:
# qemu-img convert -f vmdk -O qcow2 Dev-Fedora.vmdk Dev-Fedora.qcow2
this created the Dev-Fedora.qcow2 file
2) create a new VM with virt-manager and use the Dev-Fedora.qcow2 file
as the disk image via the 'Import existing disk image' option
3) I start the new VM and I get 'No bootable devices found'
Thanks in advance
5 months
