iOS安全深度探索：黑客与防御 - CSDN文库

4星 · 超过85%的资源需积分: 10 32 浏览量更新于2024-07-23 收藏 6.93MB PDF 举报

"《iOS黑客手册》是一本深入探讨iOS设备安全性的专业书籍，涵盖了从基础到高级的各种安全主题。作者旨在揭示Apple如何在iOS设备上构建防护机制以防止潜在的妥协，特别是在新设备和未来智能设备中。本书对iOS的安全威胁、架构、加密、代码签名、内存保护、沙盒化以及模糊测试和利用等方面进行了详细阐述，特别适合IT专业人士、安全研究人员和iOS开发者阅读。在第一章‘iOS安全基础’中，作者介绍了iOS的不同硬件类型和设备，分析了Apple如何保护App Store免受攻击，并概述了iOS面临的安全威胁。同时，书中详细剖析了iOS的安全架构，回顾了iOS设备历史上遭遇的主要攻击事件。第二章‘iOS在企业中的应用’探讨了企业环境中如何管理iOS设备，包括配置管理及移动设备管理策略，这对于企业IT管理员确保数据安全和设备合规性至关重要。第三章‘加密’详细讨论了数据保护机制，包括如何保护数据以及针对数据保护的攻击方式，对于理解iOS设备上的数据安全有极大的帮助。第四章‘代码签名与内存保护’解释了强制访问控制、配发工作原理、应用签名，以及权限等内容。此外，还探讨了代码签名的执行机制，如何发现动态代码签名以及如何打破代码签名。第五章‘沙盒化’介绍了iOS应用的沙盒概念，指导开发者如何将应用程序沙盒化，并详细解析了沙盒的实现机制，有助于提高应用的安全性和隔离性。第六章‘模糊测试iOS应用’讲解了模糊测试的基本原理，提供了模糊测试的步骤，通过实例展示了如何对Safari、PDF、QuickLook和SMS等进行模糊测试，利用模拟器和真实设备进行测试。第七章‘利用技术’专注于利用漏洞，详细阐述了不同类型的漏洞利用，包括iOS系统分配器的工作原理，以及如何驯服iOS分配器来更有效地进行漏洞利用。总体来说，《iOS黑客手册》是iOS安全领域的宝贵资源，不仅提供理论知识，还包含实用技巧，让读者能够深入了解并应对iOS设备上的安全挑战。"

After you have set a passcode, you should see a screen like the one shown in Figure 2.8, confirming that the profile has been successfully

installed. Now the settings specified in the configuration profile should have also taken effect. To verify this, go to the Passcode Lock screen in the

General menu of Settings. It should look like the screen in Figure 2.9. As you can see, some of the options have been disabled by the profile and

are grayed out.

Figure 2.8 Confirmation that the configuration profile has been installed

Figure 2.9 Passcode Lock screen showing the effect of the configuration profile

Applications and Provisioning Profiles

The iPhone Configuration Utility can also be used to install applications and provisioning profiles onto iOS devices. For now, all you need to know

is that custom applications require an Apple-issued Provisioning Profile for the application's developer in order to run on an iOS device. These

provisioning profiles may be installed separately or they may also be bundled with the application when it is distributed.

Mobile Device Management

The iPhone Configuration Utility can be used to perform basic enterprise management of iOS devices, but it clearly doesn't scale well to managing

a large number of devices. For enterprises with a larger number of devices, Apple has implemented Mobile Device Management (MDM)

functionality in iOS that allows the devices to be managed completely over the air.

Apple has released the MDM API to third-party providers, and a large number of third-party Mobile Device Management product vendors exist.

Apple also provides an MDM solution in Lion Server. Apple's implementation in Lion Server is the Profile Manager; a facility for managing settings

for users of both iOS devices and computers running Mac OS X. Profile Manager is a simple MDM solution that should work well for small

organizations or workgroups. If you are managing a large number of devices or require more features than Profile Manager provides, you should

investigate one of the many commercial MDM solutions that support iOS-based devices.

MDM Network Communication

In Apple's MDM architecture (depicted in Figure 2.12), network communication is performed between three entities: the user's iOS device, his or

her organization's MDM server, and Apple's Push Notification Service (APNS). The MDM server communicates with the APNS to publish push

notifications that are routed to the specified device and delivered through that device's persistent connection to the APNS. Upon receiving a push

notification, the iOS device establishes a direct connection to the configured MDM server.

Figure 2.12 MDM network communication

The iOS device itself maintains a persistent connection to one of the APNS courier servers at courier.push.apple.com, which is the centralized

communications channel used for all push notifications on iOS. This connection is established using client-certificate authenticated TLS to TCP

port 5223 and uses the XMPP protocol. iPhones and iPads with a cellular data connection make this connection over the cellular network, whereas

other mobile iOS devices are able to make this connection only when they are on a Wi-Fi network. The XMPP protocol was designed for the

Jabber instant messaging system; however, it is flexible enough to be used for any system needing presence notification and a publish/subscribe

model for message distribution. The iOS device simply informs Apple's APNS servers which topics to subscribe to, and those servers will route

messages published to those topics to the device. In the case of MDM, a managed client device is configured to subscribe to a unique topic

corresponding to the MDM server that is managing the device.

The MDM server acts as a push notification provider, similar to the way third-party application developers implement push notifications for their

iOS applications. In this role, the server connects to Apple's APNS gateway servers at gateway.push.apple.com. This connection is also over

client-certificate authenticated TLS, but this time it is to TCP port 2195. Push notifications are formatted as JSON dictionaries and are sent to

Apple's APNS servers through a custom binary network protocol. The push notification provider also makes a similar connection to Apple's APNS

servers on TCP port 2196 for the feedback service. Apple does not guarantee that these services will remain on a defined IP subnet, so it

recommends that firewall administrators permit outbound access to Apple's entire assigned IP space of 17.0.0.0/8. For more specifics on these

communications, see Apple's Local and Push Notification Programming Guide in the iOS Developer Library.

Finally, the MDM server serves the MDM API over HTTPS. When an iOS device receives an MDM push notification, it contacts the MDM server

at the URL configured when the device was enrolled for management and queries the MDM server directly for the sent command. The response to

the downloaded command is sent over HTTPS back to the MDM server. The MDM server may optionally provide a Simple Certificate Enrollment

Protocol (SCEP) server on TCP port 1640, which is also built on top of HTTP. The protocol-level details of the MDM API are beyond the scope of

this chapter. For more information on these, see David Schuetz's presentation “Inside Apple's MDM Black Box,” presented at BlackHat USA 2011

(https://media.blackhat.com/bh-us-11/Schuetz/BH_US_11_Schuetz_InsideAppleMDM_WP.pdf).

Lion Server Profile Manager

Lion Server's Profile Manager is a Ruby-on-Rails web application that acts as an MDM API server and administration console. The initial setup and

configuration is performed through the Server app, but after the initial setup, most administration tasks are performed through a web browser to the

Profile Manager web application.

Profile Manager can apply settings on a user, user group, device, or device group basis. If the devices' owners have accounts in Open Directory,

they can log in to the Profile Manager web application directly to enroll and manage their devices. If the devices are shared or the users do not have

accounts in OD, a Lion Server administrator will have to enroll their devices for them. Profile Manager supports a special type of profile, called an

Enrollment Profile, to assist in enrolling devices for remote management without requiring the user to log in to the Profile Manager web application.

This chapter assumes that device owners also have accounts in Open Directory on the Lion Server. For more information on using Enrollment

Profiles, consult the eBook “Managing iOS Devices with OS X Lion Server” by Arek Dreyer from Peachpit Press.

Setting Up Profile Manager

To set up Profile Manager, launch the Server application and click Profile Manager in the sidebar. This brings up the basic Settings pane for Profile

Manager, as shown in Figure 2.13. Before you can start the service, you have to perform some basic configuration. To get this started, click the

Configure button.

Figure 2.13 Profile Manager service configuration in the Server application

剩余201页未读，继续阅读

gogotest14

粉丝: 0
资源: 2

最新资源