On 01/02/2013 09:14 PM, Damian Menscher wrote:
Back on topic: encryption without knowing who you're talking to is worse
than useless (hence no self-signed certs which provide a false sense of
security),
In fact, it's very useful -- what do you think the initial diffie-hellman
exchanges are
On Wed, Jan 02, 2013 at 05:00:14PM +0100, Axel Pawlik wrote:
To prevent the automatic harvesting of personal information (real
names, email addresses, phone numbers) from the RIPE Database, there
are PERSON and ROLE object query limits defined in the RIPE Database
Acceptable Use Policy. This
On Thu, Jan 3, 2013 at 12:14 AM, Damian Menscher dam...@google.com wrote:
Back on topic: encryption without knowing who you're talking to is worse
than useless (hence no self-signed certs which provide a false sense of
security), and there are usability difficulties with exposing strong
Hello!
I'm looking for a contact in Akamai, preferably someone dwelling in the
dark realm of layer 3.
I've been contacted by a LACNIC member from Suriname who is having
reachability issues specifically with sites hosted in Akamai.
Thank you!
~Carlos
On 2012-12-18, at 11:15, David Conrad d...@virtualized.org wrote:
WRT the root _hints_ change, setting up a cron job to pull, verify, and
install the root hints file periodically (once a month should probably be
sufficient) would probably be a good idea.
This change appears to have been
On Jan 3, 2013, at 11:38 AM, Joe Abley wrote:
On 2012-12-18, at 11:15, David Conrad d...@virtualized.org wrote:
WRT the root _hints_ change, setting up a cron job to pull, verify, and
install the root hints file periodically (once a month should probably be
sufficient) would probably be a
Hi Henry,
On 2013-01-03, at 13:29, Henry Steuart hsteu...@alliedtelecom.net wrote:
Perhaps someone at internic.net could explain why the file in the first
directory is WRONG but that in the second includes the correct info?
[legacy cron jobs pointing at FTP. will obviously not succeed]
;
I'm looking for a contact in Level3, regarding a client who is having
reachability issues with a few sites in the East coast of the US and Asia
(sites are reachable via Level3 on the West Coast).
Thanks
Ram
On Thu, 3 Jan 2013, Ram Mohan wrote:
I'm looking for a contact in Level3, regarding a client who is having
reachability issues with a few sites in the East coast of the US and Asia
(sites are reachable via Level3 on the West Coast).
Has the client contacted Level3's NOC? That would seem to
On Thu, Jan 3, 2013 at 4:59 AM, Damian Menscher dam...@google.com wrote:
While I'm writing, I'll also point out that the Diginotar hack which came
up in this discussion as an example of why CAs can't be trusted was
discovered due to a feature of Google's Chrome browser when a cert was
On Jan 3, 2013, at 3:52 PM, Matthias Leisi matth...@leisi.net wrote:
On Thu, Jan 3, 2013 at 4:59 AM, Damian Menscher dam...@google.com wrote:
While I'm writing, I'll also point out that the Diginotar hack which came
up in this discussion as an example of why CAs can't be trusted was
other relevant links for this:
http://krebsonsecurity.com/2013/01/turkish-govt-enabled-phishers-to-spoof-google/
http://technet.microsoft.com/en-us/security/advisory/2798897
On Thu, Jan 3, 2013 at 4:25 PM, Steven Bellovin s...@cs.columbia.edu wrote:
On Jan 3, 2013, at 3:52 PM, Matthias Leisi
Yo All!
Apropos the recent discussions:
Google says that someone was caught trying to use an unauthorized
digital certificate issued in its name in an attempt to impersonate
Google.com for a man-in-the-middle attack.
http://www.wired.com/threatlevel/2013/01/google-fraudulent-certificate/
RGDS
On 1/3/13, Maxim Khitrov m...@mxcrypt.com wrote:
On Thu, Jan 3, 2013 at 12:14 AM, Damian Menscher dam...@google.com wrote:
I talked to Google Apps support a few weeks ago, sent them a link to
this discussion, but all they could do is file a feature request.
I am not sure why this would be
On 1/3/2013 9:08 PM, Jimmy Hess wrote:
I am not sure why this would be classified as a feature request. If it
is impacting you, and you had service before, then is an
Outage/Defect/Bug, full stop. Describing working service for a
previously supported scenario as a feature request would be
15 matches
Mail list logo
