Andrew <
and...@spam.net> wrote:
> VanguardLH wrote on Sat, 27 Jan 2024 16:43:41 -0600 :
>
>> Syndoc claims to do both encrypt and decrypt; however, that requires
>> using their web site. Yuck!
>
> Yes. But. You said you wanted your contacts even if you lose the
> phone. And you wanted contacts stored encrypted plus decrypted on the
> phone.
Web site access to contacts is a backup method. Be nice to get them
from there as a last resort, like if I lost my phone (lost, damaged,
stolen). However, my statement wasn't about whether or not the
contacts, or any file, was available at the server, but that you were
stuck using their web site to encrypt/decrypt rather than using their
client app. It was about where I could do the encrypt/decrypt that
dropped Suncoc as a candidate. Not even their $3/mo Syndoc Pro has
encrypt/decrypt in their client. Encrypt/decrypt at the client end is
mandatory for me, and web site encrypt/decrypt would be a backup feature
should I no have my client devices available.
> Plus you said you didn't want to have to set up the NAS drive to do that.
Not as easy as you mention. I've setup other servers on my intranet,
like VNC. The setup is not intuitive.
- Run the NAS or VNC server inside a DMZ (often a subnet off the
router).
- Punch a hole in the router's to allow inbound connections. You define
a rule to point at the server for inbound connections on a designated
port.
- Get an account with a DNS provider who supplies a DDNS (Dynamic DNS)
redirect service, like OpenDNS (they make finding their free service
hard to find).
- Install their IP updater client (*) which reports to your account with
the DNS provider what is your current IP address. I get a dynamic IP
from my ISP. A static IP would cost me money.
- In my OpenDNS account, define a hostname. I use that hostname to
reach OpenDNS who then looks up my account to see what is my current
IP address, and OpenDNS then redirects the connection to the WAN-side
of my router, which has a rule to punch through its firewall to
connect to the intranet server host (NAS or VNC).
- Obviously the intranet server host must be left powered on 24x7, and
the same for the router.
- Hope you aren't discovered violating your ISP's TOS on a personal-use
(non-business) service tier regarding operation of publicly accessible
servers on your intranet.
https://en.wikipedia.org/wiki/Dynamic_DNS
https://support.opendns.com/hc/en-us/articles/227987767-Using-Dynamic-DNS-with-OpenDNS
https://support.opendns.com/hc/en-us/articles/227987867-What-is-the-OpenDNS-Dynamic-IP-updater-client
I recall No-IP (
https://www.noip.com/) was another similar DDNS service.
Been too long to remember why I chose OpenDNS over No-IP. Perhaps
because OpenDNS has categories (of censoring) of who would get blocked
through their redirection service.
Wouldn't need DDNS if I got a static IP address assigned to the WAN-side
of my router from my ISP's DHCP server, but that costs money. There are
free methods of transferring or accessing files across hosts or networks
without having to pay for a static IP address, like cloud sync.
Yes, for always-on cable Internet setups, IP addresses do not often
change. In fact, after the bind's expiration, and after losing the bind
(powering down your router, or resetting it), often the ISP's DHCP
server will assign a new bind using the same IP address. It's held in
limbo for a while. But once you lose the bind, there's no guarantee
you'll get the same IP address. That's why it's called dynamic IP.
Dynamic IP addressing is included in my service tier with my ISP. I
would have to upgrade to and pay for a business account to get a static
IP address. A business account would also allow me to run publicly
accessible servers on my intranet hosts. Doing so with a personal-use
service tier violates their TOS.
Note when you speak of NAS, I assumed you means a NAS drive sitting on
your intranet, not cloud NAS storage which, for me, would provide
nothing more than cloud storage services already provide to me (e.g.,
OneDrive, Google Drive, Dropbox) and which can be access via web browser
or, more preferrable, local sync clients.
>> They only have Android and iOS clients, no Windows client.
>> 10 GB of cloud storage is nice, but unneeded in my
>> scenario with 32 GB in a OneDrive, GoogleDrive, and Dropbox scenario
>> (all free). Syndoc's free version has limited features and throttled
>> bandwidth (so there is a lure to pay for their Pro version). No thanks
>> to Syndoc mostly from having to use their web site to do encrypt/decrypt.
>
> Yes. But. You said you wanted access to contacts if you lose the phone.
Again, the statement was about having to use their web site to do
encrypt/decrypt. Granted I would have access without an endpoint
device, but remember we were discussing how to protect those contacts.
You mention using apps that don't upload contacts anywhere, but mention
somehow toting or transferring a file full of contact records, so then
it became how to protect those contacts wherever they are stored. That
the apps don't upload them still meant you had to protect wherever you
had them.
> I'm just expecting you to understand my point of view which is simple:
> 1. It's simple not to store your contacts in the default location.
True. As noted by someone else, I can save contacts on the phone in its
storage which is still accessible by pointing the app there. They don't
get synchronized from there. Works okay for a single device, but
cumbersome when managed multiple devices. Then you mentioned importing
into the app (which presumably means the app is configured to save
contacts in local storage only). Then 2 points came up: how to protect
the contact records you import (via encrypt/decrypt), and how protecting
your contacts list protects all your contacts defined in your e-mails.
Got some info on how to supply encrypters/decrypters on each device, but
keeping the e-mails protected in-situ on the mail server was never
addressed (and I've only found 1 solution, so far, using ProtonMail,
that will still work with local e-mail clients).
> 2. And it's simple to do whatever it is you want to do with them afterward.
>
> A person only need 2 things, which, unfortunately, most people don't have.
> A. They have to be wise enough to know _why_ they don't want to store
> their contacts in the default Android database & uploaded to servers.
> B. They have to be intelligent enough to create their own solution
> when they don't store their contacts in the default Android location.
Yep, increased security is often not easy. However, I'm not wasting
time protecting my contacts if the e-mails are not protected. I might
consider the scenario where I transport an encrypted file to my devices,
decrypt it on the device, and import into an app configured to store
contacts on local-only storage. However, as ancient as it sounds to
you, however the mode of transport (file transfers, cloud storage, USB
drive), we're still back to the old Sneakernet scenario. Instead of
toting around a drive, you're toting around a file. In fact, since I
have to be physically present with the device to do the import into an
app that stores local-only, all that setup with cloud storage, NAS, FTP,
or whatever other electronic means is more difficult than toting around
a USB drive. After all, you claim you only modify your contacts maybe
once per year. All other setups take more effort than bringing a USB
drive to each device. You can have a smart-door on your house where you
wave your hands around to gesture an opening action, or you can just
stick a key in the lock to open. Sometimes folks come up with the most
convoluted (Rube Goldberg) schemes to peform a simple task.
>> Zarchiver has no network access, so I would have to incorporate the use
>> of the OneDrive, Google Drive, or Dropbox clients to perform cloud sync
>> between devices.
>
> I did give you a few other apps that do both archival and network access,
> but ZArchiver solves a _different_ problem set. I mentioned ZArchiver
> mostly to solve all the problems that Frank Slootweg said he wanted solved.
>
> Frank hasn't responded, but I think ZArchiver solved all his stated needs.
>
https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver
Since I already have the cloud sync clients (OneDrive, Google Drive,
Dropbox) on my devices, that solves the deficiency of Zarchive, or any
other archive app, of not having network access. So I'd get the
convenience of cloud sync across devices, the security of encrypted data
transfer, but I could also tote along a USB drive without anything going
across a network or stored online. No network solution is going to be
as secure as requiring a physical device.
>> Zarchive doesn't list .pea as supported, but .7s is
>> supported, so perhaps the TOC can be encrypted, too.
>
> What does "TOC" mean in this context. I see you mean "Table of Contents",
> so I guess you mean what Frank meant by looking inside the
> password-protected encrypted archive but without decompressing it first?
Yep. The TOC (Table of Contents) in an archive is the list of folders
and files. Most archive formats do not protect the TOC, so anyone can
get a list of what is inside the archive. Often folder and file names
provide a hint of what is inside. .pea, .7s, and .rar allow including
the TOC when the archive is encrypted. .zip, and other archive formats,
do not. If you don't want anyone to snoop inside your encrypted archive
to get at its contents, perhaps you don't want them to snoop at the
folder and file names, either. Just because you can include the TOC in
encryption with some archive formats doesn't mean you must. It's a
security option.
Say you're trying to hide in a house. Someone rings the bell. You go
to the door and say "Andrew here. What do you want?" You identified
you're in the house where you were trying to hide.
>> I didn't find Windows or iOS versions of Zarchiver. I'd be using
>> Peazip on my Windows hosts, and Zarchiver on my Android phones.
>
> That's a completely different problem set, which wasn't stated, AFAIK,
> until now, where cross-platform tools will mostly be the open source
> apps.
I mentioned cross-platform when I first mentioned AxCrypt. I thought I
found a cross-platform client app for encrypt/decrypt on Windows,
Android, and iOS. Nope, it will decrypt on all those platforms, but not
encrypt (unless you pay for their subscriptionware). What you get is
their archive viewer (decrypt only). To add encryption costs $4/mo.
I'll probably continue using the cloud sync clients (OneDrive, Google
Drive, Dropbox) which are available for Windows, Android, and iOS. If
and when I add Linux into the mix, I'll have to find what to use there.
Since all those cloud services provide an API to use them, some Linux
app probably utilitizes the APIs to access the cloud services. I'll
figure that out when I get there.
For now, I have Peazip (7-zip fork with more features and better GUI) on
my Windows hosts, and installed Zarchiver on Android. I only have 1 iOS
device, it's locked down by my HMO that gave it to me for free, so not
important to get contacts there in encrypted form since I don't yet use
it for e-mails. Plus, as you mention, decide to use apps that keep
contacts local.
I already have a working setup, though. I have the cloud sync clients
on my devices. Any file manager can use the cloud sync folders. I have
OneNote on my Windows and Android devices, and it supports AES-128
encryption. If I'm without access to my devices, I can still get at my
OneNote data using a web browser. For the encrypted sections, I have to
provide my password (which is different than for my account login). So,
I already have transport of my contacts, or any file, across multiple
devices using cloud sync.
I need to look further into closing both doors into the barn. As you
state, I can close one door by not saving my contacts where they would
get synchronized to my e-mail accounts online. Before I do that, I need
to determine how to close the other door into the barn: access to the
e-mails with all those contacts in the headers. I found one solution
(ProtonMail), but that's not free, and requires running their "bridge"
(local proxy) to decrypt all my e-mails that remain encrypted while on
their server. I'll keep looking for an in-situ encrypted scenario for
the e-mails.