So, I just wanted to take two minutes to thank the volunteers of Forzdem.
Maybe we can give them a small round of applause.
Thanks a lot.
So, I think 25 Thursday has been a while since we live in the future.
And also I ask the AI to write my jokes.
And the AI asked me to ask you if the Wi-Fi is,
you managed to make the Wi-Fi work after our 25 years.
So, even the Wi-Fi jokes are getting old.
So, I'm Remy, I'm a co-founder of Forzdem.
I do some other things, like the open source founder of Forzdem,
it was Emilia at the back.
And in the room, you also have a CDRIC and Kevin,
or like a co-founder of Forzdem.
We've been doing the pilgrimage to Booselle every year,
so it's a blast.
So, anyone using a password manager in the room?
Great.
Who's using password?
So, after what?
We will be giving out a t-shirt and stickers,
so if you want to come, you can, you know,
basically, like, get some swag.
Who's using Bitcoin?
So, you guys are not getting anything.
So, it's a joke, and you can just get it.
We built a password manager,
there is design for collaboration.
So, the main difference is that you can assign permission,
granularity, granularity to secrets.
So, you can store your TOTPs,
you can store your machine-to-machine secret,
your SSH keys, you can store all sort of things,
that are secrets, and that you want them to be
and to an encrypted.
So, you can organize your secret by folders, by group.
You can assign permissions to folders,
and apply this permission recursively.
So, basically, that's the strengths of the software.
And the goal is to solve the collaboration issue
around secret for technical team mostly.
But it can be used by, by pretty much everyone.
So, one of the functionality we developed this year
is, like, let's say you have a secret,
you have a large team, and you want to know
when somebody leaves the organization or is removed from the group,
or is basically, like, living the organization,
you want to know which secret have been accessed
by this person, so that you can mark them as need to be rotated.
So, this is one of the functionality
we built last year around collaboration.
And you can also basically set some policies
around when you want things to expire,
and if you want to make your user life a nightmare,
you can just, like, expire everything at every 30 days.
So, we have native apps on, you know, Apple and Android.
You require an extension to run password.
So, this is required for the reason
that if the server is compromised,
we don't want to give the attacker the opportunity to change the code
that is relative to the cryptographic elements
or, like, the key management.
So, it gives us some interesting properties.
So, for example, we can display this annoying incomes
in your forms, and we can also, like, basically run updates automatically
so the clients are always up to date things
to the browser extension or to update functionalities.
It's also available in a terminal near you.
So, it means you can access your secrets using command line
or even kernel.
So, you can pipe the output of kernel
and since a password used open PGP,
you can decrypt the secrets and, like,
use them directly in your, like, CICD pipelines.
So, also, for the cool kids, some Kubernetes operator.
So, you can, basically, inject the secrets from
passballing to your Kubernetes cartel on that.
So, passballing is available on all Linux platforms.
So, we have packages, native packages for Ubuntu,
and all sort of things.
We also support open Suzy.
So, we have a partnership with Suzy.
And so, now, we are sure that the packages will work,
because it was not the case before.
And, yeah, it's fully open source.
You learn the paid version, so, like, that's something
worse to mention.
We do around three security audits per year.
So, we work with security tree, which is, like,
security research and Germany.
So, they're just completed one in December,
and we have one running right now by another film in the US.
So, we do our work when it comes to security.
What's cooking for 20, 25.
So, for the ones that are using passballing.
One of the main changes that will come to V5 is
an encrypted metadata.
One of the difficulty when creating a credential manager
is that you have different people that have different
kind of requirements.
So, on one side, you're going to have the consumers.
So, for example, run, like, your, like, my mom or whatever.
And then, on the other side, you're going to have, like,
companies like banks, or, like, that have strong
requirements when it comes to security.
And they have, like, requirements that are defined by the state,
or, like, whatever industry they are working on, depends.
So, historically, passport has been more on that side.
So, on that side, it is expected that, for example,
your administrator, no, who you are.
It knows your name.
It knows, like, and on the other side, you have, like,
the expectations that my passport manager doesn't know
when I'm using a certain credential to go somewhere.
On this side, the administrator wants to know
when you're using credentials.
So, it's, it's, it's been, like,
uh, complicated to balance all these requirements
because sometimes you have organization that behaves, like,
uh, consumers.
So, they want privacy.
So, let's say you're an organization that organizes a protest.
You won't anonymity.
But, uh, if you're a bank, you absolutely don't want that.
So, we've been trying to balance the requirements,
even though historically, we've been leaning on that side.
So, one of the changes that we're introducing with, uh,
V5, and it's actually available in V4.10.
And, uh, we work out to ship the V4.11.
So, you can, uh, actually test it.
So, there is a feature flag that you can enable,
and you can test and collect it metadata.
In version 4, even though it would be available,
only in version 5, you can already test it with, uh, version 4.
So, the main change is that we will encrypt the metadata.
So, on, there will be several ways you can do that.
One way is you encrypt with your personal key.
So, let's say you want to use it more on the consumer side.
You can use your personal key, and then the administrative
will not be able to see, uh, your secrets or, like,
anything related to your secret.
And, if you are sharing, then we will use a share key,
uh, to encrypt the metadata.
So, uh, passable to use OpenTDP, which is a, uh,
uh, hybrid crypto system.
So, you have, like, a random session key, uh, iOS key.
There is encrypted with, uh, uh, public key.
And, uh, all together, that makes the secret, uh, uh,
so, there will be options for administrator to choose, uh,
if they want to desalow, for example, personal usage,
they can, or if you want to turn your passable
into, uh, personal usage only, uh, you will be able to do that
through, through the settings.
So, uh, it's been, uh, quite a bit of work.
As you can imagine, that's why it, like,
it's called, uh, passable version 5.
So, um, that will improve the security posture.
Uh, I think I'm running out of time.
So, like, yeah, I'm just going to skip that,
but if you want, uh, uh, sneak peek at, uh,
hold the UI will, uh, change.
There is some, because it's a major version,
we add to, you know, give it a little, uh,
repo lineage.
So, uh, yeah.
Um, you will be able to construct your secret,
and basically, uh, uh,
like Lagos, add some components to, uh,
your secret, so you'll be able to construct
the kind of resource types that you want to use.
So, I'm running out of time, but we are outside,
if you want to talk about it, uh,
we have some other goodies that are coming up soon
in a version 5 X series,
and, uh, thank you for us, then.
And so if you're all thinking too much better.
Thank you, baby.