Re: BSDStats - What is involved ... ?

On Tue, Aug 29, 2006 at 11:39:23AM +1000, Antony Mawer wrote:
On 29/08/2006 6:07 AM, Marc G. Fournier wrote:
On Mon, 28 Aug 2006, Brooks Davis wrote:

While I understand (or think I understand) the motivations for this
design goal, it's contrary to allowing collection of statistics from
many people. I'd love to be able to publish data from the FreeBSD
systems (300+) at work, but unless I can do it in an anonymized
aggregate form it's not going to happen. I just can't justify leaking
that much internal configuration information given a policy of hiding
it (right or wrong and not subject to debate). If I could run my own
stats server and publish from it that might be possible.

Agreggate submissions will never be possible, as it will definitely
break any attempts at keeping the data 'clean' :( I do understand that
we will never be able to get *everyone* reporting, but we will try as
much as possible to make it easy for as many as possible to report
*within* limits ...

I'm going to work on an 'email submission' method in September, that
would allow repoting to go *thru* one mailbox, and will include a
confirmation/challenge stage *per* server though ...

Brooks, what sort of information are you looking to "anonymise" before
sending it out? Aggregating to say that I have X of this kind of CPU, Y
of this IDE chipset, etc, rather than linking it specifically to each
machine? Where would you feel a comfortable balance lay? Obviously some
effort needs to be made to minimise fraudulent entries

Perhaps aggregate submissions could be conducted using a registration
mechanism...

Other thoughts would be having a local stats aggregation server that
pushes summaries up to the master server... the aggregation server keeps
the individual details, and some sort of challenge mechanism could be
randomly selected by the master server to reduce the ease with which the
numbers can be 'faked'?

... just rambling as I thought of potential ways around this ...

I'd prefer not to expose host names or IP addresses, hardware
information and OS version aren't really a problem if they can't be
traced to a host name. The requirement to register an aggregation
server would be fine with me. A challenge mechanism would be tricky
because it would have to occur during a push to the central server since
connects back are not really possible.

-- Brooks

Attachment: pgp1pxhv0AD8L.pgp
Description: PGP signature

Relevant Pages

  • Re: AS 2000 Processor busy with no query or processing activity
    ... aggregation" is there anything else that could be causing it to do "lazy ... but during this background aggregation the server is slower. ... to occur after partitions are processed in several cubes. ... According to Performance Monitor "Analysis Server:Connection" ...
    (microsoft.public.sqlserver.olap)
  • Re: AS 2000 Processor busy with no query or processing activity
    ... the other place to find this option is to edit the cube himself. ... a lazy aggregation option will evaluate the aggregations of a partition ... but during this background aggregation the server is slower. ... According to Performance Monitor "Analysis Server:Connection" there ...
    (microsoft.public.sqlserver.olap)
  • Re: AS 2000 Processor busy with no query or processing activity
    ... the server is IDLE instead of evaluate the aggregation during the processing ... but during this background aggregation the server is slower. ... According to Performance Monitor "Analysis Server:Connection" there are ... Partition is currently being processed even though no processing is ...
    (microsoft.public.sqlserver.olap)
  • Re: AS 2000 Processor busy with no query or processing activity
    ... I checked the cube and on the advanced tab it is set to regular NOT to "lazy ... aggregation" is there anything else that could be causing it to do "lazy ... but during this background aggregation the server is slower. ...
    (microsoft.public.sqlserver.olap)
  • CSR: Exploitation Challenge
    ... Covertsystems Research is seeking submissions for the successful ... The server is a typical TCP/IP server with a vulnerable strcpy ...
    (Vuln-Dev)