Security Patch Announcements

2012-05-01 Thread llemike...@aol.com

Dear ,   ;-)

Using 5.0 I have now installed the two patches issued:

1) BIND patch from 01/12/2011
2) libcrypto patch from 23/04/12

What I cannot understand is that I have been registered
on the following mailing lists since 5 April 2012:

misc
tech
security-announce

However, I haven't seen an announcement of the libcrypto
patch on these lists.

Did I miss something? Was it announced on another list?

Mike



Re: Security Patch Announcements

2012-05-01 Thread llemike...@aol.com

Martin,

Aaaa! I see. So I didn't miss anything.

Thanks for the swift response.

Mike



Re: OpenBSD forked

2012-06-21 Thread llemike...@aol.com

Would it be right to say that the "OpenBSD forked?" discussion has been
forked into a discussion about the best way to learn C?

In my experience - the following ways are the best to learn:

1) Get a basic understanding of how a program is structured,
how to interface with other programs and the user,
and how the compilation and linker tools work.

2) Have an idea for a program you want to write.

The rest is based on your determination.

Mike



On 21/06/12 15:11, Gilles Chehade wrote:

On Thu, Jun 21, 2012 at 04:35:16PM +0300, Paul Irofti wrote:

On Thu, Jun 21, 2012 at 08:26:31AM -0400, Kenneth R Westerback wrote:

On Wed, Jun 20, 2012 at 09:16:24PM +0200, Otto Moerbeek wrote:

On Wed, Jun 20, 2012 at 11:39:44AM -0500, John wrote:


On Wed, Jun 20, 2012 at 08:28:22AM +0530, Jay Patel wrote:

Hi all users,

I am users too.  Thanks cody. I am learning C too. from "C primus
plus" any thoughts from devs. which we should read?

You may want to give this a try:
http://c.learncodethehardway.org/book/learn-c-the-hard-way.html


John

IMO tHe most valuable book is Kernighan & Ritchie "The C Programming
Language".

-Otto

+1

Pff... that's so 80's...
Cool kids these days want ``C in 21 days'' or some crap like that.


pfff...

C for dummies in two volumes is much much better !




OpenBSD - UEFI Secure Boot

2012-07-07 Thread llemike...@aol.com

Dear ,

I have been considering the implications for BSD and
Linux and any non-MS O/S of the implementation of UEFI
Secure Boot (SB).

As I understand it, ARM devices wishing to receive Win8 cert
are required to enable SB by default and prevent the disabling
of SB.

Meanwhile, x86 devices are supposed to ship with SB enabled
but allow disabling...

For some commentators, the x86 situation has been presented
as MS leaving a back-door for other OSes such as BSD or Linux
etc. i.e. "Don't worry about it"

I think it is, in fact, that MS is seeking to temporarily provide a
back-door for Win XP, Vista and Win7.

As each MS OS reaches end-of-paid-for-support (e.g. XP in 2014)
MS will slowly relax the UEFI SB specification such that the ability to
disable SB will gradually disappear from x86-based devices.

I am surprised that there is so little discussion of this developing
situation on BSD and/or Linux lists because for me, the red lights
are flashing, all bells and hooters are sounding,
"We gotta get out of here!!"

We are potentially talking about the end of BSD (or Linux...) on x86
hardware.

Am I overly pessimistic? Have I missed something?

OR

Am I Jeremiah shouting "There's a flood coming! There's a f**
flood coming, PEOPLE!" while everybody else is roasting sausages
on their barbecues?

Mike



Re: OpenBSD - UEFI Secure Boot

2012-07-07 Thread llemike...@aol.com

T,

A!! Oh Yes
I see what you are doing...

Ah-hahaha, Yes - I agree
Talk is so much puff...

We need to DO...

Time to work on CoreBoot or our own (who else will
do it?) aftermarket BIOS solutions...

Mike's plan:
1) Get EPROM programmer with PLCC adaptor
2) Get surface mount torch
3) Take over the world...

Mike


On 07/07/12 16:05, Theo de Raadt wrote:

Be realistic.  Talking about it on misc won't change anything.


Dear ,

I have been considering the implications for BSD and
Linux and any non-MS O/S of the implementation of UEFI
Secure Boot (SB).

As I understand it, ARM devices wishing to receive Win8 cert
are required to enable SB by default and prevent the disabling
of SB.

Meanwhile, x86 devices are supposed to ship with SB enabled
but allow disabling...

For some commentators, the x86 situation has been presented
as MS leaving a back-door for other OSes such as BSD or Linux
etc. i.e. "Don't worry about it"

I think it is, in fact, that MS is seeking to temporarily provide a
back-door for Win XP, Vista and Win7.

As each MS OS reaches end-of-paid-for-support (e.g. XP in 2014)
MS will slowly relax the UEFI SB specification such that the ability to
disable SB will gradually disappear from x86-based devices.

I am surprised that there is so little discussion of this developing
situation on BSD and/or Linux lists because for me, the red lights
are flashing, all bells and hooters are sounding,
"We gotta get out of here!!"

We are potentially talking about the end of BSD (or Linux...) on x86
hardware.

Am I overly pessimistic? Have I missed something?

OR

Am I Jeremiah shouting "There's a flood coming! There's a f**
flood coming, PEOPLE!" while everybody else is roasting sausages
on their barbecues?

Mike




Re: OpenBSD - UEFI Secure Boot

2012-07-07 Thread llemike...@aol.com

Tomas (and David and E.V.R. Else-Body)

Yes - I'd read the thread(s) (Gentoo too..) - but the
ultimate conclusion of much of the discussion is
"buy different hardware".

I bought Betamax (because it was the best)... until...
I bought SAAB (because it was the best)... until...
I bought Amiga (because it was the best)... until...

I don't want to be saying...

I bou.. erm.. got... OpenBSD (because it was the best)...

Mike



On 07/07/12 18:25, Tomas Bodzar wrote:

You are probably not reading misc@ or other forums (not even OpenBSD
specific) too much, right?

http://marc.info/?l=openbsd-misc&m=133857397722515&w=2  - for example




Not receiving messages from the list

2012-09-01 Thread llemike...@aol.com

Would anybody be able to explain why
I am not regularly receiving messages
from misc?
I haven't received anything since
22 August 2012.
Comments much appreciated.
Mike