search for: risky

Hi there, Domaincontroller name: risky.home.schinz.de dig dig @risky -tANY risky.home.schinz.de. returns: ;; ANSWER SECTION: risky.home.schinz.de. 900 IN A 10.0.180.254 risky.home.schinz.de. 900 IN AAAA ::1 I have a strange behavior in my network. It's only concerning DNS, but maybe someone can help me....

Hai, Sorry for the late reply, but yes, this is a risky move. Did you make sure this the DOMAIN SID's are exact the same between old and new servers? This: rsync -av --progress --xattrs --rsh=ssh Does not copy the (windows) acl's. Look at https://wiki.samba.org/index.php/Bidirectional_Rsync/Unison_based_SysVol_replication_workaround Howt...

On Jan 5, 2010, at 1:38 PM, David Greene wrote: > I don't think there's a flag that says "don't do anything risky, > ever." "Don't do anything risky with floating-point" is the default mode. If you're aware of any unsafe floating-point optimizations being done by default, please file a bug. > For example, a gfortran-fronted LLVM should have a way to always respect > ordering i...

...MU gives > GIOVA->GPA mapping, and qemu vhost code will translate GPA to HVA then pass > GIOVA->HVA to vhost. It looks no difference to me. > > Thanks The difference is in security not in performance. Getting a bad HVA corrupts QEMU memory and it might be guest controlled. Very risky. If translations to HVA are done in a single place through a single table it's safer as there's a single risky place. -- MST

...MU gives > GIOVA->GPA mapping, and qemu vhost code will translate GPA to HVA then pass > GIOVA->HVA to vhost. It looks no difference to me. > > Thanks The difference is in security not in performance. Getting a bad HVA corrupts QEMU memory and it might be guest controlled. Very risky. If translations to HVA are done in a single place through a single table it's safer as there's a single risky place. -- MST

OK, now i've to start to move the big part of my users from my old NT-like domains to my new AD domain. I've setup roaming profile in the new domain following the wiki (https://wiki.samba.org/index.php/Roaming_Windows_User_Profiles, 'using windows ACL') and for new profiles works like a charm. But i've tried to move/copy old profile to the new domain, and seems work, with

Hello Everyone, We have centos6 server. And we are planning to upgrade it to Centos7.And GRUB 2 needs a new bios grub partition. Creating a new partition is too much risky. I am wondering if it is possible to replace Grub2 with Grub legacy on Centos7 machine? Thanks!! Sachin

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the

Just sharing an experience with you all -- hopefully you take better precautions than I do. :-) I have a few sites built with Rails 0.8.3 that were ugpraded to 1.0. The newer sites are on edge rails. So when I heard 1.1 had come out, I unfroze my new apps, and installed the new gem for Rails 1.1. The sites that was operating on edge rails worked just fine. However, the sites that were working

Hi, I have a daemon process which is changings things in the system only the superuser should be allowed to change. Lets call it "riskyd". Users use a frontend on the same machine (lets call it "risky"). risky is a SUID program which talks to riskyd by binding to a privileged port, then connecting to riskyd on localhost. riskyd cheks that the connection is coming from localhost and from a privileged port to make...

On Tuesday 05 January 2010 15:57, Dan Gohman wrote: > On Jan 5, 2010, at 1:38 PM, David Greene wrote: > > I don't think there's a flag that says "don't do anything risky, > > ever." > > "Don't do anything risky with floating-point" is the default mode. If > you're aware of any unsafe floating-point optimizations being done by > default, please file a bug. Ok. It seems that something is causing a problem if Bullet is failin...

...ck pertinent to RHEL 5; as XFS isn't supported under Red Hat Enterprise Linux these items are an attempt to match XFS performance with ext3. These items were culled from a number of sources. Will they be effective for achieving the performance goals? Is the risk assessment correct? Are any too risky for consideration? Has anything been left out? Thanks. ext3 Performance Tuning This document contains notes about optimizing ext3 filesystems for storage nodes on Linux clusters used for scientific research. Each of the goals and assumptions has been assigned an identifier in square brackets...

Hi all. I have never implemented online payment and it''s the only thing that keeps me from accepting a project for a UK based client. (I must reply quickly!) While I can afford spending an extra week - or 2 - to learn/try/tune the payment system, I must be sure to succeed before I accept the contract. If you''ve already been through that path, any hints, links and/or

I'm dying to use the 1.0 capability to use more than one mysql user pasword database. However, I'm too chicken to use 1.0-test in a production environment. Does anyone know if there is a planned release date for 1.0? Or can anyone say how risky it is to use 1.0-test?

...g address 5, error -110 I am looking at xl dmesg in Dom0 where there are some messages relating to the PCI usb: [VT-D] It's disallowed to assign 0000:00:1a.0 with shared RMRR at 7b800000 for Dom6. (XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 to dom6 failed (-1) (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 for Dom7. (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 for Dom8. (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 for Dom9. (XEN) [VT-D] It's risky to assign 0000:00:1a.0 wit...

...re general question of: enable CR on a >> production >> server, yes or no? > > Not on production. Only for testing. I'm not sure. Running production environments without CR enabled means you're running without current security updates for quite some time. Seems a bad and risky idea to me. Regards, Simon

On 8/5/20 7:48 AM, Richard W.M. Jones wrote: > See comment in code and > https://www.redhat.com/archives/libguestfs/2020-August/msg00023.html > --- > plugins/vddk/vddk.c | 32 ++++++++++++++++++++++++++++---- > 1 file changed, 28 insertions(+), 4 deletions(-) I'll have to trust your testing, but code-wise, this looks safe. -- Eric Blake, Principal Software Engineer Red

I noticed that the apache rpm httpd-2.2.3-11.el5_1.centos.3.src.rpm has a bug in mod_expires. https://issues.apache.org/bugzilla/show_bug.cgi?id=39774 Please forgive a dumb question: how risky would using a Fedora httpd RPM be on a CentOS5 install? Jed

...reateCall(my_function, constPtr); The resulting IR call looks like this: call void @nativeFunc(i32* inttoptr (i64 146876396 to i32*)) I'm just wondering if there is a better way to approach this. Casting a pointer to a signed integer and back to a pointer looks both hack-ish, and potentially risky (what happens if the address falls in the negative range of the signed integer?). Unfortunately, I couldn't call a pointer constant type in the LLVM doxygen documentation. Thank you for your time, - Maxime -- View this message in context: http://www.nabble.com/Creating-Pointer-Constants-tp22...

...17: undefined reference to > WARN_ON_ONCE. This patch adds the bug.h header to idr.h to solve the > issue. Thanks; I sent this same patch out yesterday. Unfortunately, you didn't cc the author of this breakage, Masahiro Yamada. I want to highlight that these kinds of header cleanups are risky, and very low reward. I really don't want to see patches going all over the tree randomly touching header files. If we've got a real problem to solve, then sure. But I want to see a strong justification for any more header file cleanups.