Displaying 15 results from an estimated 15 matches for "chronox".
Did you mean:
chrono
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller <smueller at chronox.de> wrote:
> And finally, you have a coding error that is very very common but fatal when
> reading from /dev/random: you do not account for short reads which implies
> that your loop continues even in the case of short reads.
>
> Fix your code with something like the following:
&...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller <smueller at chronox.de> wrote:
> And finally, you have a coding error that is very very common but fatal when
> reading from /dev/random: you do not account for short reads which implies
> that your loop continues even in the case of short reads.
>
> Fix your code with something like the following:
&...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
Hi Alex,
> On Fri, 29 Jul 2016 12:24:27 +0200
>
> Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> > On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller
> >
> > <smueller at chronox.de> wrote:
> > > And finally, you have a coding error that is very very common but
> > > fatal when reading from /dev/random: you do not account for short
> > > reads which implies that your loop continues even in the case of
> > > short reads.
> > >...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
Hi Alex,
> On Fri, 29 Jul 2016 12:24:27 +0200
>
> Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> > On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller
> >
> > <smueller at chronox.de> wrote:
> > > And finally, you have a coding error that is very very common but
> > > fatal when reading from /dev/random: you do not account for short
> > > reads which implies that your loop continues even in the case of
> > > short reads.
> > >...
2004 Oct 20
1
throttle particular client ip
...''tag'' and ''throttle'' the
bandwidth to and from a particular client on my lan side. Better yet, I
just want to throttle smtp traffic, per say, for that ip.
----lan----------eth1-[linux.box]-eth0----------internet
I have used the technique provided by smueller@chronox.de and his
limit.conn-0.2 perl script, which basically does the following:
iptables --append PREROUTING --in-interface eth0 --table mangle \
--protocol tcp --source $SERVERIP \
--source-port $SERVERPORT --jump MARK --set-mark 0x1
tc qdisc add dev eth0 handle ffff: ingr...
2016 Jul 29
0
getrandom waits for a long time when /dev/random is insufficiently read from
On Fri, 29 Jul 2016 15:12:30 +0200
Stephan Mueller <smueller at chronox.de> wrote as excerpted:
> Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
> > In my opinion, assuming I am not doing something terribly wrong,
> > this constitutes a bug in the kernel's handling of getrandom calls
> > at boot, possibly only when the primary sou...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
Am Freitag, 29. Juli 2016, 10:14:07 CEST schrieb Alex Xu:
Hi Alex,
> On Fri, 29 Jul 2016 15:12:30 +0200
>
> Stephan Mueller <smueller at chronox.de> wrote as excerpted:
> > Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
> > > In my opinion, assuming I am not doing something terribly wrong,
> > > this constitutes a bug in the kernel's handling of getrandom calls
> > > at boot, possibly only...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
Am Freitag, 29. Juli 2016, 10:14:07 CEST schrieb Alex Xu:
Hi Alex,
> On Fri, 29 Jul 2016 15:12:30 +0200
>
> Stephan Mueller <smueller at chronox.de> wrote as excerpted:
> > Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
> > > In my opinion, assuming I am not doing something terribly wrong,
> > > this constitutes a bug in the kernel's handling of getrandom calls
> > > at boot, possibly only...
2016 Jul 29
0
getrandom waits for a long time when /dev/random is insufficiently read from
On Fri, 29 Jul 2016 12:24:27 +0200
Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller
> <smueller at chronox.de> wrote:
> > And finally, you have a coding error that is very very common but
> > fatal when reading from /dev/random: you do not account for short
> > reads which implies that your loop continues even in the case of
> > short reads.
> >
> > Fix your code w...
2016 Jul 29
0
getrandom waits for a long time when /dev/random is insufficiently read from
On Fri, 29 Jul 2016 19:03:51 +0200
Stephan Mueller <smueller at chronox.de> wrote as excerpted:
> Am Freitag, 29. Juli 2016, 10:14:07 CEST schrieb Alex Xu:
> > I don't follow. Assuming you are correct and this is the issue, then
> > reading 128 bits (16 bytes) from /dev/random should "exhaust the
> > supply" and then both reads fro...
2016 Jul 28
2
getrandom waits for a long time when /dev/random is insufficiently read from
Linux 4.6, also tried 4.7, qemu 2.6, using this C program:
#include <fcntl.h>
#include <stdlib.h>
#include <syscall.h>
#include <unistd.h>
int main(int argc, char *argv[]) {
char buf[16];
int fd;
if (argc != 2)
return 1;
for (int i = 0; i < atoi(argv[1]); i++) {
sleep(1);
if ((fd = open("/dev/random", O_RDONLY)) ==
2016 Jul 28
2
getrandom waits for a long time when /dev/random is insufficiently read from
Linux 4.6, also tried 4.7, qemu 2.6, using this C program:
#include <fcntl.h>
#include <stdlib.h>
#include <syscall.h>
#include <unistd.h>
int main(int argc, char *argv[]) {
char buf[16];
int fd;
if (argc != 2)
return 1;
for (int i = 0; i < atoi(argv[1]); i++) {
sleep(1);
if ((fd = open("/dev/random", O_RDONLY)) ==
2005 Jan 20
4
Hardware solution? (or v.easy software fix instead)
...roperly yet.
Here are some links to scripts and the like I found in order of interest:
http://www.smidsrod.no/products/firewall/supershaper/
http://www.metamorpher.de/fairnat/
#complex but hopeful:
http://www.digriz.org.uk/jdg-qos-script/#howitworks
http://users.skynet.be/cbqinit/
http://www.chronox.de/tc+filter/limit.conn-0.2.bz2
http://www.freenet.org.nz/python/pyshaper/#screenshot
#proxy based limiter:
http://www.stewart.com.au/ip_relay/
#comphrehensive:
http://bwm-tools.pr.linuxrulz.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mai...
2016 Jul 29
0
getrandom waits for a long time when /dev/random is insufficiently read from
Am Donnerstag, 28. Juli 2016, 18:07:32 CEST schrieb Alex Xu:
Hi Alex,
> Linux 4.6, also tried 4.7, qemu 2.6, using this C program:
I am not sure what problem you are referring to, but that is an expected
behavior.
You get partial reads when reading from /dev/random with a minimum of 64
bits. On the other hand getrandom(2) is woken up after the input_pool
received 128 bits of entropy.
In
2006 Jun 11
1
Quotas and LDAP
Hi,
first of all, it is very nice that dovecot has quotas now! Thank you very
much.
Now, I want to use quotas with LDAP requests, but I am having the following
issues.
First, contrary to what is written in the Wiki about quota and LDAP ("#
quotaStorage must be in the format mentioned above, # For example:
dirsize:storage=10240"), it is possible to have an LDAP field with just a