The passTypeIdentifier or teamIdentifier provided may not match your certificate, or the certificate trust chain could not be verified.
I am creating new Pass type ID in apple developer account using my pass type ID but, I was created pass type ID after I also create certificate then install in keychain,
Now, I export 2 file and save .p12 file at my folder, after that I open terminal and extract with .p12 file to .pem file and upload to my AWS server
Now, I run this code and try to download in iPhone safari browser but not able to download it.
After I try to debug via Xcode using Console and I figure out like
The passTypeIdentifier or teamIdentifier provided may not match your certificate, or the certificate trust chain could not be verified.
Related
I create a file and publish it as ipfs file
$ipfs add file added QmUVTKsrYJpaxUT7dr9FpKq6AoKHhEM7eG1ZHGL56haKLG
next I publish it to ipns
$ipfs name publish QmUVTKsrYJpaxUT7dr9FpKq6AoKHhEM7eG1ZHGL56haKLG Published to k51qzi5uqu5dltd25mh4mbpenvt48ogf896tmzwps60sdsifmh6jbsi5nc432x
and check , resolve correct
$ipfs name resolve k51qzi5uqu5dltd25mh4mbpenvt48ogf896tmzwps60sdsifmh6jbsi5nc432x /ipfs/QmUVTKsrYJpaxUT7dr9FpKq6AoKHhEM7eG1ZHGL56haKLG
trouble is with download it.
curl https://ipfs.io/ipns/k51qzi5uqu5dltd25mh4mbpenvt48ogf896tmzwps60sdsifmh6jbsi5nc432x
is alvays 504 Gateway Time-out
I expect download my data. I wayting about a week.
i want to know where is the privatekey and transation store in google chrome file using metamask extension. can you help me? it is in /Users/jackson/Library/Application Support/Google/Chrome/Default/Extensions???
Metamask stores your private keys using your browser's data store. The source code of Metamask is auditable, like Parity and MyEtherWallet, by downloading from a repository (which you can then be more assured that the program you are running has indeed been looked at by other people -- unless someone is man-in-the-middle attacking you) or by unpacking the Chromium extension you downloaded.
Using Chrome on a Mac, your data is stored in ~/Library/Application Support/Google/Chrome/Defaults/Extensions.
To find which directory it is in, you can do a search grep -rw 'metamask' *. This will search for all instances of the word "matamask" within these folders.
I am trying to make a webpage which will have the entire inventory of servers that our team manages in the form of a table. I am using a simple LAMP stack and the inventory input as a CSV file.
The table has three columns: Hostname, IP address and device serial number.
While this works perfectly fine, I want to take this a step further and make every IP address in the table a hyperlink, clicking which will open an SSH client, which will connect to that IP address. Any cues to how this can be done? I was hoping there would be something like the the mailto: tag which opens an email client (Outlook window).
I've done it following the info of this blog post.
For future reference in case the original page becomes missing, here is the process:
you cannot directly map the ssh:// scheme to PuTTY, but you can map it to an intermediary script which will in turn launch PuTTY with the right arguments. Mine is called putty_ssh.bat and has the following content:
#echo off
set var=%1
set extract=%var:~6,-1%
start "C:\Program Files (x86)\PuTTY\putty.exe" %extract%
the script has to be registered in the registry. You can just create a ssh.reg file with the following content and open it (customizing last line as needed):
REGEDIT4
[HKEY_CLASSES_ROOT\ssh]
#="URL:ssh Protocol"
"URL Protocol"=""
[HKEY_CLASSES_ROOT\ssh\shell]
[HKEY_CLASSES_ROOT\ssh\shell\open]
[HKEY_CLASSES_ROOT\ssh\shell\open\command]
#="\"C:\\path\\to\\putty_ssh.bat\" %1"
When I click on ssh:// links in web pages, it now opens PuTTY.
PuTTY unfortunately does not associate itself with the ssh:// or any other URLs.
You can associate an application with a protocol manually. But it's not trivial. For instructions, see below.
Easier way is to install WinSCP SFTP client. WinSCP 5.9 and newer registers itself to handle the ssh:// URL and opens the session specified by the URL in PuTTY.
So basically, if you just install WinSCP, it will make PuTTY handle the ssh:// URLs, without the below manual tweaks.
(I'm the author of WinSCP)
To register an application manually, see the MSDN article Registering an Application to a URI Scheme.
Basically you add a registry key like:
[HKEY_CLASSES_ROOT\ssh]
#="URL: SSH Protocol"
"URL Protocol"=""
[HKEY_CLASSES_ROOT\ssh\DefaultIcon]
#="\"C:\\Program Files (x86)\\PuTTY\\PuTTY.exe\",0"
[HKEY_CLASSES_ROOT\ssh\shell]
[HKEY_CLASSES_ROOT\ssh\shell\open]
[HKEY_CLASSES_ROOT\ssh\shell\open\command]
#="\"C:\\Program Files (x86)\\PuTTY\\PuTTY.exe\""
Though the above passes a whole URL to the PuTTY command-line. And PuTTY does not understand the ssh:// prefix. So you would have to add a wrapper script that strips the ssh:// and passes only a user and a host to PuTTY.
For that see:
https://johnsofteng.wordpress.com/2009/05/12/launch-putty-from-browser/
I am looking for the Mime type for an aetx file.
This file is used when distributing a windows phone 8 application in house. a user downloads and installs this to their phone.
But, when you download this file the phone does not give the option to install this enrollment token.
I can only guess the web server is not set to the correct MIME type so the phone is responding appropriately.
my google skills have failed me on the occasion and the microsoft documentation is... sparse on this subject.
thanks for any help.
Martyn
Finally found it. in the aet.xml file that's created when you generate one of these tokens you can see its an x509 certificate file.
So, the mime type is:
"application/c-x509-ca-cert"
So you can host this on a secure site and then set the mime type for your users to download, hopefully it saves someone else some time.
While Martin's answer is correct for Windows Phone 8.0, it won't work for Windows Phone 8.1.
If you use "application/c-x509-ca-cert" with 8.1, the .aetx file is transformed to .cer and you get the error 0x8028a001 "Your phone couldn't add one or more certificates because the certificate file might be unsupported or corrupt ...".
The correct type for 8.1 is "application/octet-stream". Same mime-type used when you send the token as attachment in an email.
But with "application/octet-stream", WindowPhone 8.0 doesn't see the aetx file as token and displays its content to the user.
The solution is to use a servlet (or equivalent if you're not using java) to set the mime type dynamically.
Is the Google Drive API sample command line app (DriveCommandLine) currently known to work? I have downloaded the Java client library, and compiled the sample application (inserting my application's client ID and secret created by specifying "installed application" and "other"). It runs and informs me to access the following link in a browser:
https://accounts.google.com/o/oauth2/auth?access_type=online&approval_prompt=auto&client_id=MY_ACTUAL_CLIENT_ID&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&scope=https://www.googleapis.com/auth/drive
(Obviously with my actual client ID there.)
This successfully provides me with an authentication code. When I enter this at the application's prompt, then at the line:
File file = service.files().insert(body, mediaContent).execute();
I get the exception:
Exception in thread "main" com.google.api.client.http.HttpResponseException: 401 Unauthorized
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:978)
at com.google.api.client.googleapis.media.MediaHttpUploader.executeUploadInitiation(MediaHttpUploader.java:338)
at com.google.api.client.googleapis.media.MediaHttpUploader.upload(MediaHttpUploader.java:252)
at com.google.api.services.drive.Drive$Files$Insert.executeUnparsed(Drive.java:309)
at com.google.api.services.drive.Drive$Files$Insert.execute(Drive.java:331)
at DriveCommandLine.main(DriveCommandLine.java:56)
Investigation shows that the GoogleCredential returned has all elements set to null (which seems wrong).
The version of the Drive API client that I am using is "v2-rev5-1.7.2-beta", which is the one currently pointed to on the quickstart page here:
https://developers.google.com/drive/quickstart
I am compiling and running with this JAR and all the ones in the "libs" subdirectory in the classpath (the quickstart page refers to adding source JARs to the classpath which, obviously, dosn't work).
Can anyone shed any light on what might be going wrong here?
Thanks!
The link in the Quick Start is outdated. Try downloading the Drive SDK from the following link: http://code.google.com/p/google-api-java-client/wiki/APIs#Drive_API
See if that makes a difference for you. I have the DriveCommandLine app running fine.
You need to download JSON file from the API access page at
https://cloud.google.com/console.
Rename this json file as "client_secrets.json"
Copy this json into your project folder or more specifically copy it
into "src/main/resources". (This file contains the clientID and secrets). If the file is already present in the folder then replace it.
Now run the project. You will be redirect to Google Drive's "allow
access" page.
PS - json file must belong to an "Installed Type Application" because this is a commandline sample and runs locally.