Hi steffen,
> > I think you've broken my password starting with `#'? netrc(5) from
> > Debian's ftp and ftp-ssl packages don't document a comment
> > character. The traditional way to comment a .netrc is with `machine
> > fake-name-as-comment-here'.
>
> Sorry! You're right, the fetchmail-based parser works line-wise and
> only seems to support comments starting at the beginning of the line,
> after possible whitespace. I'm looking into it.
fetchmail's code doesn't define netrc(5)'s format. It only pokes about
it for bits of interest, skipping macro definitions, for example. The
file format does not support comments. That ad hoc parsers have added
support for them over the years without considering how they're breaking
existing content is not a reason to expand this mistake.
I've just looked at /usr/share/perl5/core_perl/Net/Netrc.pm here and it
doesn't support comments. That's not a bug.
Eric Schmidt cooked up ~/.netrc as part of the Berkeley Network, and it
has no comment character. Neither has MH's ~/.mh_profile, for example,
with an email header called `#' being a convention there, but
necessitating the syntax
pick: -sequence lp
#: the header's value
is the comment
including normal continuation line rules.
Support it isn't fixing a bug, but extending the reach of one. :-)
Cheers, Ralph.
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
__________________________________
[email protected]
