You can always do it manually outside of ipfs, of course, but maybe there's some need to add a split option to ipfs add, i.e. to split a file at a random point before adding it to the IPFS? E.g.:
ipfs add --split=2 /path/to/testfile
added QmHash1 segment 1 of testfile
added QmHash2 segment 2 of testfile
Alternative options could be --split=25m for 25 MB, with g for GB and so on.
In turn ipfs would then need a concat option, e.g.:
ipfs get concat QmHash1 QmHash2 -o /newpath/to/testfile
As stated above, the original idea behind it is to increase security, i.e. to obfuscate the original file. It would be useless, though, if there's a public record on when and by which node an object (hash) was originally added to the IPFS.
The text was updated successfully, but these errors were encountered:
JayBrown commentedMay 30, 2017
Based on ideas from this discussion comment regarding enhanced security.
You can always do it manually outside of
ipfs, of course, but maybe there's some need to add a split option toipfs add, i.e. to split a file at a random point before adding it to the IPFS? E.g.:Alternative options could be
--split=25mfor 25 MB, with g for GB and so on.In turn ipfs would then need a concat option, e.g.:
or as a new command
As stated above, the original idea behind it is to increase security, i.e. to obfuscate the original file. It would be useless, though, if there's a public record on when and by which node an object (hash) was originally added to the IPFS.
The text was updated successfully, but these errors were encountered: