Health Insurance Claim Number (HICN) Validator for pre-15.5 via Custom Script?

I need a solution

Hello all,

I was curious if anyone has implemented effective HICN detection in DLP versions prior to 15.5? I know that 15.5 contains a Data Identifier for HICN, which contains an HICN-specific validator that “computes the checksum and validates the pattern against it.” However, I have a deployment on 15.0.1, and we likely won’t be able to upgrade for another year or so.

Has anyone had success implementing a Custom Script validator that can calculate the checksum and validate the pattern against it?

I realize this is a long-shot, but I wanted to throw it out there.

Thanks!

Nick

0

Related:

  • No Related Posts

Re: CERT file is broken in 4.4.0 OVA

The Unity Simulator OVA is broken. On the top line of the .cert file, you’ll see this text:

SHA1(unfinished11186_OS-c4dev_PIE_2893R-4.4.0.1534750794.1534763221-VVNX_OVA_RETAIL.mf)= ab18b6c2c08122f262da52afdcb4f02bebd6f7bb180909c2530352e75e8e03ae7f61fbac41136ad6f2b12e3bea90d26d1df0b3e55990ecead30da97b8a82f95b2dffbf74887c6e81273dc5b97c60d13e021eac89927eca2c89fbd58adf64ea8ddf9063ac8ae8da0841dfbce83f4705596215dd5a0390f261a40fca363b1adc9be594a1a7cba18c7c0b4093e62ad829bb227c24c5ce2e9c7d1418908c9e31ddd7f6d25db656196e39570fd6e1fe27ceeace766d1bc989413b707330970c5b53f129ef05b65afd5a210daf473809e5b0a1c29e1cd78276e927c16278f6fb8ecad927c9c1fd8f7310e7099a189330bbd669e604cf3417d109a4abb1ce9af7dc1421

There are 2 problems with this:

1. That’s way too long to be a sha1 checksum of the manifest file. (and indeed it’s not)

2. Look at the file name… it’s probably from some mid-level build, not a final release. (the folder is even called unfinished).

If you fix that line in the cert file, then it won’t validate out. If you remove the cert file, and re-compile the now un-signed OVA you have to use the “–allowExtraConfig” switch with ovftool to get Humpty-dumpty put back together again.

~Chris

Related:

  • No Related Posts

CERT file is broken in 4.4.0 OVA

The Unity Simulator OVA is broken. On the top line of the .cert file, you’ll see this text:

SHA1(unfinished11186_OS-c4dev_PIE_2893R-4.4.0.1534750794.1534763221-VVNX_OVA_RETAIL.mf)= ab18b6c2c08122f262da52afdcb4f02bebd6f7bb180909c2530352e75e8e03ae7f61fbac41136ad6f2b12e3bea90d26d1df0b3e55990ecead30da97b8a82f95b2dffbf74887c6e81273dc5b97c60d13e021eac89927eca2c89fbd58adf64ea8ddf9063ac8ae8da0841dfbce83f4705596215dd5a0390f261a40fca363b1adc9be594a1a7cba18c7c0b4093e62ad829bb227c24c5ce2e9c7d1418908c9e31ddd7f6d25db656196e39570fd6e1fe27ceeace766d1bc989413b707330970c5b53f129ef05b65afd5a210daf473809e5b0a1c29e1cd78276e927c16278f6fb8ecad927c9c1fd8f7310e7099a189330bbd669e604cf3417d109a4abb1ce9af7dc1421

There are 2 problems with this:

1. That’s way too long to be a sha1 checksum of the manifest file. (and indeed it’s not)

2. Look at the file name… it’s probably from some mid-level build, not a final release. (the folder is even called unfinished).

If you fix that line in the cert file, then it won’t validate out. If you remove the cert file, and re-compile the now un-signed OVA you have to use the “–allowExtraConfig” switch with ovftool to get Humpty-dumpty put back together again.

~Chris

Related:

  • No Related Posts

VxRail: How to check checksum on downloaded upgrade package in Windows

Article Number:496951

Article Title and Link for Registered Users: VxRail: How to check checksum on downloaded upgrade package in Windows

Affected Product(s): VxRail Appliance Family

Article Summary:1. Goto support.emc.com to locate the upgrade package to be downloaded. 2. Click on the checksum link to generate the checksum for the file. 3. Examine the checksum value. May need to copy it and paste it elsewhere (notepad) if the full checksum value is not …

Article Last Updated:March 06, 2017

Please note that this abstract is machine-generated. Registered users should click the above link to view the entire knowledge article from Dell EMC Online Support, otherwise please contact Dell EMC Customer Service for further assistance.

Related:

Re: RMAN Restore from Clone volume

Thanks for the replies. nsr_recover_pool did not work for me, getting an error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

We could not read the checksum. (0:3:0)

Using file ‘l0_19sii72r_1_1’ as an example. It’s not listed in the output of nsrinfo but is listed by mminfo

ausdwburr2210.ausrr2cdd03.ccrclone.01 austldbengdb07 11/2/2017 64 MB manual RMAN:l0_19sii72r_1_1

[oracle@austldbengdb07 /home/oracle]

$ rman target /

connected to target database: PATDB (DBID=3097235999, not open)

RMAN> run {

allocate channel ch1 type ‘SBT_TAPE’ parms ‘ENV=(NSR_SERVER=ausdwburr2210,NSR_CLIENT=austldbengdb07.us.dell.com,NSR_RECOVER_POOL=ccrclone)’;

restore database from TAG=’PATDB_FULLDB_20171102′;

release channel ch1;

3> }4> 5> 6> 7> 8> 9> 10> 11>

using target database control file instead of recovery catalog

allocated channel: ch1

channel ch1: SID=1147 instance=patdb1 device type=SBT_TAPE

channel ch1: NMDA Oracle v8.2.4

……..

Starting restore at 11/13/2017 02:15:56

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00004 to +DATA_1/PATDB/DATAFILE/undotbs1.306.959207061

channel ch1: reading from backup piece l0_19sii72r_1_1

………

channel ch1: ORA-27192: skgfcls: sbtclose2 returned error – failed to close file

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

We could not read the checksum. (0:3:2)

ORA-19870: error while restoring backup piece l0_19sii72r_1_1

ORA-19501: read error on file “l0_19sii72r_1_1”, block number 1 (block size=512)

ORA-27190: skgfrd: sbtread2 returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

asdf_read

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00001 to +DATA_1/PATDB/DATAFILE/system.319.959207061

channel ch1: reading from backup piece l0_17sii72q_1_1

channel ch1: ORA-27192: skgfcls: sbtclose2 returned error – failed to close file

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

We could not read the checksum. (0:3:0)

ORA-19870: error while restoring backup piece l0_17sii72q_1_1

ORA-19501: read error on file “l0_17sii72q_1_1”, block number 1 (block size=512)

ORA-27190: skgfrd: sbtread2 returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

asdf_read

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00002 to +DATA_1/PATDB/DATAFILE/sysaux.267.959207061

channel ch1: reading from backup piece l0_16sii72q_1_1

channel ch1: ORA-27192: skgfcls: sbtclose2 returned error – failed to close file

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

We could not read the checksum. (0:3:0)

ORA-19870: error while restoring backup piece l0_16sii72q_1_1

ORA-19501: read error on file “l0_16sii72q_1_1”, block number 1 (block size=512)

ORA-27190: skgfrd: sbtread2 returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

asdf_read

……..

failover to previous backup

released channel: ch1

….

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 11/13/2017 02:21:48

RMAN-06026: some targets not found – aborting restore

RMAN-06023: no backup or copy of datafile 6 found to restore

RMAN-06023: no backup or copy of datafile 5 found to restore

RMAN-06023: no backup or copy of datafile 4 found to restore

RMAN-06023: no backup or copy of datafile 3 found to restore

RMAN-06023: no backup or copy of datafile 2 found to restore

RMAN-06023: no backup or copy of datafile 1 found to restore

Related:

How can I fix this spnego error “major code: 11, minor code: 0 received checksum does not match computed checksum”?

How can I fix this spnego error “major code: 11, minor code: 0 received checksum does not match computed checksum”?

======================
9/18/17 20:21:16:030 CDT] 00000081 SystemOut O [JGSS_DBG_CTX] Error authenticating request.

Reporting to client Major code = 11, Minor code = 0

org.ietf.jgss.GSSException, major code: 11, minor code: 0

major string: General failure, unspecified at GSSAPI level

minor string: Kerberos error while decoding and verifying
token: com.ibm.security.krb5.internal.crypto.KrbCryptoException, status code: 0

message: Checksum error; received checksum does not match computed checksum

======================

Related: