Results 1 ... 21 found in all logged channels for 'alert key'
(asciilifeform) asciilifeform: quite reminiscent of the case with the old prb 'alert key'.
(trilema) asciilifeform: already turned up a buncha oddities re noades -- for instance, just about errybody not-trb still sends out gavinalert (with 'key compromised!' message. wai -- i have nfi )
(trilema) Framedragger: (what if it's a station key? what if you wanted to be alerted of 'key stolen!')
(trilema) asciilifeform: !~later tell ben_vulpes the alert messages said 'URGENT: Alert key compromised, upgrade required.' iirc this was part of prb's scheduled retirement of the alert crapola.
(trilema) jurov: "errors" : "URGENT: Alert key compromised, upgrade required" lmao power rangers leaked?
(trilema) asciilifeform: 'Gavin will "win" because most people won't even realize there was a debate, let alone a "war". Gavin has the network alert key, so when he says "please upgrade to avoid being left on a fork", most people will upgrade. Hard to get away from that. Mircea Popescu isn't likely to persuade anyone that he's right because in all of the three blog posts on this subject I found, nowhere does he bother to explain why he's opposed to a larger
(trilema) mircea_popescu: <asciilifeform> or, if all else fails, the original gavinalert key. << not acceptable, been shared.
(trilema) ben_vulpes: <asciilifeform> gavin & the merry band of shitgnomes used their magic key to transmit 'Warning: This version is obsolete, upgrade required!' << 'alerts' can be delivered per-node?
(trilema) BingoBoingo: jurov: Commenting out that section of main.cpp you highlighted and making a junk public alert key turned into a build of 0.8.6 that's been running fine for about 20 hours nao
(trilema) BingoBoingo: jurov: I'm fucking around on 0.8.6 two lines in alert.cpp in that version possess public keys for verifying "Upgrade Alerts". My gut is telling me that changing the public keys to garbage is going to be the quick dirty way to effectively neuter the alert system in the build. Figure each time I build change the garbage subbing for pubkeys.
(trilema) assbot: Logged on 20-12-2014 03:34:37; decimation: http://www.nextgov.com/cybersecurity/2014/12/opm-alerts-feds-second-background-check-breach/101622/ << "The Office of Personnel Management is alerting more than 48,000 federal employees their personal information may have been exposed following a breach at KeyPoint Government Solutions, which conducts background investigations of federal employees seeking security clearances."
(trilema) decimation: http://www.nextgov.com/cybersecurity/2014/12/opm-alerts-feds-second-background-check-breach/101622/ << "The Office of Personnel Management is alerting more than 48,000 federal employees their personal information may have been exposed following a breach at KeyPoint Government Solutions, which conducts background investigations of federal employees seeking security clearances."
(trilema) Naphex: asciilifeform: so did you remove the fork alerts as well or just the alert-keying system?
(trilema) asciilifeform: exercise for the (very) alert reader: come up with a scheme where you can prove the actual number of distinct shareholders, given their pubkeys (allowed to assume they aren't all sockpuppets)
(trilema) davout: Stardust: a system designed to monitor a defined data-set in order to : ensure data integrity, enforce arbitrary business rules on it, ensure data stability over time, issue customizable alerts, generate customizable reporting and authenticate to operators using public key cryptography