As you may know, the jump from NetWorker 7.3 to 7.4 saw the introduction of a language\/locale-neutral log format in NetWorker, referred to as “raw” format. The primary purpose of this format is to allow logs to be generated by NetWorker that can then be rendered into a support-addressable language for EMC.<\/p>\n
One of the options for nsr_render_log is “-z”, which according to the man page:<\/p>\n
-z\u00a0\u00a0 Obfuscate secure information. Hostnames, usernames and network\n addresses shall be aliased.<\/pre>\nIn theory, this replaces hostnames with neutral hostnames – e.g., the backup server gets renamed to ‘host1’.<\/p>\n
If you’re relying on nsr_render_log to totally<\/em> mask your site details, don’t<\/em><\/strong>. You still need to manually review the file and determine whether there are any references to hostnames, usernames, etc., that need to be modified.<\/p>\n
Here’s a few examples of where details aren’t aliased:<\/p>\n
\n
- Index paths in initial startup of the NetWorker server.<\/li>\n
- License count details in initial startup of the NetWorker server.<\/li>\n
- Entries of the form client:Saveset Name<\/em> when referencing savesets starting, stopping, etc. This includes the server hostname, which “-z” mainly seems to be trying to masquerade (e.g., you’ll get lines like: ‘host1 nsrd cerberus:index:mars’).<\/li>\n
- The infamous “NSR peer information”<\/a> entries.<\/li>\n
- Usernames from browsing for browsing recoveries and completing recoveries.<\/li>\n<\/ul>\n
While I don’t normally like to poke sticks at NetWorker, this isn’t a good implementation of security. Security by obfuscation never is, but if you say you’re going to hide hostnames and usernames, you should at least make every effort to do just that. In fact, using the Australian vernacular, this is a very half arsed<\/em> implementation of an advertised feature.<\/p>\n
In short, if you’re needing to completely “secure” your daemon.raw output before sending to your support provider, don’t<\/em> rely on -z, but instead do a manual search and replace.<\/p>\n
As a starting point, you may want to consider a procedure such as:<\/p>\n
\n
- Using nsradmin, extract a list of all client names.<\/li>\n
- Search and replace each client name with an arbitrary name in the daemon.raw file.<\/li>\n
- Search for “done browsing” and extract the unique usernames.<\/li>\n
- Map those unique usernames to arbitrary usernames, and search and replace in the daemon.raw file.<\/li>\n<\/ol>\n
That will not likely replace everything<\/em>, but will give you a good starting point.<\/p>\n","protected":false},"excerpt":{"rendered":"
As you may know, the jump from NetWorker 7.3 to 7.4 saw the introduction of a language\/locale-neutral log format in…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[16,21],"tags":[682],"class_list":["post-507","post","type-post","status-publish","format-standard","hentry","category-networker","category-security","tag-nsr_render_log"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t