RIT is shutting down power to the building ftp.usa.openbsd.org resides
in today at 4pm. Accordingly, I will be shutting the mirror down at
3pm. This will be a short outage, and I will be turning things back on
by 9pm tonight.
(All times are EDT)
FYI
--Kurt Mosiejczuk
RIT is doing two overnight power outages again starting 5pm (EDT)
Monday May 13th. Accordingly, ftp5.usa.openbsd.org (which is also
ftp3.usa.openbsd.org and ftp.usa.openbsd.org) will be down from Monday
Afternoon until the power comes back on Wednesday morning on May 15th.
--Kurt Mosiejczuk
RIT is turning off the power for electrical maintenance today and tomorrow.
ftp5 will be out 4pm EST until 1am EST. This dance will happen again
tomorrow, but the outage will last until 7am EST the following morning.
FYI
--Kurt Mosiejczuk
Saw some folks talking about Sun M3000 machines that got "bricked" by
installing OpenBSD. (They aren't really bricked, but the unbricking
process so far is having an Oracle Support contract and getting a hardware
engineer out).
Since some folks apparently pick these up to run OpenBSD, let's move
--Kurt Mosiejczuk
Due to a power outage happening this Sunday morning,
ftp5.usa.openbsd.org will be going down around 10pm EDT (UTC-4) on
Saturday September 24th. I will bring it back up when the power comes
back at 9:30am EDT on Sunday September 25th, so it should be back up by
11am EDT.
FYI
--Kurt
Due to a just-announced power outage happening this Sunday night,
ftp5.usa.openbsd.org will be going down around 7pm EDT (UTC-4) on
Sunday September 14th. I will bring it back up when the power comes
back at midnight EDT, so it should be back up by 1am EDT.
FYI
--Kurt Mosiejczuk
On Sat, Aug 13, 2016 at 03:40:28PM +0200, mxb wrote:
> > On 11 aug. 2016, at 21:44, Kurt Mosiejczuk wrote:
> > I've noticed that for 5.9, any VMs (in VMware) using vmx(4), end up putting
> > "vmx0: device timeout" into the dmesg a bunch when under network loa
I've noticed that for 5.9, any VMs (in VMware) using vmx(4), end up putting
"vmx0: device timeout" into the dmesg a bunch when under network load.
I switched one of the VMs to vic(4) and the messages stop. Another VM that
I haven't gotten to upgrading from 5.8 to 5.9 yet doesn't show this in its
I brought ftp5 back up this morning around 7:15am EDT and checked it was
working, it will be going down again around 4pm EDT since RIT is doing
the second half of their electrical substation work tonight from 5pm
until 7am. I'll bring it back up tomorrow morning shortly after 7am.
-
ck up
by 8am EDT on Thursday and Friday.
Sorry for the late notice, I sent it to mirrors-discuss first and someone
pointed out I should send it here, but I've been running around getting
ready for the shutdown.
--Kurt Mosiejczuk
On Wed, Jan 06, 2016 at 12:44:00PM +, Roderich wrote:
> (2) I tried to install with PXE Boot, I booted bsd.rd from another
> machine that also offered the sets with http to 10.0.0.1/5.8/i386,
> but the installation program did not find the sets. I went to
> shell and the sets co
On Wed, Dec 09, 2015 at 10:31:01PM +0100, Antoine Jacoutot wrote:
> On Wed, Dec 09, 2015 at 01:32:31PM -0500, Kurt Mosiejczuk wrote:
> > On Wed, Dec 09, 2015 at 04:15:07PM -0200, Friedrich Locke wrote:
> > > Does security/cyrus-sasl2 include support for GSSAPI (I am in need
On Wed, Dec 09, 2015 at 04:15:07PM -0200, Friedrich Locke wrote:
> Does security/cyrus-sasl2 include support for GSSAPI (I am in need of
> kerberos) ?
Not currently. They removed that support when they kicked Heimdal out
of base.
One of my spare time projects is looking how to put that back in a
ng or special setting?
> I'm planning on migrating a few Soekris boxes to virtual machines. Is this
> reliable? Is anyone running production OpenBSD servers on VMware?
Lots and lots. I find OpenBSD one of the best behaved guests on my virtual
infrastructure.
--Kurt Mosiejczuk
On Sat, Nov 14, 2015 at 04:58:58PM +0100, Riccardo Mottola wrote:
> Nick Holland wrote:
> >>><* peers over at the case of narrow SCSI drives sitting on the spare
> >>>parts shelf and wonder if they'll still spin up; they probably will *>
> >and before tossing them, let developers know -- 4, 6
On Fri, Oct 30, 2015 at 03:41:19PM +, Olivier Debr?? wrote:
> Plus, as I wrote, there are 50+ apps linked with libcrypto, and I prefer
> putting back all base58.tgz in place instead of rebuilding all of them.
There aren't 50+ apps linked *statically* to libcrypto. They use it as
a shared lib
On Wed, Sep 23, 2015 at 01:27:27PM +0100, Stuart Henderson wrote:
> On 2015/09/23 08:16, Kurt Mosiejczuk wrote:
> > Can you point me at the bug fix? I was looking at cvsweb again and the
> > newest change I could see there is 2 weeks ago...
> I believe this is the issue fi
On Wed, Sep 23, 2015 at 07:37:05AM +, Stuart Henderson wrote:
> On 2015-09-22, Kurt Mosiejczuk wrote:
> > I just updated my current box to yesterdays (2015-09-21) snapshot. Now
> > it won't keep a network address.
> That's a recent bug - should be fixed if
I just updated my current box to yesterdays (2015-09-21) snapshot. Now
it won't keep a network address.
eisenhower# dhclient -d em0
DHCPREQUEST on em0 to 255.255.255.255
DHCPACK from 129.21.208.254 (d0:c2:82:f2:94:00)
SIOCAIFADDR failed (129.21.208.29): File exists
bound to 129.21.208.29 -- ren
On Mon, Sep 14, 2015 at 05:15:01PM +, Dewey Hylton wrote:
> > I've had this issue with the same systems. Never guessed it would
> > be OpenBSD specific. What I've found to make it stop happening is
> > pulling the board out and redoing the thermal paste for the CPU
> > heatsink. I had found
On Sat, Sep 12, 2015 at 03:51:36PM +, Dewey Hylton wrote:
> the only real differences i see are:
> 1) bios revision
> 2) secondary disk attached to different sata port
> 3) sensors only present on working machine
I've had this issue with the same systems. Never guessed it would be OpenBSD
sp
On 6/5/2014 4:02 PM, Miod Vallat wrote:
Now you have and example of how they are unwilling to work with you next
time someone asks why not work with OpenSSL on fixing it. Pretty direct
proof.
The culture gap between OpenSSL and OpenBSD/LibreSSL is UNFIXABLE.
We believe in peer review; they
On 6/5/2014 3:27 PM, Theo de Raadt wrote:
Unfortunately I find myself believing reports that the OpenSSL people
intentionally asked others for quarantine, and went out of their way
to ensure this information would not come to OpenBSD and LibreSSL.
There, I've said it.
Now you have and examp
On Mon, Jun 03, 2013 at 03:49:22PM +0200, Peter N. M. Hansteen wrote:
> ALTQ is old code (perhaps move obviously so to German speakers than others
> ;)), a replacement
> is in the pipeline but not immediately ready, unfortunately.
> http://bsdly.blogspot.ca/2011/07/anticipating-post-altq-world.
Theo de Raadt wrote:
Well I moved to position that booting with a passphrase and then
concatenate strong passphrase from an Yubikey configured with
static passphrase would be better solution than keydisk and
passphrase.
Although I don't have an Yubikey token now but as an Yubikey
token is simu
I noticed when populating my mirror with the 5.2 release, that the
packages for sh just end with the packages starting with 'g'. I just
double checked when writing this, and even ftp.openbsd.org has the same
incomplete set of packages for sh. Was there some glitch? Or is there
some limitatio
Jan Stary wrote:
Strangely, the only occurence of 2.139.201.210 in the last month's
maillog is just this; that's half an hour after it got WHITE.
What happend at Mon Oct 29 14:49:24 CET 2012 that made it WHITE?
Anyway, it seems (some) spambots got less demented and actually do
resend, getting
Otto Moerbeek wrote:
untarring the sets and copying the kernel by hand is not recommended.
I used the perfect phrase for this in a presentation on PF a week ago:
"You wouldn't ever do this... unless maybe you hate yourself."
--Kurt
Daniel Ouellet wrote:
Anyone have any possible explication that would actually justify the use
of NAT64 that I obviously overlooked?
The one use I could think of us to make your internal network
independent of your ISP. Right now, if you change ISPs, your network
prefix changes and your who
Christian Weisgerber wrote:
Kurt Mosiejczuk wrote:
And AES-128 (and only that flavor of AES, so far) has a crack making
decrypting it significantly quicker.
News to me. Reference?
(You are probably confusing this with the related-key attacks on
AES-192 and AES-256.)
That may be what
Ted Unangst wrote:
On Wed, Aug 29, 2012 at 16:34, Kurt Mosiejczuk wrote:
And I'm fairly certain blowfish did get a lot of attention. And since
bcrypt is reasonably popular, I'd imagine blowfish *still* gets
attention from the cryptographic community.
The security of bcrypt
Christian Weisgerber wrote:
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.
(careful, you trimmed out whe
Eric Oyen wrote:
> I tried the copy link option in the context menu for Safari. It
should have
> given the direct link but I got that instead. sometimes, being blind
can be a
> real Pain in the backside.
That's not your fault, that is Google (and everyone else) substituting
their own redirect
Jan Stary wrote:
On Jun 21 16:35:16, 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:
IMO tHe most valuable book is Kernighan & Ritchie "The C Programming
Language".
-Otto
+1
Brian Hechinger wrote:
On 6/8/2012 1:55 PM, Chris Smith wrote:
... if you really want a firewall you need pfSense.
Also if you " walk into any security experts convention and claim that
raw OpenBSD is "a firewall", you will get laughed out of the room for
lack of clue."
Guess I've been wro
Kevin Chadwick wrote:
On Wed, 30 May 2012 13:00:45 -0400
Kurt Mosiejczuk wrote:
That's also why spamd in greylisting stutters for the first 10 seconds.
Many spammers disconnect now when stuttered at, so they give up before
even starting the greylisting process.
It might be n
Jan Stary wrote:
Being a happy new user of spamd and friends (thank you Bob!),
I have a few nitpicking questions as I go through the manpages.
(1)
spamd whitelists a given host by _adding_ it as a whitelist entry;
the original GREY entry is left there. Why is is kept around, now
that the ho
Jan Stary wrote:
On May 29 22:22:35, Otto Moerbeek wrote:
Yes. Until the host is marked WHITE spamd will handle the connection
attempts from that host.
Yes, that's understood. But why does spamd talk like that
even on the very first connection attempt? (Not that it hurts
the greylisting pr
David Diggles wrote:
I am now trying it with -G120:6:864
Although I can't think how to reproduce the problem in a controlled way,
other than wait and see what emails I don't get :/
Stop playing with those settings, you are freaking out about log entries
that don't mean what you think they mea
Henning Brauer wrote:
* Harald Dunkel [2011-02-04 14:31]:
Is there some other way to avoid a lot of "keep state (no-sync)"
statements?
is there some other way to make people READ the fucking mnapages we
put so much effort in?
If you figure that out, I think you'll be a very rich man.
--Kur
Kevin Chadwick wrote:
On Fri, 4 Feb 2011 18:56:28 +0100
Henning Brauer wrote:
is there some other way to make people READ the fucking mnapages we
put so much effort in?
laser etcher + contact lens and super glue
I'm positive that that still won't work for some folks.
--Kurt
o, mine is a RT2561C not sure how different that may be from your
RT2561. I have not had such problems with mine.
--Kurt
--
Kurt Mosiejczuk
Software Engineering
Rochester Institute of Technology
70-1527
134 Lomb Memorial Drive
Rochester, New York 14623
585-475-5999
k...@se.rit.edu
CONFIDENTIAL
e* problems with a
mismatch.
--Kurt
--
Kurt Mosiejczuk
Software Engineering
Rochester Institute of Technology
70-1527
134 Lomb Memorial Drive
Rochester, New York 14623
585-475-5999
k...@se.rit.edu
CONFIDENTIALITY NOTE: The information transmitted, including
attachments, is intended only for the person(s
Dale Rahn wrote:
> Some apple machines have two different phys. Multiple phy support does not
> exist on OpenBSD
> mostly since it has nearly never been seen except for Apple systems.
> The second phy is ignored on these systems.
Okay, good to know. Thanks for the clarification.
--Kurt
Miod Vallat wrote:
>> G4 powermac (dmesg below) which has 4.7 (although it looks like the
>> drivers in this case haven't changed).
> gem(4) media support is limited by the PHY it is connected to. Your
> machine has a particular brgphy(4) model which can only do 100Mb/s and
> 1Gb/s.
> I have a ge
G4 powermac (dmesg below) which has 4.7 (although it looks like the
drivers in this case haven't changed).
Short version:
The gem manpage claims 10Mbit half-duplex (or full, but I didn't try
that), but it clearly does not. Why? No idea. I've done some cursory
looking through the files for gem a
Claudio Jeker wrote:
Not correct autoneg is only reliable when both sides are using autoneg.
Some switches (most notably the cizzzcooeee) disable autoneg if the port
is fixed to a speed below 1G or duplex mode. In that case you must fix the
other side as well.
So autoneg is unreliable if you a
STeve Andre' wrote:
Did you try just pressing a holding Fn for a few seconds? That's how
I've had to awake all the thinkpads I've used (granted, not OBSD).
I tried various things, including holding fn-f4 down for a minute.
Nothing makes any difference.
Not Fn-F4, but just Fn, by itself.
-
STeve Andre' wrote:
> Excellent idea. It doesn't do anything, however, so I came back
> on to write this.
>
> --STeve Andre'
Did you try just pressing a holding Fn for a few seconds? That's how
I've had to awake all the thinkpads I've used (granted, not OBSD).
--Kurt
Finally updated my console server that precipitated the original patch
and found 4.4 didn't work with the card. Turns out when my patch got
added, one digit was incorrect.
Here's a patch to fix.
--Kurt
Index: pcidevs
===
RCS fil
Bob Beck wrote:
There is a quasi standard perl script which I have posted and is
available
frequently referenced in the archives of this list, and has already been
mentioned
twice in this thread. it is not "standard" with OpenBSD because pieces of it
must be customized to be site spec
Bob Beck wrote:
This is the right solution for roaming users, and is why
I will *not* make spamd ever have a notion of sasl :)
It is also, exactly, what we do here. Our users use
port 587 for this, NOT port 25
Doing it this way also helps those users who have ISPs who block
53 matches
Mail list logo
