Welcome to Smokey's Security Forums.
Guests have only limited access to the board and it's features, please consider registering to gain full access!
Registration is free and it only takes a few moments to complete.

Smokey's Security Forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

Sony recalls VAIO F11 and CW2 Series : Burn hazard

Sony has issued a recall for its F11 and CW2 series notebook PCs and is offering a firmware update to fix an overheating problem.

Burn hazard: Sony recalls VAIO F11 and CW2 Series

Multilingual OTL (OldTimer ListIt) Log Analysis * Multilingual OTL Tutorials * OTL Downloads * Malware Removal * Microsoft Security Info & Alert Center * Official Jetico Inc. Support Forums

Share this topic on FacebookShare this topic on MySpaceShare this topic on Del.icio.usShare this topic on DiggShare this topic on RedditShare this topic on StumbleUponShare this topic on TwitterAuthorTopic: Running BCArchive command prompt wise.  (Read 1378 times)

0 Members and 1 Guest are viewing this topic.

Jetico

  • Jetico Support Engineer
  • *
  • Offline Offline
  • Posts: 673
Re: Running BCArchive command prompt wise.
« Reply #5 on: October 02, 2008, 12:44:31 PM »
As you want to create archive encrypted with a password, you should not use -PKID key.
But in that case, you certainly have to enter the password each time you add anything to the archive.

The other case - if you create archive encrypted with a public key.
In that case, you do not enter the password when you create the archive - instead, you provide BCArchive
with a public key existing in the local database.
The users who open the EXE file, will get the same "Enter password" message, but with the additional field -
"use secret key" - and it is needed to point to the location of the secret key file. This location will be remembered, and
the next time only the password is required.

It seems to me that the second way is more convenient for you and for your users.

As for the error "cannot load BCKeyMan", I have a supposition.
Did you move the executable file BCArchive.exe?
If yes, you should move "BCKeyMan.dll" to the same folder where the EXE resides.
 

* Permissions
You can't post new topics.
You can't post replies.
You can't post attachments.
You can't modify your posts.
BBCode Enabled
Smilies Enabled
[img] Enabled
HTML Disabled


Except where otherwise stated, all content © 2006 - 2010 Smokey Services™ -- All rights reserved
Design of all board graphics, banners and images by Emma aka Tinker - © 2006 - 2010 Smokey Services™ -- All rights reserved

Security Knowledge-, Alert- & News Center and Comprehensive Microsoft Windows Information & Download Center
Board- and databases search functions and the download of post attachments are only available to registered board members

    

  

Smokey's Security Forums provide full qualified OTL Log Analysis & Cleaning Services in English, German and Spanish language
OTL (OldTimer ListIt) is a flexible, multipurpose, diagnostic, and malware removal tool, it also has some curative ability

Microsoft Security Info & Alert Center: all released Microsoft Security Bulletins, Alerts, Advisories and Vulnerabilities, in real-time