grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Ilya Bakulin <Ilya_Bakulin@genua.de>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB2 on OpenBSD 5.3-amd64: linking problem
Date: Fri, 23 Aug 2013 11:31:06 +0200	[thread overview]
Message-ID: <52172BDA.4030409@gmail.com> (raw)
In-Reply-To: <201308231126.22583.Ilya_Bakulin@genua.de>

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

On 23.08.2013 11:26, Ilya Bakulin wrote:
> On Thursday 22 August 2013 20:16:48 Vladimir 'φ-coder/phcoder' Serbinenko 
> wrote:
>> On 21.08.2013 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>> Based on your work, current WIP patch. I've committed some parts of your
>>> patch as well as my own fixes. Remainder is attached
>>> Current problems:
>>> -double/float is mostly a kludge
>>> -build-grub-mkfont
>>> -nm on OpenBSD doesn't accept same options as GNU one.
>>
>> Only the first problem still remains.
> 
> I have just tested the compilation of the latest revision (5148) and confirm 
> that it compiles OK!
> There is a warning about random generator not being secure in 
> util/grub-mkpasswd-pbkdf2.c, which may be supressed by adding "&& ! defined 
> (__OpenBSD__)" to the defines list.
To do this we need a confirmation that reading from /dev/urandom is
indeed the right way to access PRNG on OpenBSD and that it gives us
cryptographically good random.


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

  parent reply	other threads:[~2013-08-23  9:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201308091537.37473.Ilya_Bakulin@genua.de>
     [not found] ` <520A9F30.6080901@gmail.com>
2013-08-14  8:59   ` GRUB2 on OpenBSD 5.3-amd64: linking problem Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-14 13:09     ` Ilya Bakulin
2013-08-14 13:27       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-14 13:31       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-14 13:49         ` Grégoire Sutre
2013-08-14 15:16           ` Ilya Bakulin
2013-08-14 16:28             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-16 14:33               ` Ilya Bakulin
2013-08-16 14:41                 ` Grégoire Sutre
2013-08-16 14:51                   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-15 15:00           ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-15 23:12             ` Grégoire Sutre
     [not found] ` <52150FC5.3040109@gmail.com>
     [not found]   ` <52165590.4050207@gmail.com>
     [not found]     ` <201308231126.22583.Ilya_Bakulin@genua.de>
2013-08-23  9:31       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-08-23 11:53         ` Ilya Bakulin
2013-08-30 17:33         ` Douglas Ray
2013-09-18 11:49           ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-23 15:59             ` Ilya Bakulin
2013-09-23 16:16               ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-07  9:05                 ` Ilya Bakulin

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=52172BDA.4030409@gmail.com \
    --to=phcoder@gmail.com \
    --cc=Ilya_Bakulin@genua.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).