search for: secrets

...0 */ /* Per-handle data. */ @@ -110,6 +129,8 @@ struct backend_libvirt_data { char name[DOMAIN_NAME_LEN]; /* random name */ bool is_kvm; /* false = qemu, true = kvm (from capabilities)*/ unsigned long qemu_version; /* qemu version (from libvirt) */ + struct secret *secrets; /* list of secrets */ + size_t nr_secrets; }; /* Parameters passed to construct_libvirt_xml and subfunctions. We @@ -130,6 +151,9 @@ struct libvirt_xml_params { }; static int parse_capabilities (guestfs_h *g, const char *capabilities_xml, struct backend_libvirt_data *data); +static...

Since v1: - Base64 decode the Ceph secret before passing it to libvirt. - Don't call virSecretFree (NULL) [libvirt bug?] - Small cleanups.

...to work out what > is the matter with it, and perhaps why it is in that situation. Hmm... I have no lslocks on FreeBSD; will lsof do? In case, here's an excerpt: > samba 72462 root txt VREG 4,1302659313 430080 32007 /usr/jails/dc/var/db/samba4/private/secrets.tdb > samba 72462 root 46u VREG 4,1302659313 430080 32007 /usr/jails/dc/var/db/samba4/private/secrets.tdb > smbd 72466 root txt VREG 4,1302659313 430080 32007 /usr/jails/dc/var/db/samba4/private/secrets.tdb > smbd 72...

I know there is the command "wbinfo -t". But when it says that "could not check secret", how do I know it's the secret is bad, or something else wrong, like winbind went crazy maybe? Also, sometimes I saw problems like "wbinfo -t" just says "secret is bad", when all the daemons were running. It sure was good at some point before. So my

...fset=8, ltype=3, flags=TDB_LOCK_WAIT) at ../../common/lock.c:390 #6 0x0000000800831808 in _tdb_transaction_start (tdb=0x80161f000, lockflags=TDB_LOCK_WAIT) at ../../common/transaction.c:490 #7 0x000000000040188b in backup_tdb ( old_name=0x7fffffffddd6 "/var/db/samba4/private/secrets.ldb", new_name=0x80161c000 "/var/db/samba4/private/secrets.ldb.copy.tdb", hash_size=<optimized out>, nolock=<optimized out>, readonly=<optimized out>) at ../../tools/tdbbackup.c:157 #8 0x0000000000401528 in main (argc=<optimized out>, argv=0x7...

Hey, guys I've been working on whether libvirt supports encrypted snapshots,Here are my versions of libvirt and qemu [root@xx ~]# libvirtd -V libvirtd (libvirt) 4.5.0 [root@xx ~]# qemu-img -V qemu-img version 2.12.0 (qemu-kvm-ev-2.12.0-33.1.el7_7.4) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers 1. assign $MYSECRET to libvirt secret using the secret-define and

...t to protect_from_forgery, and the number is different from the number passed to the :secret on config.action_controller.session[:secret]. What I would like to know is, if I''m setting the secret in config.action_controller.session, do I need to pass it to protect_from_forgery? Or are they secrets of different nature? Thanks, Marcelo. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.o...

...6]: active: false key offset: 1552384 [7]: active: false key offset: 1810432 payload offset: 2068480 master key iters: 300073 corrupt: false # qemu-img check -U --object secret,id=sec_1,file=/etc/libvirt/secrets/f52a81b2-424e-490c-823d-6bd4235bc572.base64,format=base64 --image-opts encrypt.format=luks,encrypt.key-secret=sec_1,file.filename=first-snapshot.qcow2 --object secret,id=sec_2,file=/etc/libvirt/secrets/f981dd17-143f-45bc-88e6-222222222222.base64,format=base64 qemu-img: Could not open 'encrypt.f...

I would like to suggest a feature that I believe would help out one usability aspect of rysnc. The patch I am suggesting will allow the rysnc module to return 1 of multiple secrets from the password file, essentially allowing you to check ANY user's (whom belong to a team) secret to see if it matches. For example: For 2 users (user1 and user2) belonging to team1, it would check all users passwords when they authenticates to their team share - User1 - password ...

I'm trying to understand how to properly setup the /etc/rsyncd.conf file to run an rsync daemon with a secrets file specified in a module - the rsync.conf manpage does not spell it out clearly enough. Rsync server is rsync-2.5.6. If this is my /etc/rsyncd.conf file: ------------------------------------ log file = /var/log/rsync uid = root gid = root [test] uid = rsync1 gid = rsync1...

Read also the secrets associated to disks (<secret> tag within <auth>), so qemu can properly open them later on. --- src/libvirt-domain.c | 130 +++++++++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 122 insertions(+), 8 deletions(-) diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c ind...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We're power failing a unit before it goes into production, and we've noticed that every time we fail it during a data transfer, smbd loses the domain connection. I've traced it down to the secrets.tdb file. After a power failure, tdbdump secrets.tdb says: { key = "SECRETS/SID/IN28C29E" data = "\01\04\00\00\00\00\00\05\15\00\00\00\D4r\9A\B6Sd\A3N\0A5\D7\DE\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00...

Hi, I recently did a complete upgrade and reinstall of one of our Samba servers. No problem, I backed up all the data, the Samba configuration files, and the secrets.tdb. Just compiled 3.0.8 on the new server (which has the same hostname), copied the smb.conf to /usr/local/samba/lib and copied th secrets.tdb to /usr/local/samba/private. Started Samba, did 'net getlocalsid' and it reports a different SID than my old server had. Just to be sure tha...

...l snapshot (Yeah!). However, should the VM die or be powered off, it is now longer possible to start the domain or at least recover the data: Could not open backing file: No secret with id 'scsi0-0-0-0-secret0' I guess this problems happens with any disk type that is accessed with object secrets, which is why I would consider this a bug. The question is, should/can this be fixed in libvirt or qemu? I think libvirt should create the snapshot file with the object secret stored in a persistent file (and reference this file in the backing file definition) Best regards, Markus

hi friend need ur help in dial plan, i want to allow exten 2000 to 2005 can make call outside and exten 2006 to 2010 can not make call outside. heres my dial plan. ? sip.conf ? [general] port = 5060 bindaddr = 0.0.0.0 context = others [2000] type=friend context=outside secret=1234 host=dynamic [2001] type=friend context=outside secret=1234 host=dynamic [2002] type=friend context=outside

I have setup a Rysnc server in Mandrake 9.1 When I add a auth user into my Rsync.conf and rsync.secrets, it do not work, everytime it shows [root@html]# rsync chris@mandrake82::XXXXX/.html/. / Password: @ERROR: auth failed on module XXXXX rsync: connection unexpectedly closed (89 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) This is my rsync's confi...

On Fri, 30 Dec 2016 13:54:42 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2016-12-30 um 13:20 schrieb L.P.H. van Belle via samba: > > And in addition to Rowlands comments.. > > > > Correct you hosts file to > > /etc/hosts > > 127.0.0.1 localhost > > # The following lines are desirable for IPv6 capable

...no changes in smb.conf by default. > > kerberos method = system keytab > > assumes the system default ( /etc/krb5.keytab ) > > Sorry, but no it doesn't ;-), the 'system keytab' is by default in memory. Ok, but then, with the setting, `kerberos method = secrets and keytab` it's only more confusing. A small re-cap. secrets only - use only the secrets.tdb for ticket verification (default) - this is clear how its used. system keytab - use only the system keytab for ticket verification - this description here might be better off with something like...

On Wed, Apr 15, 2020 at 10:53:05 +0800, 18781374080 wrote: > > > > Hey, guys > > I've been working on whether libvirt supports encrypted snapshots,Here are my versions of libvirt and qemu > > [root@xx ~]# libvirtd -V > > libvirtd (libvirt) 4.5.0 This is too-old encrypted backing files work starting from libvirt-5.10 (but I strongly suggest using at least

...ly. By shared, I mean that the ./private directory is on a shared filesystem (via Veritas clustered filesystem). Each server is running its own independent binaries and ./var/locks. But only one server is running nmbd at time. The other one is always ready to start nmbd upon nmbd failure. If secrets.tdb is shared, would this really only be involved with nmbd/smbd during domain membership . BTW - These samba servers are domain members only. Thanks, Bill Pappas - System Integration Engineer - SAN St. Jude Children's Research Hospital 332 North Lauderdale Memphis, TN 38105 Dann...