Inspecting an old copy of sendbug.c:
fprintf(fp, "From: %s\n", pw->pw_name);
fprintf(fp, "Cc: %s\n", pw->pw_name);
fprintf(fp, "Reply-To: %s\n", pw->pw_name);
You might want to consider updating your record in your /etc/passwd file?
Thanks,
--
Raul
On Mon, Mar 16, 2020 at 9:10 AM Demi M. Oben
On Wed, Jul 27, 2016 at 8:00 AM, Paul Fariello wrote:
> Ok. I didn't notice that relayd had a security filtering focus. If so,
> enforcing presence/absence of body is legit.
Perhaps the security.html page on the openbsd site would interest you?
Did you know, for example, that openbsd has a "Secur
Reading the documentation on fparseln (and the underlying fgetln) as
well as on strsep, I see two potentially fatal errors in that code. I
stopped trying after noticing the second issue.
If you can spot one of them, and feel you are unable to spot the
other, please email me (off list) with the one
On Thu, Dec 17, 2015 at 2:33 PM, Kyle Amon wrote:
> An IP address can't get "resolved" by a nameserver. It is a
> nameserver's resolution terminus. But this is weird, so I'm open to
> suggestions on proper terminology. Converted, perhaps?
Well... in RFC 1035, domain names could not be numeric.
On Wed, Jan 13, 2016 at 3:21 PM, John Spencer
wrote:
> the following ISO C conforming program is broken on latest OpenBSD:
>
> #include
> int close() { puts("XXX"); return 0;}
> int main() { fclose(stdout); return 0;}
>
> the program is expected to not produce any output, however on OpenBSD it
>
On Fri, Mar 18, 2016 at 2:27 PM, Ted Unangst wrote:
> unicode support is incomplete.
This is, necessarily, always the case.
--
Raul
On Wed, Aug 19, 2015 at 3:15 PM, Witold Cichoń wrote:
>> You need a bypass flow to go with this 0.0.0.0/0 entry.
>
> Any advice how to do that?
Use flow bypass in ipsecadm?
--
Raul
On Wed, Aug 19, 2015 at 3:15 PM, Witold Cichoń wrote:
> I'm sorry, I missed sentence:
>
>> You need a bypass f
On Fri, Aug 28, 2015 at 4:25 PM, Mark Kettenis wrote:
>> From: Theo de Raadt
>> Date: Fri, 28 Aug 2015 13:50:57 -0600
>>
>> > > ktrace reveals that it's doing a wakeup every half second to
>> > > stat and probe each terminal and process group. My opinion is
>> > > that while the status bar update
On Wed, Sep 20, 2017 at 5:52 PM, Marc Espie wrote:
> On Wed, Sep 20, 2017 at 09:21:53PM +0200, Ingo Schwarze wrote:
>> So, apart from being safer for weird devices on weird implementations,
>> POSIX clearly recommends the idiom for symmetry with read(2) and
>> for compatibility with some historic
search.cpan.org/~shay/perl-5.26.1/lib/File/Copy.pm suggests
perlmonks.org though the search.cpan.org/~shay/ email address might
also be good,
Good luck,
--
Raul
On Thu, Nov 2, 2017 at 11:39 AM, Christian Weisgerber
wrote:
> Not sure who to report this to...
>
> Perl's File::Copy::move has a bu
poll(2) introduces a requirement to distinguish between reads and
writes of normal priority data and of high priority data. It then goes
on to say that the meaning of this distinction is device specific.
select(2) makes no such distinction.
socket(2) makes no such distinction.
The poll(2) manual
Ok, thanks, that was something which I did not understand.
So... perhaps the paragraph where poll(2) mentions significance should
read like this?
.Pp
The design of poll was adapted from STREAMS (IEEE Std 1003.1).
Typically, in OpenBSD, POLLIN indicates that read(2) may be used
without blocking, w
So... let's say I'm writing code that uses poll.
What would I need to read to discover whether POLLRDBAND is relevant
or not, to my coding effort?
Thanks,
--
Raul
On Tue, Feb 17, 2015 at 5:47 PM, Todd C. Miller
wrote:
> I think this is more accurate.
>
> - todd
>
> Index: lib/libc/sys/poll.2
On Tue, Feb 17, 2015 at 9:43 PM, Todd C. Miller
wrote:
> On Tue, 17 Feb 2015 19:34:35 -0500, Raul Miller wrote:
>
>> So... let's say I'm writing code that uses poll.
>>
>> What would I need to read to discover whether POLLRDBAND is relevant
>> or not, to
It's not safe to assume that "Local Redirect Response" is the only
valid use of the Location header.
--
Raul
On Sat, Mar 11, 2017 at 5:22 AM, wrote:
>>Synopsis: httpd/slowcgi not RFC compliant w.r.t. Local Redirect Response
>>Category: user
>>Environment:
> System : Open
On Tue, Sep 20, 2022 at 10:06 AM Alton Shaw wrote:
> I don't know it this is the same thing but I opened Firefox's console ...
The network inspector should be a tab in the console.
That said, I believe network errors should show up in the console.
That said, it's entirely possible that the mess
On Sun, Jan 22, 2023 at 9:02 AM Sören Tempel wrote:
> While this program works for the input "foo" it does (just like
> my original program) also terminate on the input "foo1" since
> the buffer is, once again, empty when the EOF is received. However, POSIX
> mandates that read(2) should only retu
This is a hardware issue.
Hardware failure is best guarded against using redundant systems.
Since random errors tend to lead to different outcomes, machines which
agree on what they were told would be the ones which did not
experience hardware failure.
Personally, I'd recommend 5x redundancy for
18 matches
Mail list logo
