search for: intrigeri

...driver: passwd-file args: /etc/dovecot/userdb socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: root group: mailgroup plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve fts: squat fts_squat: partial=4 full=10 Bye, -- intrigeri <intrigeri at boum.org> | gnupg key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | Do not be trapped by the need to achieve anything. | This way, you achieve everything.

...ers have a stick in version N that ships, say, syslinux 6.03-pre1, and the next upgrade to version N ships with 6.03-pre14's COM32R modules, will running syslinux 6.03-pre1 on the upgraded stick (that has 6.03-pre14 COM32R modules) make it unbootable? [1] https://tails.boum.org/ Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc

Actually, as you may have questions with some elements you'll see in the log, and especially: Detected Syslinux version: 6.03/20150819 (from '/EFI/BOOT/isolinux.bin') So I should point out that EFI/grub is actually used by the tails people to chain load EFI/Syslinux (hence the ldlinux.e64, ldlinux.c32 as well as isolinux.bin one also sees in /efi/boot/). As a result, in the

Hi, I have just installed dovecot and offlineimap on my laptop for syncing with my gmail, and reading in gnus, as outlined in this article: http://sachachua.com/wp/2008/05/08/geek-how-to-use-offlineimap-and-the-dovecot-mail-server-to-read-your-gmail-in-emacs-efficiently/ I am using Debian Etch, and I am the only user. The only change I made to the default dovecot.conf file was to set:

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? > > What we're doing is: > > label livefailsafe > menu label Live (failsafe) > kernel /live/vmlinuz2 > append initrd=/live/initrd2.img...

Hi, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO building scripts for TAILS, as this file is &gt...

...cludes utils/{linux/syslinux,win32/syslinux.exe}, that can be used to install a ldlinux.sys that exactly matches the included *.c32 modules. We use the former (utils/linux/syslinux) in Tails Installer when it's run from Tails, and Universal USB Installer uses the latter on Windows. Cheers, -- intrigeri

...around. > PS: [off-topic] > Reading the reports from users testing TAILS in UEFI systems, you > might want to consider adding the 'MENU RESOLUTION 1024 768' > directive to your EFI/tails.cfg as temporary workaround (for example, I'll look into it, thanks! Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc

Hi, we're trying to solve CVE-2008-4870 = rhbz#436287 = dovecot.conf is world readable - possible password exposure. This problem seems to be little more complicated than we thought. dovecot.conf can contain passphrase for ssl key, which is available for everyone since dovecot.conf has world readable permissions. (In CVE's description is note that it RHEL's/Fedora's problem,

Hi > Maybe I'm missing something, but this has been working flawlessly for > us in Tails so far. What exactly fails? Are you using EFI Handover Protocol? It might explain the difference Thomas

On Sun, Aug 9, 2015 at 3:44 AM, intrigeri via Syslinux <syslinux at zytor.com> wrote: > Hi, > > back in February, Scot Doyle proposed two patches: > > http://www.syslinux.org/archives/2015-February/023209.html 0a2dbb339 > http://www.syslinux.org/archives/2015-February/023179.html 83aad4f6 -- -Gene

...e this one -http://www.syslinux.org/archives/2013-November/021108.html - suggesting the Perl version. I did not know the Perl version did not support the EFI/Mac changes. For my use, that's critical, so I will not be using the Perl version further. (Thank you for the clarification there) intrigeri wrote: >We at Tails rely on isohybrid.pl for installing on OSX: >https://tails.boum.org/doc/first_steps/installation/manual/mac/ Now I'm confused, if Tails is able to use the .pl for the purpose of installing on OS X that would suggest it does have the EFI/Mac updates..? If the P...

On 2017.04.12 08:35, intrigeri via Syslinux wrote: > Wait, no, there's some misunderstanding going on here. Okay, I stand corrected. Knowing that tails was Debian based, I was assuming that you also followed the Debian boot model, which uses GRUB for UEFI. Considering that this is the Syslinux mailing list, it might b...

...a, but it might be that someone in here already knows better. * We currently use "--entry 4 --type 0x1c", for historical reasons; that doesn't impact whether the warning is displayed; however, it probably impacts on what hardware the USB stick boots or not. Cheers, -- intrigeri

Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux leaves long mode in kernel_jump assembly routine does not follow AMD64 specifications. More precisely: 1. After setting a new GADT, `cs` has to be refresh by doing a long jump, but it is not 2. Other segments have to be updated, but they are not 3. Disabling paging has to be done before disabling long mode, but the

...issue that has little > to do with versioning. > > Regards, > > /Pete This is going to sound "off-topic" in the Syslinux Mailing List; it is not. I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs and other users of Syslinux. If intrigeri (TAILS developer) "bites". then users reading this mailing list might learn one thing or two about Syslinux (6.04-pre1+). 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) originated in the ISO building scripts for TAILS, as this file is worthless for EFI. From the...

Correct base's type to match its initialization from prot_mode_base and passage to syslinux_memmap_find(). Tested with extlinux. Signed-off-by: Scot Doyle <lkml14 at scotdoyle.com> --- com32/lib/syslinux/load_linux.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/com32/lib/syslinux/load_linux.c b/com32/lib/syslinux/load_linux.c index 06ae2a9..ac73729 100644 ---

...are improved upstream as a result of our work, hence this email. So: What do you think shall be done on the isohybrid side? Shall it do this round-up-to-multiple-of-2048-bytes operation itself? [Tails] https://tails.boum.org/ [details] https://labs.riseup.net/code/issues/8891#note-9 Cheers, -- intrigeri

...Fedora ISOs. http://download.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso Debian, Ubuntu, and Archlinux ISOs with EFI support are made with isohybrid from xorriso/libisofs using "isohdp[fp]x*.bin" MBRs from the SYSLINUX installation. intrigeri: > Would it help if someone with the needed > Perl skills stepped up and volunteered to maintain the Perl version, > at least to port bugfixes from the C version? I am willing to explain what is unclear about above options. Theory is in http://bazaar.launchpad.net/~libburnia-team/libiso...

>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