| This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>

### Promoted endPort in Network Policy to Stable

Promoted `endPort` in [Network Policy](https://kubernetes.io/docs/concepts/services-networking/network-policies/#targeting-a-range-of-ports) to GA. Network Policy providers that support `endPort` field now can use it to specify a range of ports to apply a Network Policy. Previously, each Network Policy could only target a single port.

     *
     * @throws IOException
     *             if a network error occurs
     */

    @Override
    public int read(final byte[] b) throws IOException {
        return read(b, 0, b.length);
    }

    /**
     * Reads up to len bytes of data from this input stream into an array of bytes.
     *
     * @throws IOException
     *             if a network error occurs
     */

    @Override

     */
    CLIENT_MOVE(2),

    /**
     * Share moved to different node - share mobility event
     */
    SHARE_MOVE(3),

    /**
     * IP address changed - network configuration change
     */
    IP_CHANGE(4),

    /**
     * Share deleted - share removal notification
     */
    SHARE_DELETE(5),

    /**
     * Cluster node unavailable - node down event
     */

#!/bin/sh
#
# fess <summary>
#
# chkconfig:   2345 80 20
# description: Starts and stops a single fess instance on this system 
#

### BEGIN INIT INFO
# Provides: Fess
# Required-Start: $network $named
# Required-Stop: $network $named
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: This service manages the fess daemon

The merged fix enforces validation against the proxying address for a Node. In some cases, the fix can break clients that depend on the `nodes/proxy` subresource, specifically if a kubelet advertises a localhost or link-local address to the Kubernetes control plane. Configuring an egress proxy for egress to the cluster network can also mitigate this vulnerability.

**Affected Versions**:

     */
    public static class ShareInfo0 extends NdrObject {

        /**
         * Default constructor for ShareInfo0.
         */
        public ShareInfo0() {
        }

        /**
         * The network name of the share.
         */
        public String netname;

        @Override
        public void encode(NdrBuffer _dst) throws NdrException {
            _dst.align(4);

        // Check server capability
        if (!supportsMultiChannel()) {
            log.info("Server does not support multi-channel");
            return;
        }

        // Query network interfaces from server
        queryRemoteInterfaces();

        // Discover local interfaces
        discoverLocalInterfaces();

        // Enable multi-channel if we have multiple usable interfaces

        final String key = ComponentUtil.getVirtualHostHelper().getVirtualHostKey();
        keywordList.stream().forEach(keyword -> {
            final List<Tuple3<String, QueryBuilder, ScoreFunctionBuilder<?>>> boostList = getQueryMap(key).get(toLowerCase(keyword));
            if (boostList != null) {
                boostList.forEach(pair -> list.add(new FilterFunctionBuilder(pair.getValue2(), pair.getValue3())));
            }
        });

 * providing name service, datagram service, and session service to the
 * Microsoft Windows platform. A NetBIOS name can be 15 characters long
 * and hosts usually registers several names on the network. From a
 * Windows command prompt you can see
 * what names a host registers with the nbtstat command.
 *
 *  * <blockquote>
 *
 * <pre>
 * C:\&gt;nbtstat -a 192.168.1.15
 *