similar to: SYSLINUX PXE LOCALBOOT Bitlockers

Displaying 20 results from an estimated 900 matches similar to: "SYSLINUX PXE LOCALBOOT Bitlockers"

2014 Apr 28
2
SYSLINUX PXE LOCALBOOT Bitlockers
Label is OS and I believe there are all booting MBR. Is there a way to clear the memory then continue loading ? or rebooting the machine from the menu. I have tried that reboot.c32 and cannot get it to reboot the machine. Matt -----Original Message----- From: Gene Cumm [mailto:gene.cumm at gmail.com] Sent: Monday, April 28, 2014 1:04 PM To: Taylor Jr, Matthew [U.S. Computer Corp] Cc:
2014 Apr 29
2
SYSLINUX PXE LOCALBOOT Bitlockers
Any deviation from the expected boot process will prevent BitLocker from accessing the volume key in the TPM. One reason this behavior exists is to prevent malicious code from being loaded (such as via booting first to CD / USB / PXE, loading malware, and then continuing to boot to Windows). So what's happening here is the deviation from firmware -> PXE -> HDD is detected and the volume
2014 May 05
1
SYSLINUX PXE LOCALBOOT Bitlockers
That's a great question, actually, I should have remembered to mention that! You can control what factors are used for the TPM's integrity check to release the bitlocker key on boot. Depending on whether your on a BIOS or EFI machine, there are slight differences, but definitely controllable by group policy. http://technet.microsoft.com/en-us/library/ee706521(v=ws.10).aspx#BKMK_depopt3 I
2014 Apr 29
1
Syslinux 64 EFI boot WIM
Am 29.04.2014 07:59, schrieb H. Peter Anvin: > On 04/23/2014 03:37 PM, Romine, Bryan wrote: >> Is it possible to boot a Windows image file (.wim) directly from >> Syslinux 6.xx EFI? If not, is this a feature that will ever be added? >> This may be related to bug #17: >> http://bugzilla.syslinux.org/show_bug.cgi?id=17 >> > It probably requires someone to step up
2014 May 01
0
SYSLINUX PXE LOCALBOOT Bitlockers
do you mean it cant be circumvented from the perspective of syslinux or TPM? Sadly firmware exploits are rampant. Core Security has good research on this as phrack... SMM can be gotten to by far too much. Tho if you are targeted by that skill level then going to ic3 might be good idea. -------- Original message -------- From: Ian Bannerman <ian at internals.io> Date:04/29/2014 2:43 PM
2014 Apr 23
2
Syslinux 64 EFI boot WIM
Is it possible to boot a Windows image file (.wim) directly from Syslinux 6.xx EFI? If not, is this a feature that will ever be added? This may be related to bug #17: http://bugzilla.syslinux.org/show_bug.cgi?id=17 Bryan Romine [Description: Description: Description: green] Sr. Software Engineer | AMD Validation 7171 Southwest Parkway, Austin, TX 78735 USA O +(1) 512-602-2042 [Description:
2014 Apr 28
0
SYSLINUX PXE LOCALBOOT Bitlockers
On Mon, Apr 28, 2014 at 4:06 PM, Taylor Jr, Matthew [U.S. Computer Corp] <Matthew.Taylor at chevron.com> wrote: > Label is OS and I believe there are all booting MBR. Is there a way to clear the memory then continue loading ? or rebooting the machine from the menu. No, the entire LABEL stanza including its LOCALBOOT/COM32/KERNEL and APPEND lines as applicable. -- -Gene A: Because it
2014 Apr 28
0
SYSLINUX PXE LOCALBOOT Bitlockers
On Mon, Apr 28, 2014 at 3:37 PM, Taylor Jr, Matthew [U.S. Computer Corp] <Matthew.Taylor at chevron.com> wrote: > Hello; > > I use Bitlocker on my machines and I notice that when I am in my PXE Menu and I select "Boot to Local Hard Drive" it continues on then bitlockers. I am assuming that the syslinux is still in memory, bitlocker is being triggered because of the change.
2014 May 02
0
SYSLINUX PXE LOCALBOOT Bitlockers
On Tue, Apr 29, 2014 at 2:43 PM, Ian Bannerman <ian at internals.io> wrote: > Any deviation from the expected boot process will prevent BitLocker from > accessing the volume key in the TPM. One reason this behavior exists is to > prevent malicious code from being loaded (such as via booting first to CD / > USB / PXE, loading malware, and then continuing to boot to Windows). So
2015 Dec 23
2
samba4 windows 10 pro bitlocker key managment
hi did anyone successfully implemented bitlocker key management in samba4 ad? searching web i can find one hit on this http://kidcartouche.blogspot.com/2013/03/bitlocker-drive-encryption-and-samba4.html i'm on 4.3.3. do i still need to import the bitlocker schema? any info on the subject is appreciated. thanks -- View this message in context:
2024 Mar 22
2
Raise Domain Level, Forest Level and Schema for Bitlocker integration
Not sure what Bitlocker integration you are referring to. Saving bitlocker recovery keys does work for me with schema version 47. Regards, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Paul Littlefield via samba Gesendet: Mittwoch, 20. M?rz 2024 18:14 An: samba at lists.samba.org Betreff: Re: [Samba] Raise Domain Level, Forest Level
2024 Mar 24
1
Raise Domain Level, Forest Level and Schema for Bitlocker integration
On 22/03/2024 09:20, Joachim Lindenberg via samba wrote: > Not sure what Bitlocker integration you are referring to. Saving > bitlocker recovery keys does work for me with schema version 47. > Regards, Joachim We have tried a few times to use our existing schema version 47 and it's coming up with this error:- https://www.itdroplets.com/bitlocker-error-0x80005000/ A screenshot is
2020 Oct 09
3
Re: [PATCH v3 0/8] Windows BitLocker support.
On Fri, Oct 09, 2020 at 05:02:57PM +0200, Martin Kletzander wrote: > Basically what I did was create a small disk, create one partition > over the whole disk, then cryptsetup luksFormat the partition, open > it and format it with a filesystem (without any LVM). That is one > of the things you were adding support for, but it is not limited to > Windows Bitlocker setup, it can just
2020 Sep 07
5
[PATCH common v2 0/4] Windows BitLocker support.
For links to the original patch series, see: https://bugzilla.redhat.com/show_bug.cgi?id=1808977#c8 The original feedback was that ignoring errors from guestfs_luks_uuid would ignore legitimate errors from non-BitLocker disks, so I have modified this series so that errors are only ignored in the BitLocker case. As noted in the 4th patch there is no actual error in the BitLocker case, cryptsetup
2024 Mar 20
3
Raise Domain Level, Forest Level and Schema for Bitlocker integration
On 18/03/2024 15:44, Paul Littlefield via samba wrote: > > I would like to add BitLocker integration to the three DCs we have running 4.15.13 on Ubuntu 22.04 LTS. > > The DC has been around a while and is currently on Schema version 47 and Domain level 2008_R2. > > Can I confirm that the procedure to upgrade the three DCs is as follows:- > > 1) backup > 2) upgrade
2019 Jul 17
2
Bitlocker
>yes we installed this. And see nothing there. Do you have this running? Yes, I do. You can tell it is installed properly by looking at the additional tab "Bitlocker Recovery" on computers? properties. Joachim
2020 Aug 07
3
BitLocker integration with AD
Hi, What do I need to get BitLocker integration with AD on Samba 4? Paul
2024 Mar 20
1
Raise Domain Level, Forest Level and Schema for Bitlocker integration
On 20-03-2024 18:14, Paul Littlefield via samba wrote: > On 18/03/2024 15:44, Paul Littlefield via samba wrote: >> >> I would like to add BitLocker integration to the three DCs we have >> running 4.15.13 on Ubuntu 22.04 LTS. >> >> The DC has been around a while and is currently on Schema version 47 >> and Domain level 2008_R2. >> >> Can I
2020 Oct 07
2
Re: [PATCH common v2 4/4] options: Ignore errors from guestfs_luks_uuid.
On Tue, Oct 06, 2020 at 03:06:54PM +0100, Richard W.M. Jones wrote: >On Tue, Oct 06, 2020 at 03:25:20PM +0200, Martin Kletzander wrote: >> On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote: >> >For BitLocker disks cryptsetup does not (yet? ever?) support reading >> >UUIDs and this function will fail. This does not matter here so just >> >ignore
2020 Mar 30
6
[PATCH common 0/4] options: Support Windows BitLocker (RHBZ#1808977).
Support transparent decryption/inspection of Windows guests encrypted with BitLocker encryption. This won't make much sense without the associated libguestfs patches which I will post momentarily. (Submodules, ho hum) Rich.