On Mon, Oct 14, 2024 at 08:44:56AM -, Stuart Henderson wrote:
> On 2024-10-14, Lorenz (xha) wrote:
> > hi, i'd like to kindly ask if the patches that are included in
> > snapshots could somehow be provided to the people running the
> > snapshots, in some way, like source-changes@?
>
> It's no
On 2024-10-14, Lorenz (xha) wrote:
> hi, i'd like to kindly ask if the patches that are included in
> snapshots could somehow be provided to the people running the
> snapshots, in some way, like source-changes@?
It's not reliably possible, because the tree is shared between archs,
and a build on
hi, i'd like to kindly ask if the patches that are included in
snapshots could somehow be provided to the people running the
snapshots, in some way, like source-changes@?
one part of free and open source software is that i know which code
i am running.
and i am obviously totally fine with testing
On Sat, Mar 16, 2019 at 12:38:09PM -, Christian Weisgerber wrote:
> On 2019-03-15, Patrick Wildt wrote:
>
> > CVSROOT:/cvs
> > Module name:src
> > Changes by: patr...@cvs.openbsd.org 2019/03/15 17:20:35
> >
> > Modified files:
> > sys/dev/usb: xhci.c
> >
> > Log message:
On 2019-03-15, Patrick Wildt wrote:
> CVSROOT: /cvs
> Module name: src
> Changes by: patr...@cvs.openbsd.org 2019/03/15 17:20:35
>
> Modified files:
> sys/dev/usb: xhci.c
>
> Log message:
> Improve and enable isochronous transfers in xhci(4). [...]
Wow, that appears to be the
Hello Gilles,
In article <20190101143249.ga41...@ams-1.poolp.org> Gilles Chehade
wrote:
> On Tue, Jan 01, 2019 at 01:14:54PM +0100, Walter Alejandro Iglesias wrote:
> > On Fri, Dec 21, 2018 at 06:59:58PM +0100, Gilles Chehade wrote:
> > > On Fri, Dec 21, 2018 at 06:56:57PM +0100, Walter Alejandr
On Tue, Jan 01, 2019 at 01:14:54PM +0100, Walter Alejandro Iglesias wrote:
> On Fri, Dec 21, 2018 at 06:59:58PM +0100, Gilles Chehade wrote:
> > On Fri, Dec 21, 2018 at 06:56:57PM +0100, Walter Alejandro Iglesias wrote:
> > > Hello Gilles,
> > >
> > > In article <20181221145201.ga90...@ams-1.poolp
On Fri, Dec 21, 2018 at 06:59:58PM +0100, Gilles Chehade wrote:
> On Fri, Dec 21, 2018 at 06:56:57PM +0100, Walter Alejandro Iglesias wrote:
> > Hello Gilles,
> >
> > In article <20181221145201.ga90...@ams-1.poolp.org> Gilles Chehade
> > wrote:
> > > On Fri, Dec 21, 2018 at 07:41:41AM -0700, Gil
Hello Gilles,
In article <20181221145201.ga90...@ams-1.poolp.org> Gilles Chehade
wrote:
> On Fri, Dec 21, 2018 at 07:41:41AM -0700, Gilles Chehade wrote:
> > CVSROOT: /cvs
> > Module name: src
> > Changes by: gil...@cvs.openbsd.org 2018/12/21 07:41:41
> >
> > Modified files:
> >
On Fri, Dec 21, 2018 at 06:56:57PM +0100, Walter Alejandro Iglesias wrote:
> Hello Gilles,
>
> In article <20181221145201.ga90...@ams-1.poolp.org> Gilles Chehade
> wrote:
> > On Fri, Dec 21, 2018 at 07:41:41AM -0700, Gilles Chehade wrote:
> > > CVSROOT: /cvs
> > > Module name: src
> > > Ch
On Mon, Nov 30, 2015 at 05:45:25PM -0500, Daniel Ouellet wrote:
> On 11/30/15 4:58 PM, Joerg Jung wrote:
> > On Mon, Nov 30, 2015 at 04:48:05PM -0500, Daniel Ouellet wrote:
> >> Even removed the table password?
> >
> > Yes.
> >
> >> NO way anymore to have difference password for emails then the
On 11/30/15 4:58 PM, Joerg Jung wrote:
> On Mon, Nov 30, 2015 at 04:48:05PM -0500, Daniel Ouellet wrote:
>> Even removed the table password?
>
> Yes.
>
>> NO way anymore to have difference password for emails then the system
>> password without smtp-extra install?
>
> You may want to read table
d,
that is why it is removed.
> Forwarded Message ----
> Subject: CVS: cvs.openbsd.org: src
> Date: Mon, 30 Nov 2015 12:54:26 -0700 (MST)
> From: Joerg Jung
> To: source-chan...@openbsd.org
>
> CVSROOT: /cvs
> Module name: src
> Changes by: j...@cvs.
.
Or am I missing something or miss understand the commit?
Forwarded Message
Subject: CVS: cvs.openbsd.org: src
Date: Mon, 30 Nov 2015 12:54:26 -0700 (MST)
From: Joerg Jung
To: source-chan...@openbsd.org
CVSROOT:/cvs
Module name:src
Changes by: j
rl in base built against libpthread.19.0 cannot load
the mysql.so shared object linked against libpthread.18.1
Philip Guenther
-- Forwarded message --
From: Philip Guenther
Date: Mon, Apr 6, 2015 at 6:27 PM
Subject: CVS: cvs.openbsd.org: src
To: source-chan...@cvs.openbsd.org
CV
On 09.11.2014 12:59, thev...@openmailbox.org wrote:
On Sun, 9 Nov 2014 10:09:49 +0100 =?utf-8?Q?S=C3=A9bastien?= Marie
wrote:
On Sat, Nov 08, 2014 at 10:57:41PM +0200, Atanas Vladimirov wrote:
> On 24.10.2014 00:33, Robert Peichaer wrote:
>
> I'm following -current and decided to try autoinstal
On Sun, 9 Nov 2014 10:09:49 +0100 =?utf-8?Q?S=C3=A9bastien?= Marie
wrote:
> On Sat, Nov 08, 2014 at 10:57:41PM +0200, Atanas Vladimirov wrote:
> > On 24.10.2014 00:33, Robert Peichaer wrote:
> >
> > I'm following -current and decided to try autoinstall(8) from
> > /auto_upgrade.conf when I moved
On Sat, Nov 08, 2014 at 10:57:41PM +0200, Atanas Vladimirov wrote:
> On 24.10.2014 00:33, Robert Peichaer wrote:
>
> I'm following -current and decided to try autoinstall(8) from
> /auto_upgrade.conf when I moved to newer snapshot.
> I made a custom auto_upgrade.conf on my root [sd2a] partition bu
On Sat, 08 Nov 2014 22:57:41 +0200 Atanas Vladimirov wrote:
> On 24.10.2014 00:33, Robert Peichaer wrote:
> > CVSROOT:/cvs
> > Module name:src
> > Changes by: r...@cvs.openbsd.org2014/10/23 15:33:21
> >
> > Modified files:
> > distrib/miniroot: dot.profile install.sub
> >
On 24.10.2014 00:33, Robert Peichaer wrote:
CVSROOT:/cvs
Module name:src
Changes by: r...@cvs.openbsd.org2014/10/23 15:33:21
Modified files:
distrib/miniroot: dot.profile install.sub
distrib/notes : m4.common
share/man/man8 : autoinstall.8
Log messag
On Mon, 18 Aug 2014, Jason Tubnor wrote:
On 2 June 2014 10:23, Ted Unangst wrote:
Part of the deprecation / migration process is identifying the weird
ways people use vnd and finding solutions for them. But as we've seen,
people never move forward without the occasional push.
So the most
On 2 June 2014 10:23, Ted Unangst wrote:
>
> Part of the deprecation / migration process is identifying the weird
> ways people use vnd and finding solutions for them. But as we've seen,
> people never move forward without the occasional push.
>
So the most appropriate way to use vnd(4) as an en
, as I broke listing of /proc back in January
>and
>no one has noticed, suggesting that no one is actually using it...
>
>Philip Guenther
>
>
>-- Forwarded message --
>From: Philip Guenther
>Date: Sun, Jun 22, 2014 at 2:15 PM
>Subject: CVS: cvs.openbsd.org
g it...
>
> Philip Guenther
>
>
> -- Forwarded message --
> From: Philip Guenther
> Date: Sun, Jun 22, 2014 at 2:15 PM
> Subject: CVS: cvs.openbsd.org: src
> To: source-chan...@cvs.openbsd.org
>
>
> CVSROOT:/cvs
> Module name:src
>
y using it...
Philip Guenther
-- Forwarded message --
From: Philip Guenther
Date: Sun, Jun 22, 2014 at 2:15 PM
Subject: CVS: cvs.openbsd.org: src
To: source-chan...@cvs.openbsd.org
CVSROOT:/cvs
Module name:src
Changes by: guent...@cvs.openbsd.org2014/06/2
On Sun, Jun 01, 2014 at 11:37, Theo de Raadt wrote:
>> Could you please provide a little bit more information? What causes
>> encrypted vnd to be insecure
>
> Ted went a bit far; it is unusual for him to be melodratic.
>
> Basically -- less than state of the art crypto.
You would never use blow
> Could you please provide a little bit more information? What causes
> encrypted vnd to be insecure
Ted went a bit far; it is unusual for him to be melodratic.
Basically -- less than state of the art crypto.
> and what will happen to vnd(4) before 5.7 if it isn't removal of crypto?
You persis
On Fri, 30 May 2014, Theo de Raadt wrote:
Robert [info...@die-optimisten.net] wrote:
On Fri, 30 May 2014 12:19:35 -0400
Ted Unangst wrote:
WARNING: Encrypted vnd is insecure.
Migrate your data to softraid before 5.7.
Will 5.6 softraid support block sizes other than 512 byte?
marc.info/?l=o
On Fri, May 30, 2014 at 19:45, Jonathan Thornburg wrote:
> What will be the "right" way to achieve such a nested-encryption setup
> once encrypted vnd goes away? Is/will it be safe (i.e., free from
> data corruption, deadlock, or other kernel badness) to nest softraid
> crypto volumes?
Short answ
In message < http://marc.info/?l=openbsd-misc&m=140146687910205&w=1>,
Ted Unangst wrote:
> If you are using encrypted vnd (vnconfig -k or -K) you will want to
> begin planning your migration strategy.
[[...]]
> WARNING: Encrypted vnd is insecure.
> Migrate your data to softraid before 5.7.
Once th
> > Robert [info...@die-optimisten.net] wrote:
> > > On Fri, 30 May 2014 12:19:35 -0400
> > > Ted Unangst wrote:
> > > > WARNING: Encrypted vnd is insecure.
> > > > Migrate your data to softraid before 5.7.
> > >
> > > Will 5.6 softraid support block sizes other than 512 byte?
> > >
> > > marc.i
On Fri, 30 May 2014 11:14:40 -0700
Chris Cappuccio wrote:
> Robert [info...@die-optimisten.net] wrote:
> > On Fri, 30 May 2014 12:19:35 -0400
> > Ted Unangst wrote:
> > > WARNING: Encrypted vnd is insecure.
> > > Migrate your data to softraid before 5.7.
> >
> > Will 5.6 softraid support block
Robert [info...@die-optimisten.net] wrote:
> On Fri, 30 May 2014 12:19:35 -0400
> Ted Unangst wrote:
> > WARNING: Encrypted vnd is insecure.
> > Migrate your data to softraid before 5.7.
>
> Will 5.6 softraid support block sizes other than 512 byte?
>
> marc.info/?l=openbsd-misc&m=13952454370637
On Fri, 30 May 2014 12:19:35 -0400
Ted Unangst wrote:
> WARNING: Encrypted vnd is insecure.
> Migrate your data to softraid before 5.7.
Will 5.6 softraid support block sizes other than 512 byte?
marc.info/?l=openbsd-misc&m=139524543706370
kind regards,
Robert
If you are using encrypted vnd (vnconfig -k or -K) you will want to
begin planning your migration strategy.
-- Forwarded message --
From: "Ted Unangst"
Date: Fri 2014/05/30 10:14 -06:00
Subject: CVS: cvs.openbsd.org: src
To: source-chan...@cvs.openbsd.org
CVSROOT:
> Why is there cu(1) and tip(1) in base ?
> I am wondering what is the real difference between these two (apart
> tip(1) has more options :p)
It is a bit historical. A large factor is that unfortunately people's
fingers remember things.
In reality the cost is very small, since they can be hard l
Hi all,
Why is there cu(1) and tip(1) in base ?
I am wondering what is the real difference between these two (apart
tip(1) has more options :p)
Denis
Le 26/03/2014 14:00, Nicholas Marriott a écrit :
> CVSROOT: /cvs
> Module name: src
> Changes by: n...@cvs.openbsd.org2014/03/26 07:00
Kevin Chadwick [ma1l1i...@yahoo.co.uk] wrote:
> Made my day.
>
> So does this mean machdep can be turned off for some hardware and is
> the best way to find out, simply to try?
>
If inteldrm attaches, the aperture now appears to work at 1 (instead
of 2) but not yet 0.
On Mon, Mar 18, 2013 at 9:48 PM, Kevin Chadwick wrote:
>> > Log message:
>> > Significantly increase the wordlist for ddb hangman,
>> > and update our device independent DRM code and the Intel DRM code
>> > to be mostly in sync with Linux 3.8.3. Among other things this
>> > brings support for ker
> > Log message:
> > Significantly increase the wordlist for ddb hangman,
> > and update our device independent DRM code and the Intel DRM code
> > to be mostly in sync with Linux 3.8.3. Among other things this
> > brings support for kernel modesetting and enables use of
> > the rings on gen6+ Int
On Mon, Mar 18, 2013 at 02:13:20PM +0100, LEVAI Daniel wrote:
> On h, márc 18, 2013 at 06:36:52 -0600, Jonathan Gray wrote:
> [...]
> > Log message:
> > Significantly increase the wordlist for ddb hangman,
> > and update our device independent DRM code and the Intel DRM code
> > to be mostly in syn
On h, márc 18, 2013 at 06:36:52 -0600, Jonathan Gray wrote:
[...]
> Log message:
> Significantly increase the wordlist for ddb hangman,
> and update our device independent DRM code and the Intel DRM code
> to be mostly in sync with Linux 3.8.3. Among other things this
> brings support for kernel m
Over on source-changes, Kevin Chadwick wrote:
> I don't disagree with using AES-128 as default on a possibly busy mail
> server. I was just wondering why the word obsolete was used and if it
> was simply because twofish and AES are faster.
Blowfish is older, not standardized, and hasn't received
On Thu, Apr 12, 2012 at 6:26 AM, Mo Libden wrote:
> Wow. If memory serves, rfork() availability was a feature.
> Now it is gone... Any reasons to share please?
>
> It allowed creation of interesting types of processes,
> awesome flexibility regarding share of memory space
> and/or file handle tabl
Thu, 12 Apr 2012 11:32:54 -0400 P>Q Ted Unangst :
> On Thu, Apr 12, 2012, Mo Libden wrote:
>
> > Wow. If memory serves, rfork() availability was a feature.
> > Now it is gone... Any reasons to share please?
> >
> > It allowed creation of interesting types of processes,
> > awesome flexibility re
On Thu, Apr 12, 2012, Mo Libden wrote:
> Wow. If memory serves, rfork() availability was a feature.
> Now it is gone... Any reasons to share please?
>
> It allowed creation of interesting types of processes,
> awesome flexibility regarding share of memory space
> and/or file handle tables.
rthre
Thu, 12 Apr 2012 06:33:04 -0600 (MDT) P>Q Theo de Raadt
:
> CVSROOT: /cvs
> Module name: src
> Changes by: dera...@cvs.openbsd.org 2012/04/12 06:33:04
>
> Modified files:
> sys/kern : kern_fork.c syscalls.master
> sys/sys: param.h proc.h vmmeter.h
> incl
On Tue, Mar 13, 2012 at 05:07:58PM -0600, Gilles Chehade wrote:
> CVSROOT: /cvs
> Module name: src
> Changes by: gil...@cvs.openbsd.org 2012/03/13 17:07:58
>
> Modified files:
> usr.sbin/smtpd : scheduler_ramqueue.c
>
> Log message:
> When moving back envelope from offload tree to
Christian Weisgerber wrote:
> == xterm ==
What doesn't work: UTF-8 mode is incompatible with 8-bit control
sequences. If that doesn't ring a bell for you, then you don't
need to worry about it. ;-)
I only noticed because the RMC on my AlphaServer 800 inserts 8-bit
controls to set bold and blin
Stefan Sperling wrote:
> Log message:
> Install the en_US.UTF-8 ctype locale support file, and allow the UTF-8
> ctype locale to be enabled via setlocale(3) (export LC_CTYPE='en_US.UTF-8').
>
> A lot of programs, especially from ports, will now start using UTF-8 if the
> UTF-8 locale is enabled
> On Friday 23 April 2010 15:32:57 Owain Ainsworth wrote:
> > CVSROOT:/cvs
> > Module name:src
> > Changes by: o...@cvs.openbsd.org2010/04/23 13:32:57
> >
> > Modified files:
> > sys/ntfs : ntfs_ihash.c
> >
> > Log message:
> > It is about time that we stopped pretending s
On Friday 23 April 2010 15:32:57 Owain Ainsworth wrote:
> CVSROOT: /cvs
> Module name: src
> Changes by: o...@cvs.openbsd.org2010/04/23 13:32:57
>
> Modified files:
> sys/ntfs : ntfs_ihash.c
>
> Log message:
> It is about time that we stopped pretending simple_locks are lock
I concede, this mail and my solution was not completely thought out.
While making Xsession/xinitrc (tried startx since my first e-mail) run
under sh -l would source .profile and allow it to set any environment
variables, only that environment would persist, not any aliases or set
commands whic
> I concede, this mail and my solution was not completely thought out.
> While making Xsession/xinitrc (tried startx since my first e-mail) run
> under sh -l would source .profile
And what if a person's shell is actually csh, or some other shell?
Then it does not work.
> > CVSROOT:/cvs
> > Module name:src
> > Changes by: dera...@cvs.openbsd.org 2009/04/25 11:36:48
> >
> > Modified files:
> > etc: Makefile
> > Added files:
> > etc/root : dot.Xdefaults
> > etc/skel : dot.Xdefaults
> >
> > Log message:
> > Provide u
CVSROOT:/cvs
Module name:src
Changes by: dera...@cvs.openbsd.org 2009/04/25 11:36:48
Modified files:
etc: Makefile
Added files:
etc/root : dot.Xdefaults
etc/skel : dot.Xdefaults
Log message:
Provide users by default with XTerm*loginShell:true. This
> Damien Miller wrote:
>
> > Modified files:
> > usr.bin/ssh: myproposal.h
> >
> > Log message:
> > prefer CTR modes and revised arcfour (i.e w/ discard) modes to CBC
> > modes; ok markus@
>
> This means that ssh's default cipher will no longer profit from
> hifn(4) or glxsb(4) acceler
Damien Miller wrote:
> Modified files:
> usr.bin/ssh: myproposal.h
>
> Log message:
> prefer CTR modes and revised arcfour (i.e w/ discard) modes to CBC
> modes; ok markus@
This means that ssh's default cipher will no longer profit from
hifn(4) or glxsb(4) acceleration.
People relyi
On Fri, 12 Sep 2008 11:51:40 +0300
"Denis Doroshenko" <[EMAIL PROTECTED]> wrote:
> hi,
>
> On Thu, Sep 11, 2008 at 3:45 PM, Miod Vallat <[EMAIL PROTECTED]>
> wrote:
> > CVSROOT:/cvs
> > Module name:src
> > Changes by: [EMAIL PROTECTED]2008/09/11 06:45:20
> >
> > Modified files
Markus Bergkvist wrote:
I've had the "acpitz0: _AL1[0] not a object ref" problem with my HP
Compaq 6710B too, with -current it seems to be fixed
/Markus
Not entirely true. Yesterday I got
acpitz2: TZ5_: failed to read _TMP
acpitz2: TZ5_: failed to read temp
once every minute and today it spo
I've had the "acpitz0: _AL1[0] not a object ref" problem with my HP
Compaq 6710B too, with -current it seems to be fixed
/Markus
OpenBSD 4.4-current (GENERIC.MP) #29: Sun Sep 14 18:59:41 CEST 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2125410304 (2026MB)
av
Miod@ had a diff for that and i tried it, it fixes the warnings and
heat control completely. now i hear fan changing rotation speed
according to system load and temperature values in the different TZ
seem to be held within appropriate range.
As far as i can tell, Miod already submitted the diff to
On Fri, Sep 12, 2008 at 11:51:40AM +0300, Denis Doroshenko wrote:
> in a hope this diff would fix overheating under ACPI on my compaq
> nc6000, built the kernel and found out that this diff changed acpitz
> warnings from:
>
> acpitz0: _AL1[0] not a object ref
> acpitz0: _AL2[0] not a object ref
>
It does and yay for miod for picking this up. This was way long on my
list.
On Fri, Sep 12, 2008 at 11:51:40AM +0300, Denis Doroshenko wrote:
> hi,
>
> On Thu, Sep 11, 2008 at 3:45 PM, Miod Vallat <[EMAIL PROTECTED]> wrote:
> > CVSROOT:/cvs
> > Module name:src
> > Changes by: [EM
hi,
On Thu, Sep 11, 2008 at 3:45 PM, Miod Vallat <[EMAIL PROTECTED]> wrote:
> CVSROOT:/cvs
> Module name:src
> Changes by: [EMAIL PROTECTED]2008/09/11 06:45:20
>
> Modified files:
>sys/dev/acpi : acpitz.c
>
> Log message:
> Thermal Zone entities might not be direct ob
On Fri, Jul 11, 2008 at 09:34:36AM +0200, Ariane van der Steldt wrote:
> On Thu, Jul 10, 2008 at 10:21:28PM -0500, Marco Peereboom wrote:
> > I currently have a 3500 line diff in my tree that completely rewrites
> > softraid metadata handling. The idea is that when this goes in we can
> > start ad
I would strongly recommend against that.
On Fri, Jul 11, 2008 at 10:19:52AM +0100, Stuart Henderson wrote:
> [EMAIL PROTECTED]> <[EMAIL PROTECTED]
> net> <[EMAIL PROTECTED]>
> Date: Fri, 11 Jul 2008 10:19:52 +0100
>
> In gmane.os.openbsd.misc, you wrote:
> > When this change goes in old softraid
[EMAIL PROTECTED]> <[EMAIL PROTECTED]
net> <[EMAIL PROTECTED]>
Date: Fri, 11 Jul 2008 10:19:52 +0100
In gmane.os.openbsd.misc, you wrote:
> When this change goes in old softraid metadata formats will no longer
> work! So now is a good time to get dumps going. I am _not_ planning on
> adding a me
On Thu, Jul 10, 2008 at 10:21:28PM -0500, Marco Peereboom wrote:
> I currently have a 3500 line diff in my tree that completely rewrites
> softraid metadata handling. The idea is that when this goes in we can
> start adding foreign raid formats as sub-drivers to softraid.
With foreign raid format
I currently have a 3500 line diff in my tree that completely rewrites
softraid metadata handling. The idea is that when this goes in we can
start adding foreign raid formats as sub-drivers to softraid. This also
fixes issues of power failures and crashes where the checksums are no
longer correct.
On Jun 14, 2008, at 1:47 PM, Damien Miller wrote:
Just to reinforce the "experimental" thing:
There are some big softraid changes coming that will alter the on-disk
metadata format (for all softraid disciplines, not just crypto).
Volumes
created with the current tools will be unreadable afte
> > List: openbsd-cvs
> > Subject:CVS: cvs.openbsd.org: src
> > From: Pierre-Yves Ritschard
> > Date: 2008-06-26 15:10:02
> > Message-ID: 200806261510.m5QFA2Aa007357 () cvs ! openbsd ! org
> > [Download message RAW]
> >
> &
> List: openbsd-cvs
> Subject: CVS: cvs.openbsd.org: src
> From: Pierre-Yves Ritschard
> Date: 2008-06-26 15:10:02
> Message-ID: 200806261510.m5QFA2Aa007357 () cvs ! openbsd ! org
> [Download message RAW]
>
> CVSROOT: /cvs
> Module name:
TED]
Subject: CVS: cvs.openbsd.org: src
X-Loop: [EMAIL PROTECTED]
Precedence: list
CVSROOT:/cvs
Module name:src
Changes by: [EMAIL PROTECTED] 2008/04/02 02:54:08
Modified files:
sys/dev/usb: ubsa.c
Log message:
attach the ZTE CMDMA MSM modem from qualcomm.
from
so spake Xavier Santolaria on Wed, Jan 11, 2006 at 09:08:55AM CET:
> CVSROOT: /cvs
> Module name: src
> Changes by: [EMAIL PROTECTED] 2006/01/11 01:08:53
>
> Modified files:
> share/man/man4/man4.macppc: asms.4
>
> Log message:
> add HARDWARE and HISTORY section; ok [EMAIL PR
Hans-Joerg Hoexer <[EMAIL PROTECTED]> wrote:
> Added files:
> etc: ipsec.conf
>
> Log message:
> Very basic sample ipsec.conf, more to come. Has been demanded by deraadt@ for
> a long time, but i'm a bloody slacker...
Which raises the question where to insert ipsecctl -f /etc
76 matches
Mail list logo
