search for: bannerman

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this one -http://www.syslinu...

>What I reminder from it: > > The first "isohybrid" was in perl. > But that made perl a run-time dependency. > > A compiled version of "isohybrid" removed that > run-time dependency on perl. > > >What I think of it: > > The Perl variant of isohybrid should be removed > from the source tree. One advantage of the Perl one for me

Hi, Ian Bannerman: > I did not know the Perl version did not support the EFI/Mac changes. Comparing the help texts of http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.c and http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.in shows that the latter lacks:...

Question, Some Linux distributions I support show two approaches for pxe booting them. One uses memdisk to boot an ISO file. The other uses pxelinux to boot kernel and initrd a squashfs file. I'm unfamiliar with the impact to memory either approach has. Like, does using memdisk permanently squirrel away a chunk of memory for the ISO file that the OS will be unable to use? Is using initrd to

...lps, good luck!--Ian > Date: Fri, 2 May 2014 19:08:27 -0400 > From: gene.cumm at gmail.com > To: ian at internals.io > CC: syslinux at zytor.com; matthew.taylor at chevron.com > Subject: Re: [syslinux] 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 / > >...

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

>Although there are some "isohybrid.exe" around, there is no official support for them and they are also outdated. >The Syslinux mailing list already includes several emails about issues in the included isohybrid variants. I think that deleting either of them would be a mistake. At least users such as Ian might benefit from both being included. >Ideally, the Perl variant

On Thu, Mar 13, 2014 at 3:31 PM, Ian Bannerman <ian at internals.io> wrote: > Question, > > Some Linux distributions I support show two approaches for pxe booting them. One uses memdisk to boot an ISO file. The other uses pxelinux to boot kernel and initrd a squashfs file. > I'm unfamiliar with the impact to memory either...

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 m...

...es from other versions. This applies to the executable from isohybrid.c and to isohybrid.pl. So my proposal would be to fix isohybrid.c and to declare isohybrid.pl frozen and deprecated. (As long as isohybrid.in exists it will be able to adapt to the MBR templates of new SYSLINUX versiosn.) Ian Bannerman: > While I did know the .exe variant was not official / untrusted, Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Have a nice day :) Thomas

Hi, Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > One advantage of the Perl one for me is that I can run it on Windows. We at Tails rely on isohybrid.pl for installing on OSX: https://tails.boum.org/doc/first_steps/installation/manual/mac/ Of course, this does not mean that the current syslinux team owes u...

Op 2014-06-21 om 21:19 schreef intrigeri: > Hi, > > Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > > One advantage of the Perl one for me is that I can run it on Windows. > > We at Tails rely on isohybrid.pl for installing on OSX: > https://tails.boum.org/doc/first_steps/installation/manual/mac/ > > Of course, this does not mean that th...

...d 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 (GMT-05:00) To: Gene Cumm <gene.cumm at gmail.com>,"Taylor Jr, Matthew [U.S. Computer Corp]" <matthew.taylor at chevron.com> Cc: syslinux at zytor.com Subject: Re: [syslinux] SYSLINUX PXE LOCALBOOT Bitlockers Any devi...

...meone can still update the Perl variant, at least it should not be deleted and the differences / limitations should be documented. FWIW, I would not want to "declare" it frozen, as it would stop any potential contributions attempting to improve the Perl variant. > > > Ian Bannerman: > > While I did know the .exe variant was not official / untrusted, > > Is there a special reason for this ? (Except the known bugs which > affect Linux binaries, too.) I am not sure I understand you question. I don't know whether those "isohybrid.exe" are "un...

I'm using Ubuntu server 8.10 amd64 with the 3.2.3 samba they provide. I'm using winbind for authentication. Samba is the ONLY service this box is providing for a small office (maybe 15-18 users max). I am using Backup Exec 12.5 ralus but always at night, no active users. My hardware is very overkill for my application (file server for small office, 8gb ram, Intel quad core cpu, raid 10

Hey, question if I could. What kind of support does syslinux have for UEFI? In particular I'm looking to use syslinux on Windows 8 systems.. I know I can leverage the shim to work through SecureBoot, but yeah, I couldn't find any documentation as to UEFI support otherwise. Thanks! -- Ian Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

More context to this: syslinux_run_command calls into load_kernel(), and somewhere behind load_kernel things break. This is also broken at the boot: console prompt. Any commands executed at the boot: prompt also lose all parameters. --Ian > From: ian at internals.io > To: syslinux at zytor.com > Date: Tue, 29 Apr 2014 13:55:39 -0500 > Subject: [syslinux] Issues with

Thanks Ady, you were spot on, and I should have tested that scenario! I narrowed the issue down to a line in my config: ALLOWEDOPTIONS 0 The comment next to it in my config indicates this was added to disallow users dropping to the console with Escape or Tab, a restriction I would like to keep. BUT, when this is set whichsys fails to function in the manner I described. And similarly if I end up

I don't think that's it, but fair enough, try this sample config: ************************************************# Test File: isolinux.cfg default vesamenu.c32 ALLOWOPTIONS 0 LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img MENU END************************************************ I am using binaries from 6.03-pre11 from kernel.org. I used

With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk