essage, according to the
video of Ken Westerback's presentation)? Or maybe use the MSNoAutoMount
attribute to undo the effects of the Required one with regard to spoofing?
Philippe
eb.netbsd.org/bsdweb.cgi/src/sys/arch/i386/include/vmparam.h?only_with_tag=MAIN
(MAXTSIZ currently is 128 MB on FreeBSD.)
Philippe
Anyone?
Philippe
Philippe Meunier wrote:
>Jonathan Gray wrote:
>>MAXTSIZ is 128 MB on i386
>>see sys/arch/i386/include/vmparam.h
>
>Mark Kettenis wrote:
>>sys/arch/i386/include/vmparam.h has:
>>#define MAXTSIZ (128*1024*1024) /* max text size */
below? I've checked with a new kernel that it
fixes the problem with chrome (even when using the default limits in
/etc/login.conf).
Philippe
Index: sys/arch/i386/include/vmparam.h
===
RCS file: /cvs/src/sys/arch/i386/include/vmpar
Philippe Meunier wrote:
>Is there some kind of limitation on the size of an ELF executable that can
>be executed on i386? I mean, in addition to the limits in /etc/login.conf?
When using readelf(1) on the chrome executable from
chromium-81.0.4044.138.tgz from OpenBSD 6.7-release i386 packa
se (with syspatches applied; dmesg below).
I just upgraded from 6.7-release which is when I found out about this
problem with chrome. On 6.7 I had datasize-max, datasize-cur, and
memoryuse set to 1024M in /etc/login.conf and never had any problem using
chrome.
Any idea what the problem might be?
Be
Mark Kettenis wrote:
>I have to think through the consequences of simply doing a delay
>without checking the condition here though.
Ping?
Philippe
s to wait for one vblank
but does not when "cold" is 1. So that's where I think "if (cold) {
delay(tick); return; }" ought to be, and then there would be no need to
worry about __wait_event_intr_timeout's condition or about vblank
interrupts. I'm not the one who has to merge that code with the Linux code
though :-)
Philippe
\
atomic_inc_int(&(wq).count);\
It's ad-hoc but it's simple. My DAC timing problem that makes the console
resolution wrong is fixed with about a 2 microseconds delay, so one tick of
delay is plenty enough time to make the thing
Philippe Meunier wrote:
>Mark Kettenis wrote:
>>Does the diff below fix things?
>
>Yes, it fixes the console resolution problem, although a bunch of "vblank
>wait timed out on crtc 0" messages now show up (see dmesg's output below).
How about the patch below? I
Mark Kettenis wrote:
>Does the diff below fix things?
Yes, it fixes the console resolution problem, although a bunch of "vblank
wait timed out on crtc 0" messages now show up (see dmesg's output below).
Philippe
OpenBSD 6.4-beta (GENERIC) #5: Tue Aug 14 22:20
ts" into
the shape of a mathematical pretzel is not helpful. If anything, it's GNU
dc that needs to be changed. Anyway, I'm done with this topic.
Philippe
ated note, is this:
$ dc
16o16i
FFZp
supposed to print 2 or 3?
Philippe
didn't show up
before reading your patch...)
Philippe
ist of variables comma-separated instead
of space-separated, so that the intent is clearer from the syntax?
Cheers,
Philippe
look at it today but you
beat me to it :-)
Philippe
t
value that is more likely to work for everyone? Something like
https://www.un.org/ for example.
Cheers,
Philippe
While trying to make a fresh install with the from the Oct 12th miniroot58.fs,
while installing the sets I get a bunch of:
tar: Unable to set file uid/gid of ./blah/blah: Operation not permitted
tar: Unable to set file uid/gid of ./...: Operation not permitted
tar: Unable to set file uid/gid of ./
SIGINFO is awesome, but it's even better when it actually does
something relevant.
This makes it print the total counts so far to stderr.
Useful? Feature creep? You decide.
Index: wc.c
===
RCS file: /cvs/src/usr.bin/wc/wc.c,v
retri
On Thu, Jun 25, 2015 at 07:01:29AM +, Pavel Plamenov wrote:
> There are some leftover links to www@, which is gone.
I sent an almost identical diff over a year ago:
https://www.marc.info/?l=openbsd-misc&m=139627200904849&w=2
I think this is the right direction.
This adds a -p option to pkg_info to show the PackageRepositorys
being used.
Inspired by trying to parse /etc/pkg.conf with some awk and quickly
realized that was the wrong way to solve my problem. I then wrote
some perl that reached into OpenBSD:: internals, but concluded it'd
be much cleaner for
This is no longer used anywhere, and even crashes if you try to call it.
Besides, OpenBSD::PackageRepository::Source was removed almost a year ago.
Index: PackageRepositoryList.pm
===
RCS file: /cvs/src/usr.sbin/pkg_add/OpenBSD/Packag
The idea was to print the package repository used followed by the stuff
found in it, but that doesn't work:
$ pkg_info -vQ foo
Use of uninitialized value $ENV{"PKG_PATH"} in concatenation (.) or string at
/usr/libdata/perl5/OpenBSD/PkgInfo.pm line 604.
PKG_PATH=
foo2zjs-20140627
foobilla
I now realize this may have been ignored simply because the clock
on the sending machine was horribly off and many people sort mail
by date. So... Should this go in? Am I missing something?
On Thu, Apr 30, 2015 at 06:03:23PM -0400, Jean-Philippe Ouellet wrote:
> The intermediate values calcula
On Sat, Jun 20, 2015 at 03:01:18PM +0200, Reyk Floeter wrote:
> there is some great interest in getting support for rewrites
What do people think of something like our tftpd(8)'s -r
-r socket
Issue filename rewrite requests to the specified UNIX domain
socket. tftpd will wri
The overhead is somewhat high, and it's considered broken anyway:
https://www.acsac.org/2012/openconf/modules/request.php?module=oc_proceedings&action=view.php&a=Accept&id=237&type=4
P.S. Sorry for breaking threading, my mail setup is currently a mess.
The intermediate values calculated in hmac_sha1 as part of
pkcs5_pbkdf2 are not zeroed afterwards, so we leak a single-hashed
version of the key on the stack in tk[].
Also, the correct RFC defining this is
RFC 2104 - HMAC: Keyed-Hashing for Message Authentication
not
RFC 2202 - Test Cases
POSIX says the truncated things are "record(s)" not "block(s)":
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/dd.html
That's what it's historically been too:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/cmd/dd.c
http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Reno/src/bi
Thanks for making my day :)
I actually propose the following instead:
Index: rand.c
===
RCS file: /cvs/src/lib/libc/stdlib/rand.c,v
retrieving revision 1.10
diff -u -p -r1.10 rand.c
--- rand.c 1 Aug 2013 19:42:08 - 1.
Found these lurking earlier.
I looked for things depending on them and didn't find any,
maybe they were just missed in the giant tedu?
Index: libexec/login_passwd/common.h
===
RCS file: /cvs/src/libexec/login_passwd/common.h,v
retri
Hello,
Finally found some free time.
What would you think of making the "Which disk is the root disk?"
question default to the first softraid device you have configured,
if any.
The thinking is if you bothered to actually configure a softraid
device, it's probably because you actually intend to
We use "async-signal-safe" (not "async-signal safe") elsewhere,
and so does POSIX.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/sigaction.html
Index: sigaction.2
===
RCS file: /cvs/src/lib/libc/sys/sigaction.2,v
retriev
ious
versions, I just made sure it still built and that build built itself
too.
Capsicum is still blocking on this patch (or one like it).
Any/all feedback welcome.
On Thu, Jul 10, 2014 at 04:13:38PM -0400, Jean-Philippe Ouellet wrote:
> This diff adds another struct between filedesc a
Ping?
On Sun, Jul 13, 2014 at 03:45:44PM -0400, Jean-Philippe Ouellet wrote:
> Updated for mallocarray() and free(size).
>
> On Thu, Jul 10, 2014 at 04:13:38PM -0400, Jean-Philippe Ouellet wrote:
> > This diff adds another struct between filedesc and file to store
> &
On Mon, Jul 21, 2014 at 06:59:12AM +, Doug Hogan wrote:
> -objects and checks for arithmetic overflow.
> +objects and calls
> +.Xr panic 9
> +on arithmetic overflow.
That is misleading in the M_CANFAIL case.
I'm not terribly good at wording things, but I suggest something
more like this inst
On Wed, Jul 16, 2014 at 01:56:00PM -0500, patric conant wrote:
> Isn't there a responsibility to disclose that, and possibly remove it
> from base.
It's being removed.
> ... you use it to get a list of mirrors for your newly installed system,
> so you can set the pkg_path. I'd love it if we inclu
For the cases where it's more than just nitems * sizeof(item),
maybe it wouldn't be a bad idea to have something like:
static __inline int
MULT_OVERFLOWS(int x, int y)
{
const intmax_t max = 1UL << sizeof(size_t) * 4;
return ((x >= max || y >= max) && x > 0 && SIZE_MAX / x < y);
}
On Mon, Jul 14, 2014 at 11:44:30AM -0400, Jean-Philippe Ouellet wrote:
> The C standard mandates that static be first.
Of course I forgot something... This is the hunk that made me
notice in the first place. Found while porting signify to osx.
Index: lib/libc/hash/sha
The C standard mandates that static be first.
>From ISO/IEC 9899:1999 and 9899:201x,
6.11.5 - Storage-class specifiers:
The placement of a storage-class specifier other than at the
beginning of the declaration specifiers in a declaration is
an obsolescent feature.
and -Wextra complain
It takes a void *, not a char *.
Index: getentropy.2
===
RCS file: /cvs/src/lib/libc/sys/getentropy.2,v
retrieving revision 1.4
diff -u -p -r1.4 getentropy.2
--- getentropy.215 Jun 2014 07:24:19 - 1.4
+++ getentropy.2
Updated for mallocarray() and free(size).
On Thu, Jul 10, 2014 at 04:13:38PM -0400, Jean-Philippe Ouellet wrote:
> This diff adds another struct between filedesc and file to store
> process-local per-descriptor information. Currently, the only thing in
> this struct is the file pointer
And some cosmetic things:
> Index: ic/malo.c
> - ring->data = malloc(count * sizeof (struct malo_rx_data), M_DEVBUF,
> - M_NOWAIT);
> + ring->data = mallocarray(count, sizeof (struct malo_rx_data),
> + M_DEVBUF, M_NOWAIT);
Might as well s/sizeof (/sizeof(/ while you're her
On Sun, Jul 13, 2014 at 11:29:22AM -0600, dera...@cvs.openbsd.org wrote:
> - ldp = malloc(sizeof(*ldp) + (k-1), M_DEVBUF, M_NOWAIT);
> + ldp = mallocarray(k-1, sizeof(*ldp), M_DEVBUF, M_NOWAIT);
Are you sure k-1 can never be small enough such that a*b is less than a+b?
On Sun, Jul 13, 2014 at 04:03:53PM +0200, Brent Cook wrote:
> On Jul 13, 2014, at 3:58 PM, Ted Unangst wrote:
> > @@ -411,6 +404,9 @@ static long
> > random_l(void)
> > {
> > int32_t i;
> > +
> > + if (use_arc4random)
> > + return arc4random() & 0x7fff;
>
> return arc4random()
This diff adds another struct between filedesc and file to store
process-local per-descriptor information. Currently, the only thing in
this struct is the file pointer and some flags, however I have another
patch on top of this that adds capsicum capabilities to it. (And
another that uses mallocarr
On Thu, Jul 10, 2014 at 12:02:40PM -0700, Matthew Dempsky wrote:
> -.Fn malloc "unsigned long size" "int type" "int flags"
> +.Fn malloc "size_t size" "int type" "int flags"
> +.Ft void *
> +.Fn malloc "size_t nmemb" "size_t size" "int type" "int flags"
2nd one should be mallocarray.
Those 4 memcpy()s are copying the things referenced by the old
filedesc to the new one. The things being copied are file*s,
not file**s. They're the same size anyway, but still...
Index: sys/kern/kern_descrip.c
===
RCS file: /cvs/sr
Hi,
When assigning mount points to an already-partitioned disk
without a its fstab handy, it's annoying to type the partition
letters one after another. (And sing the alphabet each time or
look at the output of 'p' for letters after 'f'. I blame hex.)
I could go back to preeschool and learn the al
Eww...
See distrib/notes/mirrors and installpath from pkg.conf(5).
On Wed, Jun 04, 2014 at 08:02:06PM +, Miod Vallat wrote:
> > First, str{cat,cpy} were vehemently expunged from the kernel many years ago,
> > so stop trying to keep them around.
> >
> > Index: lib/libc/Makefile.inc
>
> Hello, this is libc you are butchering in. I'm afraid strcat and strcpy
>
Hello,
This came up when I was looking for the proper place to put code for dealing
with capsicum data structures which need to be handled by both userland and
the kernel.
FreeBSD's libc build system has tentacles that reach over and grab
sys/kern/subr_capability.c. That's not very elegant, I lik
On 26/05/14(Mon) 13:46, Martin Pieuchot wrote:
> I'd appreciate if people having troubles with suspend/resume could try
> this diff an report back.
Fixes it for me! :D
Many thanks.
> Previous diff was lacking the header chunk, please use this one instead.
Was the corresponding commit missing the
Found while trying to figure out how to be sure the console is always
cleared at logout (and the resulting login prompt seemed like a pretty
guaranteed-to-always-work place). If you have a cleaner way, perhaps
one that is actually at logout and doesn't involve missing all the
startup messages due t
> todd, can you put this in snaps so that we know if there's some fallout?
I don't know if this is related or not, but running that snap I experienced
the following crash while trying to shut down: (which I've never had before)
http://i.imgur.com/4YFzdv0.jpg
http://i.imgur.com/KR1hWtT.jpg
http://
There are a bunch of nearby printfs which start with ": ..." without
a devname. I'm not sure which one is preferred, so here's both ways.
Index: ehci_cardbus.c
===
RCS file: /cvs/src/sys/dev/cardbus/ehci_cardbus.c,v
retrieving revisi
On Mon, May 05, 2014 at 07:31:34PM +1000, Joel Sing wrote:
> > This one is calloc, not reallocarray, so unless I'm seriously missing
> > something obvious here, it is indeed zero'd, no?
>
> Run the following before and after your change:
Ah, yep. Can't believe I missed that (along with all the ot
On Mon, May 05, 2014 at 11:12:00AM +1000, Joel Sing wrote:
> > - i = 0;
> > if (arg->count == 0) {
> > arg->count = 20;
> > - arg->data = (char **)malloc(sizeof(char *) * arg->count);
> > + arg->data = calloc(arg->count, sizeof(char *));
> > }
> > - for (
On Sun, May 04, 2014 at 11:30:40PM +0200, Alexander Hall wrote:
> NULL theoretically could be != 0
Umm... short of something like:
#undef NULL
#define NULL "I'm silly and want to break everything"
or something, I don't see when that'd be the case.
According to ISO/IEC 9899:1999 TC3 (n1256
On Sun, May 04, 2014 at 12:17:16PM -0600, Theo de Raadt wrote:
> We are going to completely ignore diffs which change multiple idioms
> at once.
Okay.
> That is how mistakes get made.
Yep, more true than I realized.
Here's a simpler one:
Index: apps.c
=
Hello,
I've gone through lib/libssl/src/apps with the goal of making {m,c,re}alloc
uses more idiomatic, adding error checking in some places where missing,
and some minor style unification.
Feedback appreciated, better patches to come after the semester ends.
Index: apps.c
=
Hello,
When building libcrypto on amd64 I get this warning:
(cd /usr/src/lib/libcrypto/crypto/../../libssl/src/crypto/md5 ; /usr/bin/perl
./asm/md5-x86_64.pl openbsd-elf) > md5-x86_64.S
Use of uninitialized value $output in pattern match (m//) at
./asm/md5-x86_64.pl line 115.
Admittedly it's
This doesn't fix the problems, only removes markers alerting us to audit it.
Memory management in these files is still missing integer overflow checks,
NULL return checks, and is full of crazy abominations like:
X509_NAME *
parse_name(char *subject, long chtype, int multirdn)
{
size_t buf
Here's another pass.
This replaces RAND_{,pseudo_}bytes() calls with equivelant arc4random_buf(3)
calls for apps/ and ssl/ (crypto/ still has a bunch).
There was one that was commented out (in ssl/s3_pkt.c) which I wasn't sure
about, so I made the accoring transformation and left it commented out
Hi,
Here's more fuel for the OpenSSL fire. Mostly just axeing at ifdefs,
trying to err on the conservitive side.
There's obviously *TONS* more to clean up, but I only had so much time
tonight. :)
BTW, libssl and libcrypto don't currently build because their Makefiles
still include some recently
Thank you very much for the feedback.
On 3/14/14 9:38 AM, Ingo Schwarze wrote:
> According to the sigaction(3) manual, "volatile sig_atomic_t" would
> be better. If i understand correctly, overzealous compilers might
> otherwise optimize checks away.
Dammit, of course. I should have caught that.
On 3/13/14 3:18 AM, Loganaden Velvindron wrote:
> On 3/13/14 10:57 AM, Jean-Philippe Ouellet wrote:
>> On 3/13/14 2:39 AM, Loganaden Velvindron wrote:
>>> I'm not a mentor, but I'd be happy to help you in any way I can.
>>> You can send mails to tech@ for testi
On 3/13/14 2:39 AM, Loganaden Velvindron wrote:
> I'm not a mentor, but I'd be happy to help you in any way I can.
> You can send mails to tech@ for testing your diffs.
Any chance you'd like to review my bootloader patch from last month then?
http://marc.info/?l=openbsd-tech&m=139408992902933
I
On 3/12/14 11:15 PM, Loganaden Velvindron wrote:
> I've read about the file vulnerability, and capsicumization also
> came to mind. However, there was also a discussion when i was
> playing with capsicum and openssh, about the limits of capsicum.
> Capsicum doesn't prevent DoS, and we still need rl
On Wed, Mar 12, 2014 at 11:09:14PM +0100, Ingo Schwarze wrote:
> I don't really like the warnx(3) call from the bye() ALRM handler
> either, but that's a separate matter.
Me neither.
Maybe something like this instead? (although maybe the done check should
be someplace else?)
Index: lock.c
==
On 3/12/14 4:58 AM, tuchalia wrote:
> Should l try to port also the Casper daemon to OpenBSD, or
> only work in the kernel implementation?
Based on more private mail, I figured it'd be a good idea to make what I
plan to work on public in case there are others interested so we can
avoid stepping o
Hello,
When lock(1) receives SIGINT, SIGQUIT, or SIGTSTP, it calls hi()
twice, once because it's the signal handler, and once after
readpassphrase() errors because the read was interrupted.
Since hi() gets called when readpassphrase() fails anyway, this
patch ignores the signals instead of using
On 3/12/14 4:58 AM, tuchalia wrote:
> Also, do we have any IRC channel to discuss al this?
I've been wondering about that too, although I was never really active
on any of the channels.
Mindcry is dead, subcult is mostly non-english, freenode and efnet are
mostly whiners. I vaguely remember some
On 3/12/14 4:58 AM, tuchalia wrote:
> Hi all,
>
> I'm really interested in this possibility of porting the Capsicum framework
> to OpenBSD. Should l try to port also the Casper daemon to OpenBSD, or
> only work in the kernel implementation?
>
> I've used Capsicum during the last summer, but I on
n the multiboot FAQ that if you're
booting with the windows bootloader and you get an error message like
that to re-get openbsd.pbr to the windows side.
Hello Bob,
I agree, until I found that (With help from Kenneth), it was not obvious
to understand/fix my problem.
Regards,
Jean-Phili
Le 2014-03-07 11:21, Stuart Henderson a écrit :
On 2014/03/07 11:04, Jean-Philippe Luiggi wrote:
Hi everybody,
I follow "-current" for several years but recently a thing puzzles me.
My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and sinc
I used that setup for several years without any need to do that, what do I
miss here, is it now normal ?
Regards,
Jean-Philippe.
--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
For all your IT requirements visit: http://www.transtec.co.uk
could do
it, but I'm not sure what the cleanest approach would be. Any feedback
is much appreciated.
Original message with patch:
http://marc.info/?l=openbsd-tech&m=139208386213686&q=raw
On 2/10/14 8:57 PM, Jean-Philippe Ouellet wrote:
> Hello,
>
> I patched the sparc64 b
On 3/5/14 3:30 PM, Ted Unangst wrote:
> On Wed, Mar 05, 2014 at 16:15, Giancarlo Razzolini wrote:
>> Hi,
>>
>> I have one linux server that has full disk encryption, and I use
>> it's initramfs with dropbear to be able to remote unlock the encrypted
>> root partition.
>>
>> From what I read
Here's some documentation of it for www/
I think there should also be some mention of this functionality in
diskless(8), but I don't know where to put it, and I don't want to
just .Xr it to boot_sparc64 because diskless is for all archs and
none of the other boot_*s are referenced.
Index: sparc64
Hello,
While hacking on the sparc64 bootloader (patch in another mail) I
had some questions about the recently added super-early entropy
loading code.
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/sparc64/stand/ofwboot/boot.c.diff?r1=1.19;r2=1.20
>From the commit message:
"Try to load e
Hello,
I patched the sparc64 bootloader to allow users to manually specify
network config and where to load the kernel from via openfirmware
parameters instead of always requiring rarp/bootparams/bootp.
This enables remote bootstrapping of semi-recent sun boxes (like
the T1000) on networks where
It appeared in revision 1.3 ("Update from lite2.")
It's the only one in the string family that has it, and nothing from it
is used.
Index: strsep.c
===
RCS file: /cvs/src/lib/libc/string/strsep.c,v
retrieving revision 1.6
diff -u -p
them...)
>Does something like this work for you?
>
>interface "em0" {
> request subnet-mask, broadcast-address, routers, domain-name-servers;
>}
>
>interface "em1" {
> request subnet-mask, broadcast-address, routers;
>}
This would work if dhclient were using a "default deny" policy.
Unfortunately it doesn't, so your suggestion doesn't work.
Philippe
ent.conf to change it to explicitly request all the basic
options (though sysmerge could easily take care of that one-time
change) but I think it just would be cleaner and clearer to have the
default requested options listed explicitly in the default
/etc/dhclient.conf rather than to have them hard coded and buried in
clparse.c. Maybe it's just me :-)
Anyway, food for thoughts.
Philippe
A few days ago I saw a commit for NSD, I had never heard of it before,
so naturally, I went to read the manpage, however it wasn't there. I
looked at the cvs tree, and saw that there was a manpage, just not
formatted for mandoc like all other manpages I've seen in OpenBSD, so I
read up on mdoc
A and RLIMIT_STACK. Is there a better way
to approximate RLIMIT_AS?
Thanks a lot,
Philippe
Si vous ne pouvez pas lire cet email, suivre ce lien
(http://front.datafnxjune25.com/php/emailing/view_mail.php?CODE=586BBGXG_416219&HASH=df0fe6426bc7f9674e80137ab1433bd7)
Untitled Document
Fini les traveaux compliquis
(http://www.keltravo.com/?prt=c68af80669a4eaf631fae6da
You are seeing this message in Text format. if your email is in the junk
folder, add the sender email to your address book and move this email into your
inbox to view the HTML version.
Ce message contient des images, si elles ne s'affichent pas correctement,
cliquez ici,
Fini les traveaux compliquis
Entreprendre des travaux chez soi est compliqui et fastidieux !
Je pourrais laisser faire un professionnelâ¦
Mais qui ?!
Laissez nous faire
Comment savoir
si je peux lui faire c
Ce message contient des images, si elles ne s'affichent pas correctement,
cliquez ici,
Unsuscribe, here.
Fini les traveaux compliquis
Entreprendre des travaux chez soi est compliqui et fastidieux !
Je pourrais laisser faire un professionnelâ¦
Mais qui ?!
Laissez nous faire
Comment savoir
si j
Ce message contient des images, si elles ne s'affichent pas correctement,
cliquez ici,
Unsuscribe, here.
Devis-Avis.com
Energies renouvelables : ` quel prix ?
Economisez jusquâ` 45% en cridit dâimptt
Riduisez votre facture de 50%
Empruntez ` taux 0% (eco-prjt)
Aides et subventions rigionales
91 matches
Mail list logo
