dpsa4flower
Server and client to use the flower framework for differentially private federated learning with secure aggregation.
Made to be used with the dpsa infrastructure, head there for an explanation of the system's participants and properties. Setup of additional aggregation servers is required, head here for instructions.
Installation
To install, you require the following packages:
- python version 3.9 or higher.
- poetry package manager for python
Once you have those, go ahead and clone this repository:
> git clone https://github.com/dpsa-project/dpsa4flower.git
Enter the new directory:
> cd dpsa4flower
Use poetry to create a virtualenv and install all dependencies:
> poetry shell
> poetry install
You're ready to use our classes now. Note that to actually run a learning task, you will need to provide locations at which two seperate dpsa4fl aggregation servers are running. See here for instructions or check out our example project.
Example code
There is a repo containing an example implementation learning the CIFAR task using a torch model, where learning is federated using flower with differential privacy and secure aggregation.
Classes
This package exposes two classes, one for the server and one for the client.
DPSAServer(model_size, privacy_parameter, granularity, aggregator1_location, aggregator2_location, client_manager, strategy)
The dpsa4flower server class extends the flower server class with the necessities for using DPSA for aggregation. It handles configuration of the aggregator servers, reshaping of the collected aggregation results, and redistributing the updates to the clients. Construction requires the following parameters as keyword arguments:
model_size: intThe number of parameters of the model to be trained.privacy_parameter: floatThe desired privacy per learning step. One aggregation step will be1/2*privacy_parameter^2zero-concentrated differentially private for each client.granularity: intThe resolution of the fixed-point encoding used for secure aggregation. A larger value will result in a less lossy representation and more communication and computation overhead. Currently, 16, 32 and 64 bit are supported.aggregator1_location: strLocation of the first aggregator server in URL format including the port. For example, for a server running locally: "http://127.0.0.1:9991"aggregator2_location: strLocation of the second aggregator server in URL format including the port. For example, for a server running locally: "http://127.0.0.1:9992"client_manager: flwr.server.ClientManagerA flower client manager to manage connected clients.strategy: Optional[flwr.server.strategy.Strategy]A flower strategy for the server to use. It will be wrapped replacing theconfigure_fitandaggregate_fitmethods with ones that interact with the dpsa infrastructure.
An example construction of a dpsa4flower server object would look like this:
dpsa4flower.DPSAServer(
model_size = 62006,
privacy_parameter = 30,
granularity = 32,
aggregator1_location = "http://127.0.0.1:9981",
aggregator2_location = "http://127.0.0.1:9982",
client_manager=flwr.server.SimpleClientManager(),
)
The created object can then be used to start a flower server using flwr.server.start_server as usual.
DPSANumPyClient(max_privacy_per_round, aggregator1_location, aggregator2_location, client, allow_evaluate)
The dpsa4flower client class implements the NumPyClient interface provided by flower. It's a wrapper for existing NumPyClients adding secure aggregation and differential privacy. The wrapped client is used for local training, results are then submitted to the secure aggregation infrastructure in an encrypted fashion. The constructor requires the following parameters as keyword arguments:
max_privacy_per_round: floatThe maximal zero-contentrated differential privacy budget allowed to be spent on a single round of training. If the selected server offers a weaker guarantee, no data will be submitted and an exception will be raised.aggregator1_location: strLocation of the first aggregator server in URL format including the port. For example, for a server running locally: "http://127.0.0.1:9991"aggregator2_location: strLocation of the second aggregator server in URL format including the port. For example, for a server running locally: "http://127.0.0.1:9992"client: flower.client.numpy_client.NumPyClientThe NumPyClient used for executing the local learning tasks.allow_evaluate: boolEvaluation is a privacy-relevant operation on the client dataset. If this flag is set toFalse, evaluation always reports infinite loss and zero accuracy to the server. Otherwise, the evaluation function of the wrapped client will be used and the results will be released to the server, potentially compromising privacy. Defaults toFalse.
An example construction of a dpsa4flower client object would look like this:
dpsa4flower.DPSANumPyClient(
max_privacy_per_round = 30,
aggregator1_location = "http://127.0.0.1:9981",
aggregator2_location = "http://127.0.0.1:9982",
client = FlowerClient()
)
where FlowerClient is some NumPyClient of your choice. It can then be started using flwr.client.start_numpy_client as usual.
What's going on
When using our classes in the setup described (and used in the example project), the training procedure takes place as described in this diagram:
gradient sum
┌───────────────────────────────────────────────────────────────────────────────┐
│ (differentially private) │
│ │
│ │
│ │
│ │
│ gradient shares │
│ (ciphertext) │
┌───────▼─────────┬────────────────────┐ │
│ DPSANumPyClient │ │ ┌──────────────┐ │
└─────────────────┴────────────────┐ └─► │ │
│ │ Aggregator 1 ├───┐ │
┌───)─────► │ │ │
│ │ └──────────────┘ │ ┌───────┴───────┐
. │ │ │ gradient sum │ │
. │ │ ├───────────────────► DPSAServer │
. │ │ │ (differentially │ │
│ │ ┌──────────────┐ │ private) └───────────────┘
│ └─────► │ │
│ │ Aggregator 2 ├───┘
┌─────────────────┬────────────┘ ┌─────► │
│ DPSANumPyClient │ │ └──────────────┘
└─────────────────┴────────────────┘
gradient shares
(ciphertext)
flower clients dpsa4fl infrastructure flower server
-------------- ---------------------- -------------
compute gradients locally checks if clipping was done properly, collects aggregate,
on sensitive data, computes aggregate on ciphertext, distributes updates
clip to norm 1 and submit adds noise for differential privacy. back to the clients
ciphertext can not be decrypted
if the servers don't collaborate
Metadata
Release files for dpsa4flower 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dpsa4flower-0.6.1.tar.gz | 11.3 kB | Without provenance | Details for dpsa4flower-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dpsa4flower-0.6.1-py3-none-any.whl | Python 3 | none | any | Details for dpsa4flower-0.6.1-py3-none-any.whl |
Total release size: 22.2 kB
Release files / dpsa4flower-0.6.1.tar.gz
| Download URL | dpsa4flower-0.6.1.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
713695187a962647b1a9226e625630f9363144edffd00c4d5842c78dd8e73a20
|
|
BLAKE2b-256 checksum How to use checksums |
80ca2813beb23b844b50eb821e0896121d3a25f54f35054d8511cb1550ad56b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.2 CPython/3.10.8 Linux/5.15.109
|
Release files / dpsa4flower-0.6.1-py3-none-any.whl
| Download URL | dpsa4flower-0.6.1-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1d539fe92908e690969f71fab96ae6dd519913d947140e8b670abc55633b1bc
|
|
BLAKE2b-256 checksum How to use checksums |
a7476e786cbd4f9604565b2645fea75d795b63218757d329ade8c69e22a7d5a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.2 CPython/3.10.8 Linux/5.15.109
|
Security for dpsa4flower 0.6.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.