similar to: safety vulnerability in tablet computer

The matter of EUFI?s Secure Boot vs Legacy Boot has been briefly discussed a couple of days ago. I would ask the List opinion concerning our case. A bit of the history. We?ve been in the research of malicious hypervisor threat since 2013. We finally developed publicly available HyperCatcher freeware. It runs on specially built Ubuntu 14.4. We tried CentOS 6/7 as well. The OS was compiled to

Hello, I ran today update of my CentOS 6.9 running on Dell T105 (AMD OPTERON) and httpd failed to start. Any idea what could cause that? I never had a problem after CentOS 6.x update. Web server runs since March 2017. I do updates usually once in a week. Thank you Mikhail Utin

> Date: Tuesday, January 23, 2018 00:55:28 +0000 > From: Mikhail Utin <mikhailutin at hotmail.com> > > Hello, > > I ran today update of my CentOS 6.9 running on Dell T105 (AMD > OPTERON) and httpd failed to start. Any idea what could cause that? > I never had a problem after CentOS 6.x update. Web server runs > since March 2017. I do updates usually once in a

Hi all, Tl;dr: Virt-Lightning uses libvirt, cloud-init and libguestfs to allow anyone to quickly start new VM. Very much like a container CLI interface, but locally. -> https://github.com/virt-lightning/virt-lightning To validate my Ansible roles, I was looking for a way to quickly start and stop my test environments. I was looking for an experience similar to what we have with the

On 3/26/19 11:27 PM, Gonéri Le Bouder wrote: > Hi all, > > Tl;dr: Virt-Lightning uses libvirt, cloud-init and libguestfs to allow > anyone to quickly start new VM. Very much like a container CLI interface, > but locally. > > -> https://github.com/virt-lightning/virt-lightning > > To validate my Ansible roles, I was looking for a way to quickly start > and stop

https://bugs.freedesktop.org/show_bug.cgi?id=27928 Summary: Nouveau / Mesa sometimes gets libraries overwritten Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

Just released by the CPSC on their recalls mailing list; please forward to any venues where you feel operators or resellers of the SoundStation might be, with this preface included. My 2W had a battery with the part code 1520-07804-002; its date code was GP0806, and therefore predates the recall period. Cheers, -- jra ----- Begin forwarded message ----- This message consists of the following:

I would prefer simple text in tech and security related news but you are right - they are HTML formatted. I think it is pure marketing thing. people dump other stuff to remind you who they are and for a sort of entertaining us. The same story is in OS desktop GUI including Linux. I use CentOS 6 and 7 and still do not like 7. Not to mention in the morning Win 10 with all its crap included.

Synopsis: Prior to the 2.6.4pre versions, issuing 'rsync rsync://host/module/' behaved effectively as 'ls -l'. I've toyed with various options in an attempt to get an 'ls -l' style output, but to no avail. As I have a small handful of scripts that rely on this no-longer-functioning functionality, this could be considered a Bad Thing(TM). Following is an example of

Why do you need UEFI? It does not add to security "a lot" but was designed to block booting software like a "hypervisor". I used my Dell notebooks to test our hypervisor identification software (HyperCatcher if you are interested) which is bootable image. However, I was unable to boot it until I disabled UEFI. As I understand it, it will block anything from booting excepting

when installing dotnet 2.0 the install crashes ive tried clearing winetricks cache but that doesn't seem to work here's the errors im getting any help is appreciated Code: lithium at lithium-laptop:~$ ./winetricks ------------------------------------------------------ Instaling .net 2.0 runtime. Can take several minutes. See http://wiki.winehq.org/MicrosoftDotNet for tips.

3.0.0pre2: non-recursive remote listing breakage Looks like pre1's fix broke something else. I noticed this when listing module/directory contents on servers known to be running versions 2.5.7 & 2.6.3. Not having (full) access to them, I replicated the errors using 2 machines on my home lan. # the machines lithium.elements.lan: the client. rsync 3.0.0pre2 for all tests.

Package: xen-utils-4.1 Version: 4.1.0-2 Severity: important I had a working Xen server with 4.0 hypervisor and 2.6.32 kernels. After updating (and booting up) 4.1 hypervisor with 2.6.38 kernel, any attempt to create a VM failed (also the ones saved from previous book don't come up either). If I try to use xl : # xl create /etc/xen/lithium.vm.carpediem.sh.cfg Parsing config file

The page to see this if you cannot see HTML on e-mail or just want to look at all of it is. Sometimes, if it is reasonable, people would prefer not to search around to web sites so I am posting highlights in HTML as well as giving the link. Could someone buy me a DMC-800 :-). Why I always look for components and off brands that focus on engineering rather than marketing is that they are not in the

I had noticed the --link-by-hash patch a short while back & decided it was time to experiment with it. Sadly, its behaviour is considerabely different from what I expected - to the point that I find it unusable in its current form. I had hoped to use it both for my rotating backups & for my (unofficial) slackware mirror. For the test itself, I did the following: - created 3 directories in

Hi all, thank you for your patience. I am dealing with a large dataset detailing patients and medications Medications are hard to code, as they are (usually) meaningless unless matched with doses. I have a dataframe with vectors (Drug1, Drug2..... Drug 16) and individual patients are represented by rows. The vectors are actually factors, with 100s of possible levels (all the drugs the patient

This makes the IDT unconditionally read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks. It has an added benefit of also not leaking (via the "sidt" instruction) the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> ---

This makes the IDT unconditionally read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks. It has an added benefit of also not leaking (via the "sidt" instruction) the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> ---

Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> --- v2: - clarify commit

Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> --- v2: - clarify commit