verifying "/" exists in User-Password field

[Phil Mayers]

Geoff Silver wrote:
>> If so, this works for me:
>>
>> user User-Password=~".*/.*", Some-Stuff := whatever
> 
> Cool.  So is there an easy way to combine that with the dynamic hint I'm 
> already creating, since I'm already applying a hint?  If I change my 
> hint to:
> 
> DEFAULT         User-Name =~ "^(.*)$", User-Password =~ ".*/.*"
>                 Hint = "Port-%{request:Packet-Dst-Port}"
> 
> Then connections which use Port-1812 also require a / in the password 
> (which will never appear, because when doing SSL authentication, the 
> password is always the username).  I tried to "chain" the hints, but 

Yes, you can't do that annoyingly - the Fall-Through pseudo-attribute is 
not checked/honoured, and the hints processing code will ALWAYS break on 
first match.

I don't think you'll be able to do it cleanly in hints. Your following 
solution was about as good as it will get.