linux operating commands and unix operating commands

Update on (ISC)2 Erroneous Exam Notifications


 
Thread Tools Search this Thread
# 1  
Old 11-25-2010
Update on (ISC)2 Erroneous Exam Notifications

24 November, 2010 - 4:30 pm

As we head into a long holiday weekend in the US, I want to let you know that we continue our outreach to candidates affected by the erroneous exam results notices. Please know that while our corporate office will be closed on Thanksgiving Day, Customer Service Advisors in our US office will be available to assist you Friday and through the weekend, from 8 a.m. to 4 p.m. Nov. 26-28. Of course, normal business hours will resume on Monday, Nov. 29. Our London and Hong Kong offices will have standard business hours, 8 a.m. to 5 p.m., Monday through Friday. Don't hesitate to contact us if there's anything we can do to assist you.

For more information, see http://blog.isc2.org/isc2_blog/exam-results.html

Image
Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Erroneous file concatenation.

I have more than one files in a directory , namely GLOW_OUT.txt FIELD_OUT.txt BASE_OUT.txt ... SHOW_OUT.txt What I wanted to do is to I am working in Korn Shell What I did was : for file in <directory_name>/*.* ;do cat $file | grep -v '^$' >> temp_file rm $file done ... (7 Replies)
Discussion started by: kumarjt
7 Replies

2. Programming

erroneous output

#include<stdio.h> int main () { FILE* f_read; FILE* f_write; char *string; f_read=fopen("file1","r"); while(!feof(f_read)); { fscanf(f_read,"%s",string); fprintf(stdout,"%s\n",string); ... (2 Replies)
Discussion started by: bishweshwar
2 Replies

3. UNIX for Dummies Questions & Answers

Deleting a File with an Erroneous Period

Hi - I am new to the Unix environment and have encountered a problem I can't resolve. I inadvertently created a data file with a period/dot at the end of the word 'dat', I.e. filename.dat. and can't remove it using the 'rm' command. In attempting to do so, I receive a message reading that the... (3 Replies)
Discussion started by: PLF
3 Replies
Login or Register to Ask a Question
ISC-HMAC-FIXUP(8)						       BIND9							 ISC-HMAC-FIXUP(8)

NAME
isc-hmac-fixup - fixes HMAC keys generated by older versions of BIND SYNOPSIS
isc-hmac-fixup {algorithm} {secret} DESCRIPTION
Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the hash algorithm (i.e., SHA1 keys longer than 160 bits, SHA256 keys longer than 256 bits, etc) to be used incorrectly, generating a message authentication code that was incompatible with other DNS implementations. This bug has been fixed in BIND 9.7. However, the fix may cause incompatibility between older and newer versions of BIND, when using long keys. isc-hmac-fixup modifies those keys to restore compatibility. To modify a key, run isc-hmac-fixup and specify the key's algorithm and secret on the command line. If the secret is longer than the digest length of the algorithm (64 bytes for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a new secret will be generated consisting of a hash digest of the old secret. (If the secret did not require conversion, then it will be printed without modification.) SECURITY CONSIDERATIONS
Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in operation anyway, it does not affect security. RFC 2104 notes, "Keys longer than [the digest length] are acceptable but the extra length would not significantly increase the function strength." SEE ALSO
BIND 9 Administrator Reference Manual, RFC 2104. AUTHOR
Internet Systems Consortium COPYRIGHT
Copyright (C) 2010, 2013 Internet Systems Consortium, Inc. ("ISC") BIND9 January 5, 2010 ISC-HMAC-FIXUP(8)