I need code signing?

Similar Questions

• Code signing keys can be used on more than a developer (different PC)?

  Hello

  I applied for a set of code a long time ago signing keys.

  I installed them on the JDE on my computer... and I was able to migrate them to my new computer always on the JDE, then on the eJDE thereafter.  I had a few problems of migration of these keys, but everything is working well now, I am able to sign my application.

  Now, I have a colleague who wants to develop an application using Widgets and there need code signing keys as well.  Can I just send my key itself?  Or he must apply to his own set of keys?

  In other words, the code signing keys used to identify a company or developer?

  Thank you!

  Each developer must have their own set of BlackBerry Code signing keys.  Sharing the key is against the license agreement.

• Code signing

  I developed an application that needs code signing (uses SQLite functions), but unlike other positions, I found that I can't run on the Simulator. I have a ControlledAccessException. (application) refused permission to "files". Any help would be appreciated.

  (I use the Torch 9800 Simulator using the Java plug-in)

  I kept looking and found a response from mark in a different thread.

  http://supportforums.BlackBerry.com/T5/Java-development/app-throws-ControlledAccessException-but-ONL...

• Code sign VISA raw driver USB for Windows 8

  Hi guys,.

  I wrote a LabVIEW program that communicates with a measuring using NI-VISA (class raw USB) USB device.
  With the development of Driver NI-VISA Wizard, I created two .inf files of drivers (for XP/2000 and 7/Vista).
  It works like a charm on my computer (Windows 7, 64-bit) and on the computers running Windows XP and 32-bit versions of Windows Vista and 7.
  I also have to work on 64 bit versions of Windows Vista and 7 using "disable driver signature enforcement" before installing the driver.
  Once the driver is installed, it is listed under "devices USB of NI-VISA" in the Windows Device Manager. After that I can reactivate the driver signature enforcement, the unit will continue to work, even after a reboot.

  Alas, in the 64-bit version of Windows 8 is not as simple as that. Yes, you can temporarily disable driver signing enforcement, but not on computers that use 'secure boot' or UEFI.
  I know that there are ways to disable booting UEFI's secure, but I don't want that on our customers computers. It seems wrong, and could introduce a large number of security problems.

  The next logical step would be to sign the device driver. Our company has a valid kernel mode code signing certificate and we signed the other drivers with it in the past.
  The problem is that I don't know how to sign my device in the NI-VISA database driver. According to the .inf file it uses WinUSB.sys, a Microsoft USB generic driver (part of the Windows Driver Kit, I think).
  Winusb.sys is already signed by Microsoft and that I could replace the signature, but that probably won't work without some tweaking inf and generate a new catalog file.

  Can someone please give me some pointers on where to start? As a reference, I have attached one of the inf files for this post. This inf file works on Windows Vista and 7.

  It is even possible to create a signed driver based on NI-VISA raw?

  Thanks in advance for your help.

  Paul

  Here's a knockout who described workaround.

  http://digital.NI.com/public.nsf/allkb/36DB8D6AC385052786257A940066A421

  What you have written, you need to generate a catalog (.cat) of the inf file (as described in step 1 of the KB) and then sign the .cat with your certificate file, the same way you would sign your other components. The inf and CAT are always distributed together. The inf file contains information about the cat file that has the signature, and the cat file contains the signature information. Since you have already been distributing the components signed with your own certificate, I'm sure you can understand the process, but please let us know if you have any other questions.

  Thank you

  Pankaj

• Process * \MCSHIELD. EXE the nest (428) contained code signed or corrupted and could not perform an operation with a McAfee driver.

  XP SP3 system

  I get warnings like this when Mcafee updates.

  Process * \MCSHIELD. EXE the nest (428) contained code signed or corrupted and could not perform an operation with a McAfee driver.

  Process * \SVCHOST. EXE the nest (1632) contained code signed or corrupted and could not perform an operation with a McAfee driver.

  Is this a problem Microsoft or Mcafee?

  Do I need to fix?

  In the McAfee forums, there are several similar positions such as:

  https://community.McAfee.com/message/241542

  I'll sue your question on in their community, as they already seem to know about it.

  I would also say that, unless you are very fond of McAfee or you are forced to use it, you plan to replace it with something that has a smaller footprint, uses less resources and doesn't have these problems - something like Microsoft Security Essentials, you can get here:

  http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download

  MSE completed with the free version of MBAM and SAS should permanently keep your clean enough unless you're a daredevil like me:

  Download, install, update and do a quick scan with these free malware detection programs (not at the same time) and remove all threats:

  Malwarebytes (MMFA): http://www.malwarebytes.org/products/malwarebytes_free
  SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

  SAS will probably report a lot of tracking cookies and you can just let him delete them.

  Even if you keep McAfee, I always supplement it with MBAM and SAS since no single AV program does seem to know everything.  If your McAfee of your system is clean, I would interpret that means - McAfee found nothing, says he knows.  It is prudent to use more than a reputable scanner to get more coverage.

  If you choose to spend (and you can't have both at the same time), you must be sure to use the uninstaller that you can get from here:

  http://service.McAfee.com/FAQDocument.aspx?LC=1033&ID=TS101331

  Your system will give you better performance.

• Reuse of code signing on more than one computer keys

  Hello

  I'm moving my code signing keys to a machine with JDE 4.2.1 to another computer running JDE 4.1.0.

  Is this possible?  I copied my files sigtool.csk and sigtool.db.  But, when I try to sign a .cod file, it gives me an error of password - and I know that the password is correct.

  Of course, I could generate a new key pair and pay $20 to get signature for her keys, but I should be able to copy my keys autour, right?

  Someone else has been able to copy successfully their signature on another key machine?  I need to downgrade from JDE 4.2.1 to 4.1.0 - keys are not backward compatible through JDE versions and their corresponding SignatureTool.jar?

  Help, please!  :-)

  Using signature on several PC keys is not supported.  If you want to move your signing keys from one PC to another, you can contact [email protected] who can send you a set of replacement of csi files, that you can install on the new PC.  Note that this process invalidates your keys.

• Signature without using Code code signing authority of signatory to basic password file

  I'm trying to restrict access to a store of PersistentObject using code signing. I created the public/private key pair and I also have my. KEY file. When I do following step it work very well:

  • Sign your application using your code signing key standard issued by Research In Motion.
  • Sign that these signed .cod files with the application file signatory in the administration of BlackBerry signature tool.

  But I want to design a signature tool automated using ant tasks.  I am unable to find corresponding Ant task to call the file signing tool.

  Anyone know how to get the code signing to work without using the JDE?

  Thanks in advance

  you need a server to use this signature signature. AFAIK, you sign your apps as before, just with your own signature added server.

• BlackBerry - lost password code signing

  Could someone recover password lost for the signatory to the code? The PDF provides links to a support email where nobody has the faintest idea how to do that?

  No chance, someone of you found any help on the site of bb or service customer? It has been a month since I've been chasing these people for one simple password reset question.

  This is an old thread... but since it's one of the first results in a Google search, I wanted to bring an answer here.

  It is not possible to recover your password for BlackBerry Code signing keys.  However, you can choose a new if you reinstall your keys.  The first thing you need to do is to order a new set of keys (free) using the form below.

  https://www.BlackBerry.com/SignedKeys/

  Before installing your keys, find and delete the files below that will be present in the various BlackBerry development tools installation directories (location varies by tool).

  sigtool.DB

  sigtool. CSK

  sigtool. Set

  You will now be able to install your new CSI files and choose a new password.

• I forgot the password of the Code signing key

  Hi, I got the signature key (csk file) by registering on blackberry, but for some reason, I forgot my password... When I try to sign my code it ask me password... I googled a lot to find a way to recover my password, but no avail... Can someone please tell me how to recover my password for the key signature or any other way that i can reset my password... Any kind of help would be appreciated... Thanks in advance...

  This is an old thread... but since it's one of the first results in a Google search, I wanted to bring an answer here.

  It is not possible to recover your password for BlackBerry Code signing keys.  However, you can choose a new if you reinstall your keys.  The first thing you need to do is to order a new set of keys (free) using the form below.

  https://www.BlackBerry.com/SignedKeys/

  Before installing your keys, find and delete the files below that will be present in the various BlackBerry development tools installation directories (location varies by tool).

  sigtool.DB

  sigtool. CSK

  sigtool. Set

  You will now be able to install your new CSI files and choose a new password.

• What is the problem with the form of code signing?

  I would ask code signing for BB10, I go to https://www.blackberry.com/SignedKeys/codesigning.html BUT when I choose sign app for BB10, it always go to the BlackBerry ID login page

  A few months ago anymore, at least not in the way you have used for a signature key. Is now complete with your BlackBerry ID now, hence the need to connect. It used to be a sticky thread at the top of the Council of native development, but I see that they removed that now.

  Go here.

• Free code signing!

  I'm developing an application that requires code signing. The application would serve only on my device and nowhere else.

  I wanted to know if I could get a signing key, i.e. unique access. not massive key free of charge, just for development and deployment.

  Nokia already provides free certificates for the development of general use. Here are some details and a link that best describes.

  http://wiki.Forum.Nokia.com/index.php/S60_3rd_Edition:_Application_Development

  Depending on the features used in an S60 application, there are different ways to sign a request:

  1. Possibility of user: used in an application compatibility are granted during the installation and the application UID should in the unprotected range (0x80000000-0xFFFFFFFF). A developer can use SignSis command to sign a .sis file. Please note that the application can only use: LocalServices, ReadUserData, WriteUserData, NetworkServices, UserEnvironment (S60 3rd Edition FP2, a developer can also use location capability).
  2. Open signed without the Publisher ID: the user must register and sign in to www.symbiansigned.com to download .sis application file. After having successfully downloaded, a developer can get immediately the application signed by the Web site, and the developer can download it from the Web site. This is to test the goal and the signed application can be installed on a mobile device. At the signing, a developer must provide email address valid as well as the number of IMEI (serial number of the phone) device. The signed application is installable within 36 months, and this method is for development purposes.
  3. Open signed with the Publisher ID: a developer must buy a first of TC TrustCenterPublisher ID. For Chinese developers, a developer can go to WoSign for the purchase of a Publisher ID. With the Publisher ID, a developer can request a certificate of developer of the www.symbiansigned.com. Using the certificate, a developer can sign with SignSis command .sis file. This is to test the goal and the certificate is limited by the number of IMEI listed in the certificate (maximum 1000 IMEI numbers to date). This certificate is valid for 36 months, and this method is for development purposes.
  4. Express signed: a developer must have an ID of the Publisher first. The developer has go to www.symbiansigned.com website to connect, and pay 20 USD for such a signature by an application. After you have downloaded the files needed on the site. Immediately, the developer can get the application signed by the Web site, and the developer can download it from the Web site. The signed application is for commercial sales.
  5. Certified signed: a developer must have an ID of the Publisher first. After an application has been fully tested using the Open signed or self-signed method (the request must have a UID between 0x00000000-0x7FFFFFFF), the developer can send the request to one of the 3 named test houses world for detailed testing and little money has to be paid for such a test, although the price may vary a House to another test. After that the application has passed Symbian test criteria, the application may be signed for commercial use.
  6. Symbian signed for Nokia: one of the necessary applications for the pre-installation must pass from the Nokia test criteria, and a developer has to pay for such a test. It has more standards than signed certified, and it should be conducted by 3 named test houses in the world. Detailed information can be found at: www.symbiansigned.com. For developers, who need to use the capabilities of the manufacturer, the developer must present a valid reason to justify the objective of using the features. Once the application has been approved, the developer can use Open signed with the Publisher ID to obtain the certificate required for testing and development. This method is for commercial use
  !

  If a developer wants to sign an application Freeware , please see the article How to sign an application freeware

  RIM is going to take the details of the previous keys and those will be disabled and you get the new.

• Updated approved App - Code signing?

  Hey guys,.

  today I received the email from the approval of my application so my app is officially in the "approved" State However, I have a small correction about my icon of the application that need attention (just 86 x 86 resizing). Once I made the correction, I'm supposed to respond to the email and say that I did.

  My question is: when I submit the update file with the new icon bar, that I sign the bar file again? Which means that I have to order another set of keys? Anyone can guide me please know exactly how I do this? Do I just rebuild the file bar and not worry the code signing part, or?

  Any help would be greatly appreciated!

  Thank you!!

  You don't need to send them back. Resign just your bar to deposit with your .p12 file you created when you registered your keys. Don't forget to also get your version in you - app.xml file number as long as you can't sign the same version twice.

• Code Signing - development vs. Production

  From embedded development of MFD, so this may be a matter of redunant.

  I'm used to code signing being differentiated between development and production of keys, with the latter being an expensive, difficult process.

  For our commercial blackberry application we are really only need to buy a key to release to the public of $ 20 code signing?

  Thanks - Lindsay

  You only need the keys if you use RIM API requires a signature. All secure APIs are noted in the documentation of the API.

  You don't need a key to run your code on the Simulator.

  There is no distinction between the 'production' signed construction and off-production.

• Versions of Blackberry and warnings from Code signing

  Greetings-

  I'm new to the Blackberry development, and, in fact, this is my first post after developing an app for a couple of months.  It went well, but it left me with a few general questions.  I do not know this is the right forum for these questions, then, otherwise, a pointer to the right place to ask this would be appreciated:

  1. I want to be able to customize the wallpaper.  I found a long thread on the web that gave a complicated for this technology, and I also saw the décor package which makes it a piece of cake; However it seems that décor package have not been around prior to version 4.6.  This led to the question: is there anywhere I can go to get a good idea of how the older & mature OSs are still used?  I found a Wikipedia site that gave a glimpse of all the carriers, devices on which they are based and which OS they support on these devices and there were a bunch of still be supported with OSs before 4.6.  But there is no indication of the number of people still use these.  Is there a "lot" of devices with the OSs before 4.6?  And where can I get a summary of the Blackberry range, preferably in a sort of comparative format (as a matrix of features vs model number)?

  2. in my Eclipse workspace, I have a plethora of messages like:

  The path location type Resource Description
  Discourage access: the getHeight() method of display type is not accessible due to restrictions on required library C:\Program Files\Eclipse\plugins\net.rim.eide.componentpack5.0.0_5.0.0.14\components\lib\net_rim_api.jar BackgroundManager.java SlickSwitch/src/net/infoisland/net/AC line 63 Java problem

  I asked and got my code signing keys and have signed with (apparently) success of my application.  Why I always have these warnings and how do I get rid of them (probably the answer to any of these questions will also meet each other ;-)?

  TIA,
  ANW

  (1) there are many devices on the market that supports less than 4.6 OS versions. It depends on who your audience is. Indeed, the BlackBerry Curve (4.5) is one of the best selling smartphones right now so there is a way to go before the changes.

  To change backgrounds, you must use methods of custom paint to do prior to 4.6. Try using paintBackground of IPY and drawBitmap to add a chart. Also check out the graphics API if you need more.

  (2) it depends on what version you have.

  1.1:

  Window > Preferences > BlackBerry Java Plugin > Code Signing

  Check all the signatures that apply to you (if in doubt, check all)

  For 1.0:

  BlackBerry > configure the workspace BlackBerry > BlackBerry JDE > Code Signing

  Check all the signatures that apply to you (if in doubt, check all)

• BlackBerry Code signing

  Hello

  I use APIs that require signature deploy and run on real devices. It says that I have to pay 20USD. I have 3 questions about this.

  1. I need to provide my PIN code. What happens if I do not have a real device?

  2. I use Blackberry JDE on both my laptop and desktop computers. Can I use the same key on both computers.

  3. do I need to get for each application, that I develop Code signing.

  Can someone explain this to me. Thank you.

  Kind regards

  Prasad

  1. the identification number has nothing to do with one of your existing numbers. It's just an arbitrary number that you're supposed to do up/generate. You will only need once - to unlock the. File CSI you will receive more later from the RIM.

  2. Yes, just copy the sigtool.db and sigtool.csk between your machines (once you have run the.) File CSI that will fill the sigtool.* files).

  3. you must generally use the same 'key' for all applications, unless you really want the signatures for these different applications to be obtained using different accounts signature.