On Tue, Aug 26, 2014, Dawe wrote:
Otherwise it works fine for me with .fit files from my Sigma ROX 10.0 GPS
exported from the Sigma datacenter software.
It works with srm files, csv files (from Joule/Poweragent - I
couldn't get direct downloading to work -- yet), hrm files from
Polar (with
On Sun, Aug 31, 2014, Dawe wrote:
I don't have any experience with train mode, does it make sense without video
support?
Yes. It shows real-time data if you use a USB ANT+ stick.
So which of the suggested alternatives (fdm, sieved, ???) have
undergone a security audit or at least can claim that no problems
were found when using some of those fuzzing tools?
Before switching from procmail to something else it would be
nice to know if that alternative is (more) secure.
On Thu, Jun 18, 2015, Christian Weisgerber wrote:
sendmail TLS/DH Interoperability Improvement
https://www.freebsd.org/security/advisories/FreeBSD-EN-15:08.sendmail.asc
AFAIK that advisory is being revised...
Simply use '2' or your own dhparams (the latter is preferred).
A new sendmail
On Thu, May 21, 2015, Peter van Oord van der Vlies wrote:
When receiving mail i sometimes get this error when sendmail is configured
with starttls.
STARTTLS=server, error: accept failed=-1, reason=no shared cipher,
receiving
On Fri, May 22, 2015, Peter van Oord van der Vlies wrote:
2015-05-22 3:29 GMT+02:00 Claus Assmann openbsd+po...@esmtp.org:
STARTTLS=server, error: accept failed=-1, reason=no shared cipher,
receiving mail from which
On Wed, Mar 09, 2016, Jeremie Courreges-Anglas wrote:
> Claus, in the future would it be possible to prefix the patch file names
> with "sendmail-"? It would be a bit safer for us, as we would not have
Do you mean the patch on the sendmail.org FTP server? That naming
scheme is used for about
FYI (I haven't seen this in ports yet):
If sendmail tried to reuse an SMTP session which had already been
closed by the server, then the connection cache could have invalid
information about the session. One possible consequence was that
STARTTLS was not used even if offered.
The problem can be
On Mon, Jan 30, 2017, Jeremie Courreges-Anglas wrote:
> I just want to stress that "FFR" means "For Future Releases".
> Generally I don't think we should enable experimental features just
> because we can, and I can't see why EC would be different here.
It is a "non-FFR" compile time option in
On Sat, Oct 15, 2016, Otto Moerbeek wrote:
> On Sat, Oct 15, 2016 at 11:59:05AM -0700, Claus Assmann wrote:
> > #0 0x178ecfe55d8a in _thread_sys___syscall () at :2
> > #1 0x178ecfe4662a in *_libc_mmap (addr=Variable "addr" is not
> > available.
> &g
Maybe someone can give me a hint how to fix/handle this problem:
GoldenCheetah crashes on OpenBSD 6.0 (amd64) when compiled against
Qt5 (installed from ports). I currently have a working version on
OpenBSD 5.3 (i386) compiled against Qt4 (from ports), but an upgrade
is a bit overdue...
$ gdb
[wxallowed as mount option solved W^X violation abort in 6.0i,
but not 6.2]
On Mon, Dec 04, 2017, Rafael Sadowski wrote:
> Looks like you built GoldenCheetah from scratch outside the ports env.
Yes; I build SW "just out of the box" (because I build the same
SW on various OSs -- and a port of
Back in OpenBSD 6.0 running the program from /usr/local which has
wxallowed as mount option solved this problem:
On Sat, Oct 15, 2016, Otto Moerbeek wrote:
> On Sat, Oct 15, 2016 at 11:59:05AM -0700, Claus Assmann wrote:
> > #2 0x178e9dc67db7 in WTF::OSAllocator::reserve
> cloudfront.net
Just for completeness: those are mozilla.net names, so I blocked
that too.
Thanks again for the hints/help!
--
Address is valid for this mailing list only.
On Sun, Oct 20, 2019, Johnathan M. wrote:
> https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections
Thanks, I followed all of those instructions and FF is still making
the connections. I found out that those to AWS are actually for hostnames
in mozilla.com and
Can someone point in me in the right direction how to prevent firefox
from making lots of unwanted network connections, e.g., to
amazonaws.com
cloudfront.net
even if I didn't open any website yet?
I disabled "pingsender" and all "telemetry" options I could find,
and in OpenBSD 6.5 I simply used
On Thu, Jan 23, 2020, Landry Breuil wrote:
> Since 72 was backported to stable pledge config/overrides isnt in
> about:config prefs anymore but in /etc/firefox, have a look at the
> pkg-readme provided by the package.
I didn't find a hint about pkg-readmes in the man pages :-(
(I also ran
I really appreciate your work of providing upgraded pkgs via -stable;
for the user having to change something is a much smaller "problem"
than having a pkg with a security problem.
Maybe just add a (upgrade) note to the pkg_info output about
incompatibilities?
Thanks!
--
Address is valid for
Sorry if I missed something, but the last info I found on this
was to set these two options to avoid the problem:
$ fgrep pledge prefs.js
user_pref("security.sandbox.pledge.content", "moo");
user_pref("security.sandbox.pledge.main", "moo");
I also tried to set it to "", but that doesn't help
On Fri, Jan 24, 2020, Ingo Schwarze wrote:
> Claus Assmann wrote on Fri, Jan 24, 2020 at 09:25:27AM +0100:
> > I didn't find a hint about pkg-readmes in the man pages :-(
>$ man -k any=pkg-readmes
Two mails to the openbsd lists and I learned three new things :-)
I only trie
I'm probably doing something wrong, but just in case:
these warnings where displayed when I ran
make
in ports/net/isc-bind/
configure: WARNING: unrecognized options: --enable-filter-,
--enable-threads, --with-randomdev, --disable-silent-rules, --disable-gtk-doc
Maybe those options are used
Please note that there is a double-free bug in 3.2.0
related to DANE - maybe wait until this is fixed?
See the openssl-users mailing list or
https://github.com/openssl/openssl/pull/22821
On Thu, Jan 31, 2019, Stuart Henderson wrote:
> security/openssl/1.1/patches: patch-Configurations_10-main_conf
> patch-Configurations_shared-info_pl
> Unbreaks i386.
Is it "ok" for OpenSSL to include these patches
or is there a license problem?
--
23 matches
Mail list logo
