Broken documentation:
In the page “Building for iOS on Windows”, the section “Workaround for Unprotected Private Key” needs to be redone because the SubInACL command line tool is no longer available from Microsoft (and does not appear to work with current versions of Windows 10). I’ll put one alternative method below, using the same structure as in the doc (hopefully that makes this a little easier to fix, thanks for all the documentation!):
You might see an error that reads as follows:
ERROR: Unable to determine home directory for remote user. SSH output:…WARNING: UNPROTECTED PRIVATE KEY FILE!..0660
If you do not see this error, you can proceed with the next step. If you do see this error, use the following steps to resolve it:
- Navigate to your RemoteToolChainPrivate.key
- Right-click the file and select “Properties”
- Click the “Security” tab
- Click “Edit…”
- Remove all group or user names
- Click “Add…”
- Click “Object Types…” and make sure all boxes are checked, then hit OK
- In the text box, type “Users”, then hit Enter.
- Make sure permissions for Users is set to Read and Read & Execute
This will change the file’s primary group so that it is not the same as your username, which is what confuses SSH when it checks group permissions. The process should then work as normal.
(Note that SubInACL could previously be used for this purpose, but is no longer available from Microsoft. Cygwin is a possible alternative which has been discussed in AnswerHub)