Doubt about B2 configuration with crypt

[steakhutzeee]

That's exactly what i am saying.

There are only two possible scenarios:

1. I point the crypt to "remote:" (that is a bucket) and alongside file names encryption also the bucket name will be encrypted.
2. I point the crypt to "remote:a directory", avoiding the bucket name encryption.

This is what i was trying to say in all my previous messages. Maybe this message was not clear.

[asdffdsa (jojothehumanmonkey)]

i do not agree about 1.
did you try 1., what happened?

[steakhutzeee]

No not tried, just because of what you also posted:

"myremote:" (not recommended).

and

it is generally advisable to define a crypt remote in the underlying remote s3:bucket. If s3: alone is specified alongside file name encryption, rclone will encrypt the bucket name.

My remote would be a bucket so i can't have a bucket in a bucket. So the only option is to create a directory in the bucket and point the crypt to it.

I'm just reporting what's in the docs.

[asdffdsa (jojothehumanmonkey)]

for what it is worth, why not try it and see what happens.
it should work, no problem.

[steakhutzeee]

Yes it works, for the reason @ncw mentioned but that i only figure out now.

After the app key creation if i create a remote "xxx", if i do rclone lsd xxx: i still see the bucket under it.

So i can create the crypt remote pointing to "xxx:the bucket name".

[ncw (Nick Craig-Wood)]

@steakhutzeee

After the app key creation if i create a remote "xxx", if i do rclone lsd xxx: i still see the bucket under it.

Yes that is the reason. Sorry if I wasn't clear enough earlier.

So you must use xxx:bucketName in the crypt remote config otherwise it won't work.