[Nut-upsdev] NUT I-D: Unencrypted communication

[Tim Dawson]

To throw my $.02 in here, *NOTHING* should be "removed for security purposes"!

It should *ALWAYS* be the choice of the person doing the deployment what to use - no some anonymous derp who has no clue about any specifics of the deployment! Not everything has the same exposure, and support of more "legacy" gear must be maintained, even if it means a deliberqte recompile with the old stuff enabled!

- Tim

On January 3, 2022 9:08:45 PM CST, David Niklas <deference at null.net> wrote:
>On Mon, 3 Jan 2022 19:10:09 +0100 (CET)
>Roger Price <roger at rogerprice.org> wrote:
>
>> On Mon, 3 Jan 2022, Greg Troxel wrote:
>> 
>> >>> On 1/3/22 14:17, Roger Price wrote:  
>> >>>> I propose adding the following sentence to section 4.2.12:
>> >>>>
>> >>>>  If the client does not send command STARTTLS to the Attachment
>> >>>> Daemon communication continues unencrypted.  
>> >>>  
>> >> Should the Attachment Daemon upsd be able to defend itself against
>> >> unencrypted access from misconfigured or possibly hostile clients?  
>> >
>> > That's an implementation question, really, but it seems obvious that
>> > it should be conforming for an implementation to refuse to interact in
>> > cleartext.  And also to choose to allow cleartext on localhost and not
>> > with other addresses.  
>> 
>> I'll change the additional sentence to
>> 
>>  If the client does not send command STARTTLS to the Attachment Daemon
>>  communication continues unencrypted, however an Attachment Daemon may
>> refuse unencrypted communication.
>> 
>> How the AD does this is an implementation matter and outside the scope
>> of the RFC.
>> 
>> Roger
>
>What if the client doesn't ask for TLS because the UPS (server) only
>supports an old TLS version that was removed in the client for security
>purposes? Or what if the certificate/certificate chain was compromised
>and so the client doesn't have a TLS cert/cert chain for the UPS?
>
>Just my thoughts,
>David
>
>_______________________________________________
>Nut-upsdev mailing list
>Nut-upsdev at alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220103/fdec551c/attachment.htm>