Forum Replies Created

Viewing 8 posts - 1 through 9 (of 9 total)

  • RE: SQL + PGP = head aching

    Note that for FIPS compliance, you can't just use PGP, you need to insure that all the PGP keys and/or configurations are set to only use FIPS compliant algorithms. ...

  • RE: SQL + PGP = head aching

    Some great suggestions here guys, its a great help. I have a workshop with the client in a few days. It seems there is indeed more than one...

  • RE: SQL + PGP = head aching

    Hey,

    Has anyone got any further suggestions for this solution?

  • RE: SQL + PGP = head aching

    Either of the first 2 works, if you dont specify a location it assumes the root directory to place the encrypted file, and the 3rd one is fine

  • RE: SQL + PGP = head aching

    itll create a file, there are other switches for what to do with the file incase of duplicates:

    pgp --decrypt report.doc.pgp --symmetric-passphrase Pa55w0rd --overwrite remove

  • RE: SQL + PGP = head aching

    I just spoke to another PGP Consultant to had another way of doing it:

    Website passes record to PGP -> Encrypts -> passes back to website -> Website inserts into database

    Just...

  • RE: SQL + PGP = head aching

    Ok really simple stuff:

    pgp --encrypt report.doc --passphrase Pa55w0rd report.doc:encrypt (0:output file report.doc.pgp)

    pgp --decrypt report.doc.pgp --passphrase Pa55w0rd

    That will be enough to get the script working from a PGP point of view,...

  • RE: SQL + PGP = head aching

    Lowell (6/20/2012)


    it sounds like you are looking for a CLR which can encrypt/decrypt a file to disk using PGP;

    my Google-Fu pointed me to this thread from 2007 about SecureBlackbox ,...

Viewing 8 posts - 1 through 9 (of 9 total)