All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Simon Schubert <2@0x2c.org>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Integrating grub2tc into upstream GRUB
Date: Wed, 06 Jul 2011 14:30:17 +0200	[thread overview]
Message-ID: <4E145559.3040204@gmail.com> (raw)
In-Reply-To: <4E1454E4.6040602@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Note: I treat truecrypt as a proprietary software but due to its
popularity it makes sense to support it.
On 06.07.2011 14:28, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, I've had a look into your grub2tc project and I think it can be
> successfully changed into a GRUB2 module. extract.rb would need to be
> rewritten in C. tcloader.S would mostly disappear and be replaced with a
> small C code to set the registers and load the file. Could you tell me
> the expected load address and register values? Also current license
> prohibits direct use of your code in GRUB2. Could you drop the Affero
> clause? IT's useful mainly for network-based projects.
> Also a possibility is to dump the contents of MBR gap on grub-setup and
> if it's a truecrypt loader, save it in a file. Do you know of any
> signature which can be used for this? This way we can integrate
> truecrypt into grub-mkconfig.
> Thank you in advance
>



-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2011-07-06 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 12:28 Integrating grub2tc into upstream GRUB Vladimir 'φ-coder/phcoder' Serbinenko
2011-07-06 12:30 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-07-06 13:12   ` Simon Schubert
2011-07-06 20:42     ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E145559.3040204@gmail.com \
    --to=phcoder@gmail.com \
    --cc=2@0x2c.org \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.