Android 上的自签名 SSL 接受

发布于 2024-07-30 20:42:56 字数 114 浏览 1 评论 0原文

如何在 Android 上接受 Java 自签名证书?

代码示例将是完美的。

我在互联网上到处查找,虽然有些人声称找到了解决方案,但它要么不起作用,要么没有示例代码来支持它。

How do I accept a self-signed certificate in Java on Android?

A code sample would be perfect.

I've looked everywhere on the Internet and while some people claim to have found the solution, it either does not work or there is no sample code to back it up.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(8

梦亿 2024-08-06 20:42:56

我在 ExchangeIt 中具有此功能,它通过 WebDav 连接到 Microsoft Exchange。 以下是创建 HttpClient 的一些代码,它将通过 SSL 连接到自签名证书:

SchemeRegistry schemeRegistry = new SchemeRegistry();
// http scheme
schemeRegistry.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80));
// https scheme
schemeRegistry.register(new Scheme("https", new EasySSLSocketFactory(), 443));

HttpParams params = new BasicHttpParams();
params.setParameter(ConnManagerPNames.MAX_TOTAL_CONNECTIONS, 30);
params.setParameter(ConnManagerPNames.MAX_CONNECTIONS_PER_ROUTE, new ConnPerRouteBean(30));
params.setParameter(HttpProtocolParams.USE_EXPECT_CONTINUE, false);
HttpProtocolParams.setVersion(params, HttpVersion.HTTP_1_1);

ClientConnectionManager cm = new ThreadSafeClientConnManager(params, schemeRegistry);

EasySSLSocketFactory 是 此处,EasyX509TrustManager 为 此处

ExchangeIt 的代码是开源的,托管在 googlecode 此处,如果您有任何问题。 我不再积极致力于它,但代码应该可以工作。

请注意,自 Android 2.2 以来,该过程发生了一些变化,因此请检查 this 使上面的代码工作。

I have this functionality in exchangeIt, which connects to Microsoft exchange via WebDav. Here's some code to create an HttpClient which will connect to self signed cert's via SSL:

SchemeRegistry schemeRegistry = new SchemeRegistry();
// http scheme
schemeRegistry.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80));
// https scheme
schemeRegistry.register(new Scheme("https", new EasySSLSocketFactory(), 443));

HttpParams params = new BasicHttpParams();
params.setParameter(ConnManagerPNames.MAX_TOTAL_CONNECTIONS, 30);
params.setParameter(ConnManagerPNames.MAX_CONNECTIONS_PER_ROUTE, new ConnPerRouteBean(30));
params.setParameter(HttpProtocolParams.USE_EXPECT_CONTINUE, false);
HttpProtocolParams.setVersion(params, HttpVersion.HTTP_1_1);

ClientConnectionManager cm = new ThreadSafeClientConnManager(params, schemeRegistry);

The EasySSLSocketFactory is here, and the EasyX509TrustManager is here.

The code for exchangeIt is open source, and hosted on googlecode here, if you have any issues. I'm not actively working on it anymore, but the code should work.

Note that since Android 2.2 the process has changed a bit, so check this to make the code above work.

白芷 2024-08-06 20:42:56

我昨天在将我们公司的 RESTful API 迁移到 HTTPS 时遇到了这个问题,但使用的是自签名 SSL 证书。

我到处寻找,但我发现的所有“正确”标记答案都包括禁用证书验证,显然覆盖了 SSL 的所有含义。

我终于找到了解决方案:

  1. 创建本地密钥库

    要使您的应用能够验证自签名证书,您需要以 Android 可以信任您的端点的方式提供带有证书的自定义密钥库。

此类自定义密钥库的格式是来自 BouncyCastle 的“BKS”,因此您需要可以下载的 1.46 版本的 BouncyCastleProvider 此处

您还需要自签名证书,我假设它名为 self_cert.pem

现在创建密钥库的命令是:

<!-- language: lang-sh -->

    $ keytool -import -v -trustcacerts -alias 0 \
    -file *PATH_TO_SELF_CERT.PEM* \
    -keystore *PATH_TO_KEYSTORE* \
    -storetype BKS \
    -provider org.bouncycastle.jce.provider.BouncyCastleProvider \
    -providerpath *PATH_TO_bcprov-jdk15on-146.jar* \
    -storepass *STOREPASS*

PATH_TO_KEYSTORE 指向将在其中创建密钥库的文件。 它一定不存在

PATH_TO_bcprov-jdk15on-146.jar.JAR 是下载的 .jar 库的路径。

STOREPASS 是您新创建的密钥库密码。

  1. 在您的应用程序中包含 KeyStore

将新创建的密钥库从 PATH_TO_KEYSTORE 复制到 res/raw/certs.bks (certs.bks 只是文件名;您可以使用任何您想要的名称)

res/values/strings.xml 中创建一个键

<!-- language: lang-xml -->

    <resources>
    ...
        <string name="store_pass">*STOREPASS*</string>
    ...
    </resources>
  1. 创建一个继承 的类DefaultHttpClient

    导入 android.content.Context; 
      导入 android.util.Log; 
      导入 org.apache.http.conn.scheme.PlainSocketFactory; 
      导入 org.apache.http.conn.scheme.Scheme; 
      导入 org.apache.http.conn.scheme.SchemeRegistry; 
      导入 org.apache.http.conn.ssl.SSLSocketFactory; 
      导入 org.apache.http.impl.client.DefaultHttpClient; 
      导入 org.apache.http.params.HttpParams; 
    
      导入java.io.IOException; 
      导入 java.io.InputStream; 
      导入 java.security.*; 
    
      公共类 MyHttpClient 扩展 DefaultHttpClient { 
    
          私有静态上下文appContext = null; 
          私有静态 HttpParams 参数 = null; 
          私有静态SchemeRegistry schmReg = null; 
          私有静态方案 httpsScheme = null; 
          私有静态方案httpScheme = null; 
          私有静态字符串标记=“MyHttpClient”; 
    
          公共 MyHttpClient(上下文 myContext){ 
    
              应用程序上下文 = myContext; 
    
              if (httpScheme == null || httpsScheme == null) { 
                  httpScheme = new Scheme("http", PlainSocketFactory.getSocketFactory(), 80); 
                  httpsScheme = 新方案("https", mySSLSocketFactory(), 443); 
              } 
    
              getConnectionManager().getSchemeRegistry().register(httpScheme); 
              getConnectionManager().getSchemeRegistry().register(httpsScheme); 
    
          } 
    
          私有 SSLSocketFactory mySSLSocketFactory() { 
              SSLSocketFactory ret = null; 
              尝试 { 
                  最终 KeyStore ks = KeyStore.getInstance("BKS"); 
    
                  最终InputStream inputStream = appContext.getResources().openRawResource(R.raw.certs); 
    
                  ks.load(inputStream, appContext.getString(R.string.store_pass).toCharArray()); 
                  输入流.close(); 
    
                  ret = new SSLSocketFactory(ks); 
              } catch (UnrecoverableKeyException ex) { 
                  Log.d(TAG, ex.getMessage()); 
              } catch (KeyStoreException ex) { 
                  Log.d(TAG, ex.getMessage()); 
              } catch (KeyManagementException ex) { 
                  Log.d(TAG, ex.getMessage()); 
              } catch (NoSuchAlgorithmException ex) { 
                  Log.d(TAG, ex.getMessage()); 
              } catch (IOException ex) { 
                  Log.d(TAG, ex.getMessage()); 
              } catch (异常前) { 
                  Log.d(TAG, ex.getMessage()); 
              } 最后 { 
                  返回ret; 
              } 
          } 
      } 
      

现在只需使用 **MyHttpClient** 的实例即可使用 **DefaultHttpClient** 进行 HTTPS 查询,它将正确使用和验证您的自签名 SSL 证书。

HttpResponse httpResponse;

HttpPost httpQuery = new HttpPost("https://yourserver.com");
... set up your query ...

MyHttpClient myClient = new MyHttpClient(myContext);

try{

    httpResponse = myClient.(peticionHttp);

    // Check for 200 OK code
    if (httpResponse.getStatusLine().getStatusCode() == HttpURLConnection.HTTP_OK) {
        ... do whatever you want with your response ...
    }

}catch (Exception ex){
    Log.d("httpError", ex.getMessage());
}

I faced this issue yesterday, while migrating our company's RESTful API to HTTPS, but using self-signed SSL certificates.

I've looking everywhere, but all the "correct" marked answers I've found consisted of disabling certificate validation, clearly overriding all the sense of SSL.

I finally came to a solution:

  1. Create Local KeyStore

    To enable your app to validate your self-signed certificates, you need to provide a custom keystore with the certificates in a manner that Android can trust your endpoint.

The format for such custom keystores is "BKS" from BouncyCastle, so you need the 1.46 version of BouncyCastleProvider that you can download here.

You also need your self-signed certificate, I will assume it's named self_cert.pem.

Now the command for creating your keystore is:

<!-- language: lang-sh -->

    $ keytool -import -v -trustcacerts -alias 0 \
    -file *PATH_TO_SELF_CERT.PEM* \
    -keystore *PATH_TO_KEYSTORE* \
    -storetype BKS \
    -provider org.bouncycastle.jce.provider.BouncyCastleProvider \
    -providerpath *PATH_TO_bcprov-jdk15on-146.jar* \
    -storepass *STOREPASS*

PATH_TO_KEYSTORE points to a file where your keystore will be created. It MUST NOT EXIST.

PATH_TO_bcprov-jdk15on-146.jar.JAR is the path to the downloaded .jar libary.

STOREPASS is your newly created keystore password.

  1. Include KeyStore in your Application

Copy your newly created keystore from PATH_TO_KEYSTORE to res/raw/certs.bks (certs.bks is just the file name; you can use whatever name you wish)

Create a key in res/values/strings.xml with

<!-- language: lang-xml -->

    <resources>
    ...
        <string name="store_pass">*STOREPASS*</string>
    ...
    </resources>
  1. Create a this class that inherits DefaultHttpClient

    import android.content.Context;
    import android.util.Log;
    import org.apache.http.conn.scheme.PlainSocketFactory;
    import org.apache.http.conn.scheme.Scheme;
    import org.apache.http.conn.scheme.SchemeRegistry;
    import org.apache.http.conn.ssl.SSLSocketFactory;
    import org.apache.http.impl.client.DefaultHttpClient;
    import org.apache.http.params.HttpParams;
    
    import java.io.IOException;
    import java.io.InputStream;
    import java.security.*;
    
    public class MyHttpClient extends DefaultHttpClient {
    
        private static Context appContext = null;
        private static HttpParams params = null;
        private static SchemeRegistry schmReg = null;
        private static Scheme httpsScheme = null;
        private static Scheme httpScheme = null;
        private static String TAG = "MyHttpClient";
    
        public MyHttpClient(Context myContext) {
    
            appContext = myContext;
    
            if (httpScheme == null || httpsScheme == null) {
                httpScheme = new Scheme("http", PlainSocketFactory.getSocketFactory(), 80);
                httpsScheme = new Scheme("https", mySSLSocketFactory(), 443);
            }
    
            getConnectionManager().getSchemeRegistry().register(httpScheme);
            getConnectionManager().getSchemeRegistry().register(httpsScheme);
    
        }
    
        private SSLSocketFactory mySSLSocketFactory() {
            SSLSocketFactory ret = null;
            try {
                final KeyStore ks = KeyStore.getInstance("BKS");
    
                final InputStream inputStream = appContext.getResources().openRawResource(R.raw.certs);
    
                ks.load(inputStream, appContext.getString(R.string.store_pass).toCharArray());
                inputStream.close();
    
                ret = new SSLSocketFactory(ks);
            } catch (UnrecoverableKeyException ex) {
                Log.d(TAG, ex.getMessage());
            } catch (KeyStoreException ex) {
                Log.d(TAG, ex.getMessage());
            } catch (KeyManagementException ex) {
                Log.d(TAG, ex.getMessage());
            } catch (NoSuchAlgorithmException ex) {
                Log.d(TAG, ex.getMessage());
            } catch (IOException ex) {
                Log.d(TAG, ex.getMessage());
            } catch (Exception ex) {
                Log.d(TAG, ex.getMessage());
            } finally {
                return ret;
            }
        }
    }
    

Now simply use an instance of **MyHttpClient** as you would with **DefaultHttpClient** to make your HTTPS queries, and it will use and validate correctly your self-signed SSL certificates.

HttpResponse httpResponse;

HttpPost httpQuery = new HttpPost("https://yourserver.com");
... set up your query ...

MyHttpClient myClient = new MyHttpClient(myContext);

try{

    httpResponse = myClient.(peticionHttp);

    // Check for 200 OK code
    if (httpResponse.getStatusLine().getStatusCode() == HttpURLConnection.HTTP_OK) {
        ... do whatever you want with your response ...
    }

}catch (Exception ex){
    Log.d("httpError", ex.getMessage());
}
善良天后 2024-08-06 20:42:56

正如 EJP 正确评论的那样,“读者应该注意到这种技术根本不安全。除非至少有一个对等点经过身份验证,否则 SSL 并不安全。请参阅 RFC 2246。”

话虽如此,这里还有另一种方法,无需任何验证额外课程:

import java.security.SecureRandom;
import java.security.cert.CertificateException;
import java.security.cert.X509Certificate;

import javax.net.ssl.HostnameVerifier;
import javax.net.ssl.HttpsURLConnection;
import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLSession;
import javax.net.ssl.X509TrustManager;

private void trustEveryone() {
    try {
        HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier(){
                public boolean verify(String hostname, SSLSession session) {
                    return true;
                }});
        SSLContext context = SSLContext.getInstance("TLS");
        context.init(null, new X509TrustManager[]{new X509TrustManager(){
            public void checkClientTrusted(X509Certificate[] chain,
                    String authType) throws CertificateException {}
            public void checkServerTrusted(X509Certificate[] chain,
                    String authType) throws CertificateException {}
            public X509Certificate[] getAcceptedIssuers() {
                return new X509Certificate[0];
            }}}, new SecureRandom());
        HttpsURLConnection.setDefaultSSLSocketFactory(
                context.getSocketFactory());
    } catch (Exception e) { // should never happen
        e.printStackTrace();
    }
}

As EJP correctly commented, "Readers should note that this technique is radically insecure. SSL is not secure unless at least one peer is authenticated. See RFC 2246."

Having said that, here's another way, without any extra classes:

import java.security.SecureRandom;
import java.security.cert.CertificateException;
import java.security.cert.X509Certificate;

import javax.net.ssl.HostnameVerifier;
import javax.net.ssl.HttpsURLConnection;
import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLSession;
import javax.net.ssl.X509TrustManager;

private void trustEveryone() {
    try {
        HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier(){
                public boolean verify(String hostname, SSLSession session) {
                    return true;
                }});
        SSLContext context = SSLContext.getInstance("TLS");
        context.init(null, new X509TrustManager[]{new X509TrustManager(){
            public void checkClientTrusted(X509Certificate[] chain,
                    String authType) throws CertificateException {}
            public void checkServerTrusted(X509Certificate[] chain,
                    String authType) throws CertificateException {}
            public X509Certificate[] getAcceptedIssuers() {
                return new X509Certificate[0];
            }}}, new SecureRandom());
        HttpsURLConnection.setDefaultSSLSocketFactory(
                context.getSocketFactory());
    } catch (Exception e) { // should never happen
        e.printStackTrace();
    }
}
羞稚 2024-08-06 20:42:56

除非我错过了什么,否则本页上的其他答案都是危险的,并且在功能上相当于根本不使用 SSL。 如果您信任自签名证书而不进行进一步检查以确保证书是您期望的证书,那么任何人都可以创建自签名证书并可以冒充您的服务器。 到那时,你就没有真正的安全感了。

执行此操作的唯一合法方法(无需编写完整的 SSL 堆栈)是在证书验证过程中添加一个额外的受信任锚点以供信任。 两者都涉及将受信任的锚点证书硬编码到您的应用程序中,并将其添加到操作系统提供的任何受信任的锚点(否则,如果您获得真正的证书,您将无法连接到您的站点)。

我知道有两种方法可以实现此目的:

  1. 按照 http://www.ibm.com/developerworks/java/library/j-customssl/#8

  2. 创建 X509TrustManager 的自定义实例并重写 getAcceptedIssuers 方法以返回包含您的证书的数组:

    public X509Certificate[] getAcceptedIssuers() 
      { 
          X509Certificate[] trustAnchors = 
              super.getAcceptedIssuers(); 
    
          /* 创建一个新数组,为额外的受信任证书留出空间。   */ 
          X509Certificate[] myTrustedAnchors = new X509Certificate[trustedAnchors.length + 1]; 
          System.arraycopy(trustedAnchors, 0, myTrustedAnchors, 0, TrustedAnchors.length);   
    
          /* 加载您的证书。 
    
             感谢http://stackoverflow.com/questions/11857417/x509trustmanager-override-without-allowing-all-certs 
             为了这一点。 
           */ 
          InputStream inStream = new FileInputStream("证书文件名"); 
          CertificateFactory cf = CertificateFactory.getInstance("X.509"); 
          X509Certificate cert = (X509Certificate)cf.generateCertificate(inStream); 
          inStream.close(); 
    
          /* 将您的锚点证书添加为数组中的最后一项。   */ 
          myTrustedAnchors[trustedAnchors.length] = 证书; 
    
          返回我的TrustedAnchors; 
      } 
      

请注意,此代码完全未经测试,甚至可能无法编译,但至少应该引导您正确的方向方向。

Unless I missed something, the other answers on this page are DANGEROUS, and are functionally equivalent to not using SSL at all. If you trust self-signed certificates without doing further checks to make sure the certificates are the ones that you are expecting, then anyone can create a self-signed certificate and can pretend to be your server. At that point, you have no real security.

The only legitimate way to do this (without writing a full SSL stack) is to add an additional trusted anchor to be trusted during the certificate verification process. Both involve hard-coding the trusted anchor certificate into your app and adding it to whatever trusted anchors that the OS provides (or else you won't be able to connect to your site if you get a real certificate).

I'm aware of two ways to do this:

  1. Create a custom trust store as described at http://www.ibm.com/developerworks/java/library/j-customssl/#8

  2. Create a custom instance of X509TrustManager and override the getAcceptedIssuers method to return an array that contains your certificate:

    public X509Certificate[] getAcceptedIssuers()
    {
        X509Certificate[] trustedAnchors =
            super.getAcceptedIssuers();
    
        /* Create a new array with room for an additional trusted certificate. */
        X509Certificate[] myTrustedAnchors = new X509Certificate[trustedAnchors.length + 1];
        System.arraycopy(trustedAnchors, 0, myTrustedAnchors, 0, trustedAnchors.length);  
    
        /* Load your certificate.
    
           Thanks to http://stackoverflow.com/questions/11857417/x509trustmanager-override-without-allowing-all-certs
           for this bit.
         */
        InputStream inStream = new FileInputStream("fileName-of-cert");
        CertificateFactory cf = CertificateFactory.getInstance("X.509");
        X509Certificate cert = (X509Certificate)cf.generateCertificate(inStream);
        inStream.close();
    
        /* Add your anchor cert as the last item in the array. */
        myTrustedAnchors[trustedAnchors.length] = cert;
    
        return myTrustedAnchors;
    }
    

Note that this code is completely untested and may not even compile, but should at least steer you in the right direction.

铁憨憨 2024-08-06 20:42:56

如果您按如下方式修改更大的 createSocket 方法重载,Brian Yarger 的答案也适用于 Android 2.2。 我花了一段时间才让自签名 SSL 正常工作。

public Socket createSocket(Socket socket, String host, int port, boolean autoClose) throws IOException, UnknownHostException {
    return getSSLContext().getSocketFactory().createSocket(socket, host, port, autoClose);
}

Brian Yarger's answer works in Android 2.2 as well if you modify the bigger createSocket method overload as follows. It took me a while to get self-signed SSLs working.

public Socket createSocket(Socket socket, String host, int port, boolean autoClose) throws IOException, UnknownHostException {
    return getSSLContext().getSocketFactory().createSocket(socket, host, port, autoClose);
}
携余温的黄昏 2024-08-06 20:42:56

在 Android 上,HttpProtocolParams 接受 ProtocolVersion 而不是 HttpVersion

ProtocolVersion pv = new ProtocolVersion("HTTP", 1, 1);
HttpProtocolParams.setVersion(params, pv);

On Android, HttpProtocolParams accepts ProtocolVersion rather than HttpVersion.

ProtocolVersion pv = new ProtocolVersion("HTTP", 1, 1);
HttpProtocolParams.setVersion(params, pv);
许一世地老天荒 2024-08-06 20:42:56

@Chris - 将此作为答案发布,因为我还无法添加评论。 我想知道您的方法在使用 webView 时是否应该有效。 我无法在 Android 2.3 上这样做 - 相反,我只是得到一个白屏。

经过更多搜索后,我发现了这个 用于处理 webView 中的 SSL 错误的简单修复,这对我来说就像一个魅力。

在处理程序中,我检查是否处于特殊的开发模式并调用 handler.proceed(),否则调用 handler.cancel()。 这使我可以根据本地网站上的自签名证书进行开发。

@Chris - Posting this as an answer since I can't add comments (yet). I'm wondering if your approach is supposed to work when using a webView. I can't get it do so on Android 2.3 - instead I just get a white screen.

After some more searching, I came across this simple fix for handling SSL errors in a webView which worked like a charm for me.

In the handler I check to see if I'm in a special dev mode and call handler.proceed(), otherwise I call handler.cancel(). This allows me to do development against a self-signed cert on a local website.

不知所踪 2024-08-06 20:42:56

这个用例有很多替代方案。 如果您不想在代码库中包含任何自定义代码,例如自定义 TrustManager 我建议尝试 GitHub - SSLContext Kickstart 和以下代码片段:

<dependency>
    <groupId>io.github.hakky54</groupId>
    <artifactId>sslcontext-kickstart</artifactId>
    <version>6.7.0</version>
</dependency>

SSL 配置

SSLFactory sslFactory = SSLFactory.builder()
    .withUnsafeTrustMaterial()
    .build();

SSLContext sslContext = sslFactory.getSslContext();
SSLSocketFactory sslSocketFactory = sslFactory.getSslSocketFactory();

HttpClient 配置

HttpParams params = new BasicHttpParams();
HttpProtocolParams.setVersion(params, HttpVersion.HTTP_1_1);
HttpProtocolParams.setContentCharset(params, HTTP.UTF_8);

SchemeRegistry registry = new SchemeRegistry();
registry.register(new Scheme("https", sslSocketFactory, 443));

ClientConnectionManager ccm = new ThreadSafeClientConnManager(params, registry);

HttpClient httpClient = new DefaultHttpClient(ccm, params);

HttpsUrlConnection

HttpsURLConnection.setDefaultSSLSocketFactory(sslSocketFactory); 

There are a-lot alternatives for this use case. If you don't want to have any custom code in your code base such as custom TrustManager I would suggest to try GitHub - SSLContext Kickstart and the following code snippet:

<dependency>
    <groupId>io.github.hakky54</groupId>
    <artifactId>sslcontext-kickstart</artifactId>
    <version>6.7.0</version>
</dependency>

SSL configuration

SSLFactory sslFactory = SSLFactory.builder()
    .withUnsafeTrustMaterial()
    .build();

SSLContext sslContext = sslFactory.getSslContext();
SSLSocketFactory sslSocketFactory = sslFactory.getSslSocketFactory();

HttpClient configuration

HttpParams params = new BasicHttpParams();
HttpProtocolParams.setVersion(params, HttpVersion.HTTP_1_1);
HttpProtocolParams.setContentCharset(params, HTTP.UTF_8);

SchemeRegistry registry = new SchemeRegistry();
registry.register(new Scheme("https", sslSocketFactory, 443));

ClientConnectionManager ccm = new ThreadSafeClientConnManager(params, registry);

HttpClient httpClient = new DefaultHttpClient(ccm, params);

HttpsUrlConnection

HttpsURLConnection.setDefaultSSLSocketFactory(sslSocketFactory); 
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文